Hello Dave,
Sorry for my delayed response. I consulted with the product team to get a
more accurate answer for you.
According to their response, it is actually the other way around: if you
know the charset, you know the codepage, because the codepages include all
the charsets. There's a little twist: SYMBOL_CHARSET corresponds to the
codepage 42, at least here in Office : Fonts like Symbol and Wingdings have
SYMBOL_CHARSET.
They told me that ANSI_CHARSET is only 1252. If you want 437 or 850, we
should use \cpg437 or \cpg850, respectively. But hopefully you'll forget
about using codepages in RTF except for those with standard charsets.
If \fcharsetN appears in the \fonttbl entry, RichEdit's RTF reader uses the
corresponding codepage for conversion purposes. If a \cpgN appears, that N
is used for conversion purposes. RichEdit doesn't ever write \cpgN, since
noncharset text runs can be written using Unicode control words \uN. For
example, for Shift-JIS, \fcharset128 (SHIFTJIS_CHARSET) is all that's
needed for reading and writing RTF. The generated rtf will not write the
codepage 932. The next version of the RTF spec will make this clearer.
Regard,
Jialiang Ge (
[email protected], remove 'online.')
Microsoft Online Community Support
=================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
=================================================
This posting is provided "AS IS" with no warranties, and confers no rights.