Kazuko O. wrote:
Very very sorry, I said totally wrong things.
I can successfully convert MDITA files with BOM and without BOM into PDF.
No problem.
But when MDITA file is opened with xxe, the Japanese characters are incorrectly
displayed (see the attached png).
Please find the attached sample. zip which contains mdita files with BOM and
without BOM.
Thank you.
Your Japanese MDITA file starting with a UTF-8 BOM always looks fine
when opened in XXE. XXE uses this BOM to determine the encoding of the
text file.
Your Japanese MDITA file NOT starting with a UTF-8 BOM looks fine when
opened in XXE running on Linux, because Linux default encoding is UTF-8.
It looks completely WRONG on my Windows 8 PC because the default
encoding there is Windows-1252. When all ways to determine the encoding
of a text file are absent, XXE fallbacks to the default encoding of the OS.
In the next version of XXE, we'll improve (and document) the
Options|Preferences, Add-on|Text Format dialog box (see attached
screenshot of current dialog box) in order to let the user specify the
default encoding of text files (on a per-file-extension basis; e.g.
".md" files use UTF-8, makefile uses default encoding).
And when I edit the UTF-8 MDITA file with BOM and save it by using xxe,
the file is changed to UTF-8 file without BOM.
How do you think about the above case?
This is clearly an oversight. In the next version of XXE, a text file
originally starting an UTF-8 or UTF-16 BOM will be saved back to disk
with its BOM.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
