Haruyuki Ohtani writes:
> After I downloaded the source code of doxygen, I understand the
> current doxygen embeds EUC Kanji code in the source and does not
> support generationg Japanese RTF which is typically Shift JIS. I
> guess the most easiet way to support Shift JIS is to embed Shift JIS
> Kanji code instead of EUC in the source, to return the literal string
> "Shift_JIS" instead of "euc-jp" in QCString::idLanguageCharset(), and
> then to recompile all source code. But Maybe it is not good idea
> because of limiting extensibility.
Changing everything to use ShiftJIS (or, more appropriately on
Windows, CP932) is just changing the nature of the problem. Perhaps a
better solution would be to use iconv() to transcode the EUC-JP text
to CP932, at least when certain options are set. Doing this would
eliminate the duplication of messages that differ only in their
encoding.
I haven't looked at the Doxygen source in a long while: I don't know
if changing the Japanese encoding would effect the lexer at all... I
would expect not.
In any event, this could be used too to support different Russian
encodings.
-tree
--
Tom Emerson Basis Technology Corp.
Sr. Sinostringologist http://www.basistech.com
"Beware the lollipop of mediocrity: lick it once and you suck forever"
|
