GNOME Bugzilla – Bug 166209
Bad messages with cp1251 charset
Last modified: 2007-04-05 20:10:04 UTC
In config file: OUTPUT_LANGUAGE = Russian USE_WINDOWS_ENCODING = YES All russian letters in all messages replace on '?' $ locale LANG=ru_RU.cp1251 LC_CTYPE="ru_RU.cp1251" LC_NUMERIC="ru_RU.cp1251" LC_TIME="ru_RU.cp1251" LC_COLLATE="ru_RU.cp1251" LC_MONETARY="ru_RU.cp1251" LC_MESSAGES="ru_RU.cp1251" LC_PAPER="ru_RU.cp1251" LC_NAME="ru_RU.cp1251" LC_ADDRESS="ru_RU.cp1251" LC_TELEPHONE="ru_RU.cp1251" LC_MEASUREMENT="ru_RU.cp1251" LC_IDENTIFICATION="ru_RU.cp1251" LC_ALL=
Created attachment 36947 [details] Fixed version of qtextcodec $diff qtextcodec.cpp.orign qtextcodec.cpp 1324c1324 < #ifndef QT_NO_CODECS --- > // #ifndef QT_NO_CODECS 1951c1951 < #endif // QT_NO_CODECS --- > // #endif // QT_NO_CODECS 2051c2051 < #ifndef QT_NO_CODECS --- > 2056a2057 > #ifndef QT_NO_CODECS
Can the same not be achieved by setting USE_WINDOWS_ENCODING to YES? (I don't know Russian so I do not know for sure).
If I wrote comments in koi8-r I set only OUTPUT_LANGUAGE = Russian and all is ok. If I wrote comments in cp-1251 I set OUTPUT_LANGUAGE = Russian and USE_WINDOWS_ENCODING = YES. In this case in output files all my comments are ok but instead system messages created by doxygen I have question marks. For example I have: ??????? ???????? Doxygen 1.3.9.1 Must be: Создано системой Doxygen 1.3.9.1 This happens because all system messages are written in koi8-r and if I set USE_WINDOWS_ENCODING to YES those messages are translated first into UTF then cp-1251. Doxygen tranlates UTF into cp-1251 with the help of qtextcodec, but in qtextcodec tables of encoding is off (by #ifndef QT_NO_CODECS). My patch activades this tables.
reopening as requested information has been provided. zaz, is this still an issue?
Since the latest CVS update Doxygen uses UTF-8 internally for all strings and uses iconv to recode the input to UTF-8. For HTML, LaTeX and man pages the output is now always UTF-8. For RTF the encoding is local and depends on the code page specified in the translator. The config option USE_WINDOWS_ENCODING has been removed. A new condig option INPUT_ENCODING has been added which can be used to specify the encoding of the input. Another config option DOXYFILE_ENCODING can be used to specify the encoding of the config file itself. Could you please let me know if this fixes the problem.
This bug was marked "assigned" by me some time ago, which means it should be fixed in version 1.5.2 and is hereby marked as such. I would kindly request you to check if this version indeed fixes the problem and reopen the bug report should you still see the same problem.