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?
> 



_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Reply via email to