If you use resource files in such a way that the #pragma code_page directives should not be used during loading and saving, perhaps because you prefer to encode the entire file in UTF-16 or UTF-8, then you should uncheck this option. a mixture of Japanese, Chinese, Western European, etc). These directives are normally used to denote codepage changes within a file, potentially enabling a single file to contain text encoded in a variety of different codepages (e.g. Try to auto-detect character encodings in Windows Resource filesĬheck this option to make Merge look for and use #pragma code_page directives within Windows Resource (.rc) files. Merge currently looks for Unicode byte-order markers at the start of files, XML and HTML encoding directives, files that appear to be validly UTF-8 encoded, and optionally for #pragma codepage directives within resource files. If the encoding cannot be determined, the default character encoding specified below will be used. Try to auto-detect character encoding from file contentĬheck this option to make Merge look within files to determine the character encoding that should be used for loading and saving. The controls on this page enable you to specify the way character encoding is used in text comparisons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |