| Re: non-English language [message #83503 is a reply to message #83435] |
Thu, 07 March 2013 14:24   |
![DavidF[1] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "DavidF[1] is currently offline")
DavidF[1]
Messages: 94
Registered: April 2012
|
Member |
|
|
On Thursday, March 7, 2013 3:10:43 PM UTC-7, Katya wrote:
> Hi Chris, "showfont, 16, 'Russian'" shows me a table with Russian letters and when I'm trying to use this font for postscript output it does print Russian letters but in some chaotic meaningless way... =( David posted a link above about Cyrillic encoudings, maybe this is the case. Also, I've noticed that Russian symbols are two-bytes, for exapmle,
>
> print, byte('щ')
>
> 209 137
>
> so, it seems that IDL looks for a symbol in ASCII table according to the first byte. But I don't really inderstand what this means :D. I've just noticed that syboles with the same first byte are printed as the same unreadable symbol a-la 'Ñ'.
I think the UNICODE method could actually work, although it seems enormously labor intensive. If you had a font with UNICODE Cyrillic letters (and I think it is fairly easy to find one), you could probably write a "translator function" that could convert your letters to the proper Unicode values, which *ought* to work in PostScript in both direct graphics and object graphics.
Maybe this is not so hard. A table of letters and a table of values, wrapped in the appropriate way so IDL will understand it is UNICODE.
Cheers,
David
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
