You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Result after clean-repair: ... <pre>? езультат</pre> ...
It seems tidy does not like cyrillic letter "Р" in pre tag ...
If i replace it with another letter -> result will be ok. ( sorry, but thats not funny ).
If i remove "input-encoding" and "output-encoding" option -> result also will be ok ( sorry, but thats not funny too, because those options have 'utf8' as default value )
The text was updated successfully, but these errors were encountered:
@ogolovanov I have big trouble with utf-8 in my windows machine... but was able to test in linux... and I do not see any problem...
The input file has the hex sequence D0 A0 D0 B5 D0 B7 D1 83 D0 BB D1 8C D1 82 D0 B0 D1 82, which is valid utf-8...
After running it though tidy the ouput remains exactly D0 A0 D0 B5 D0 B7 D1 83 D0 BB D1 8C D1 82 D0 B0 D1 82... no change...
Nothing is changed if I add --input-encoding utf8 --output-encoding utf8, since these are the defaults... so can not duplicate the problem...
Of course I was testing with the latest 5.7.3 tidy, but there have been no encoding, decoding changes inbetween..
And regrettably, we do not add a *.deb packages any more, since 2016. It is usually easy for unix/linux users to build and install from the git source... sorry...
And sorry unable to duplicate the problem, so can do nothing at this time... maybe if you explain more, other samples, etc... thanks...
Hello.
Input:
"<html><body><pre>Результат</pre></body></html>"
Config:
array('input-encoding' => 'utf8', 'output-encoding' => 'utf8');
Result after clean-repair:
...
<pre>? езультат</pre>
...
It seems tidy does not like cyrillic letter "Р" in pre tag ...
If i replace it with another letter -> result will be ok. ( sorry, but thats not funny ).
If i remove "input-encoding" and "output-encoding" option -> result also will be ok ( sorry, but thats not funny too, because those options have 'utf8' as default value )
The text was updated successfully, but these errors were encountered: