[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 123672] RTF - kword doesn't recognize lang/charset settings
From:       Mikolaj Machowski <mikmach () wp ! pl>
Date:       2006-03-17 15:49:06
Message-ID: 20060317154906.12066.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=123672         




------- Additional Comments From mikmach wp pl  2006-03-17 16:49 -------
> Then there is the \ansicpg keyword to set a codepage.

After adding just \ansicpg1250 immediately after \ansi KWord displays
previously attached document as it was indented (all Polish characters
visible).
> > Aaahhh.  Checked RTF 1.6 doc and it looks like by design RTF doesn't
> > support native encodings?!
> It does, as it defines the keywords that I have listed above.

Sorry, misunderstood, pre-1.6 versions officially didn't support them.
Even now \ansicpg is rather for proper translation of UTF than native
encodings. 8-bit characters are only as a side effect: (Converters that
communicate with Microsoft Word for Windows or Microsoft Word for the
Macintosh should expect 8-bit characters.)
> It worries me that \pc and \ansi would perhaps not mean a particular
> codepage but just the locale MS-DOS respectively Windows codepages. If
> that is the case, then the RTF filter need quite an improvement.

I am afraid this is the case. Also possible is that MS-programs are
just guessing encoding depending on locale or perform additional tests
to display properly. You could check OO.o code - oowriter displays
document without problems.
[prev in list] [next in list] [prev in thread] [next in thread]