XYplorer Beta Club

The output of show character table on OS Windows with default codepage WIN-1252 may be correct. I could not verify it.
But the output of show character table on OS Windows with default codepage WIN-1250 is not always right.
Some of the characters which have in WIN-1250 value greater than 128 have wrong unicode value in output of show character table on OS Windows with default codepage WIN-1250. These chars are not preceded with sign '-' in attachment 'UTF-8_CZ_CHARS.txt'.
The second attachment 'UTF - 8 - XYPLORER.txt' is test output of show character table of Xyplorer on OS Windows with default codepage WIN-1250.
Can the show character table feature work properly in these special cases on OS Windows with default codepage other than WIN-1252 ?

So, character Č is not shown as 268 but as 200 under your codepage?

Yes. Character Č was not shown as 268 but as 200 under my codepage Win-1250.
In the last beta version of Xyplorer (19.20.0026) is output of show character table corrected. All values in the columns dec,hex and UTF8 are now correct, but values in the column utf8hex are not yet correct in some cases.
Final correct state should be as is in attachment "Czech_chars_desired_output_final_state.txt". All Czech chars from Win-1250 codepage with values above 128 are encoded into UTF8 with use of two chars. Current state of output is in attachment "Czech_Chars_output_from_xyplorer_v19.20.0026.txt".

Thank you very much. Hogaty.

admin wrote:So, character Č is not shown as 268 but as 200 under your codepage?

Confirmed. Next version should be better.

There is need to make the last eight corrections in the column utf8hex (see attaxchment Czech_chars_with_8_utf8hex_corrections_19_20_0027.zip) . Then will be all in show character table output on windows with default codepage win-1250 solved.

admin wrote:Confirmed. Next version should be better.

Is it fixed in v19.20.0029?

After last fix in v19.20.0029 are all problems solved. Excuse me for delay of my answer. Thank you very much.

admin wrote:Is it fixed in v19.20.0029?

Thank you for the detailed reports!