Page 1 of 1
Compare by contents: code pages
Posted: 2019-03-06, 12:24 UTC
by browny
Recently there was a need to compare a UTF-16 file to a file with ANSI 1256 code page.
My default code page is different, and autodetection (if there is any) did not work.
For quick selection of a code page comboboxes could be added in both sides of Choose encoding dialog.
In the line with ANSI radio buttons, of course.
Re: Compare by contents: code pages
Posted: 2019-03-07, 09:24 UTC
by ghisler(Author)
TC uses the code page chosen in the font settings. Just pick a font and set the encoding to Arabic. This does not affect the encoding of UTF-16.
Re: Compare by contents: code pages
Posted: 2019-03-09, 21:26 UTC
by browny
Thanks.
Font setting is more "permanent", and encoding dialog is better for changing things on the fly.
There were dozens of files, all in different languages.
It was not easy to guess which font to pick even though code pages and language codes were known.
A simple entry field for code page number would have been a convenience.
Luckily, this is not expected to happen often.
Re: Compare by contents: code pages
Posted: 2019-11-11, 16:24 UTC
by Slavic
I would like to support this request: the amount of possible code pages in the Compare contents (chosen in the Font settings) is quite limited and sometimes is not enough. Lister, on the other side, has much more options in the Encoding menu and allows to add user-defined codepages from even more extensive list, like different DOS codepages etc. Adding the Lister-like menu to the Compare dialog would be a great advantage.