🚀 go-pugleaf

In <1992Dec17.172641.1584@gamelan> thf@zelator.in-berlin.de (Thomas Funke) writes:

>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 :(
>> 

>Same with german umlauts. Did someone manage to transform NeXT-RTF to PC-RTF ?  
>I believe it's not too difficult.

This is just one aspect of what some people like to call the "font 
encoding morass", a problem has has been around for some time but wasn't
particularly noticeable back when computers and/or their apps didn't talk
to each other much.  Now that they do the different encoding schemes cause
all sorts of trouble and you need all sorts of filters/translators (look
for example in the "utilities" provided by TeXMenu3.0 -- itself a great app
by the way --- where there are 5 or 6 such filters supplied.  The font
encoding problem is really a pain in the TeX world for a variety of 
reasons, not the least of which being that Knuth  did not use a uniform 
scheme when he first wrote the package.)  

I have a copy of a long descriptive post on this issue which appeared in 
comp.text.tex some months ago.  It dosn't offer specific solutions but does
make it somewhat clearer where the problems come from.  I'd be glad to 
E-mail a copy to anyone who wants it (reposting it in this somewhat 
inappropriate newsgroup seems a waste of bandwidth).

Tom