[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RTF enconding
From: |
Fred Kiefer |
Subject: |
Re: RTF enconding |
Date: |
Fri, 11 Aug 2006 16:55:56 +0200 |
User-agent: |
Thunderbird 1.5.0.4 (X11/20060527) |
Hi Andreas,
this problem is caused by the GNUstep code not taking the encoding of
the RTF file into account.
The (known) problem is in the method [RTFConsumer
parseRTF:documentAttributes:class:] here we should peek the encoding and
use this to interpret the read characters.
If you send my a short Mac file with Umlaute in it, I might have a look,
but I wont promise nothing.
Fred
Andreas Höschler schrieb:
>
> my text write application generates teh attributed string with
>
> NSAttributedString *attrString = [[NSAttributedString alloc]
> initWithRTFD:value documentAttributes:NULL];
>
> and stores it with
>
> value = [attrString RTFFromRange:NSMakeRange(0, [attrString
> length]) documentAttributes:nil];
>
> This works on MacOSX and on GNUstep. But when I create a document on
> MacOSX with ü,ö.ä,... and open it on GNUstep, these german characters
> are gone. Is this a bug? How can I force RTFFromRange: do encode the
> attributed string as unicode 16 to avoid a possible encoding problem?
>
- RTF enconding, Andreas Höschler, 2006/08/03
- Re: RTF enconding,
Fred Kiefer <=