|
From: Juergen W. <wie...@fr...> - 2005-07-05 19:01:41
|
Harald Harders wrote: > If I remember correctly, the low byte of UTF-8 is identical with either > latin1 or latin9. Thus, using =BBset encoding iso_8859_1=AB should also w= ork > with UTF-8 (and in fact it worked for me today at work) as long as you > don't use characters above \377. But aren't the umlauts "=E4=F6=FC" multibyte characters in UTF-8? This is at least what hexdump says to sample files. And I can say empirically that it doesn't work to just use UTF-8 scripts containing umlauts with gnuplot -- at least with SuSE9.3. > > So my question: Is it possible to add UTF to "set encoding"? At > > least for the postscript terminal? What does the postscript > > standard say about UTF? > > Postscript can only handle 255 characters per font encoding. Thus, it does > not work with UTF-8. It may be possible to add a second and third encoding > that contains the encoding vectors for UTF-8 fonts. Thus, 255 characters > will be put into one font. E.g., /Times-Roman, /Times-Roman-1, > /Times-Roman-2. But this is just theoretical, not yet implemented in > gnuplot. Oh dear. I have spent so much time on all this font/encoding stuff. And I still feel like a complete beginner. But thank all of you for your explanations. Juergen |