🚀 go-pugleaf

In article <eronald.724544541@ruble> eronald@fml.tuwien.ac.at (Edmund  
Ronald) writes:
>  I write. I write for a living. I write on my cube, when I can. Then I  
have
>  to hand the copy in to an editor.   Said (human :) editor sits in front 
>  of a PC. My text is usually in French, contains all these nice accents
>  which the french seem to need like salt and pepper.
> 
>   There is a DOS Ascii character set, and a Windows character set. 
> 
>   HOW THE HELL IS ONE SUPPOSED TO MOVE TEXT TO EITHER? 
>   AM I THE ONLY MAN IN THE WORLD WHO GETS ANGRY ABOUT THIS?
>   OH, YES, I KNOW ABOUT RTF. ON THE NEXT RTF MEANS NEXT_RTF :(
> 
>   ARGH.
> 
>  Edmund (who also happens to be a NeXT developper, but can't be  
bothered)


In NeXTSTEP 2.1, many of our customers and I were very surprised to see  
that a RTF file generated on a PC (with word for instance) or on a Mac was  
not properly handled by Edit, neither by WriteNow, neither by WordPerfect,  
although the RTF format contains an information on the charSet used (ansi,  
mac).
A solution for me was to quickly write a NS2.1 piece of software called  
RTFiltre.app which can translate PC/RTF and Mac/RTF, making the good  
character encoding translation to resolve that problem of accents. The  
file filtered is then correctly read by Edit, WN or WP. 
For RTFiltre.app, if the input is not an RTF file (say an ascii file), it  
uses a default conversion table that you can create yourself.
Soonly (if I have time), a NS3.0 RTFiltre.app will be able to export its  
NeXT/RTF for PC and Mac. Idem for exporting its special ascii files.

--
Eric Camps - Email/NeXTmail: ecamps@xlan.fdn.org
X&LAN, 2 rue du Colisee, 33000 Bordeaux, France
Voice: (+33) 56 51 04 89    Fax: (+33) 56 51 05 31