Re: localising IDL programs [message #85204 is a reply to message #85201] |
Fri, 12 July 2013 10:29   |
Andy Sayer
Messages: 127 Registered: February 2009
|
Senior Member |
|
|
Aha! The plot thickens. Your suggestion inspired me to open up the output postscript file in a text editor, and I found the place where the relevant bit of text is contained. IDL is writing code \341 there, which from before is the correct octal value for á. So that bit was right. I also found this page which shows that \341 is Æ in text encoding, but á in ISO Latin-1 encoding: http://www.math.u-bordeaux1.fr/~mleguebe/docs/gnuplot_liite3 4.pdf
So, I checked the IDL help and there is a keyword /isolatin1 to device. I set that, and it displays as intended.
Thanks,
Andy
On Friday, July 12, 2013 12:08:23 PM UTC-4, David Fanning wrote:
> AMS writes:
>
>
>
>> Ok, I fiddled around some more this morning but still can't get it working.
>
>>
>
>> I also tried using string("341B) which should be the octal representation for á in that font according to IDL documentation, but again get Æ. I have experimented but can't find any simple map between the symbol that ASCII tables tell me I should get for a given value, and the symbol I actually get when writing to postscript.
>
>>
>
>> Any thoughts?
>
>
>
> My only thought is that these values are almost *always* different in
>
> PostScript. See, for example, the contortions I have to go through to
>
> produce similar output on the display and in PostScript files in
>
> cgSymbol:
>
>
>
> http://www.idlcoyote.com/programs/cgsymbol.pro
>
>
>
> Cheers,
>
>
>
> David
>
> --
>
> David Fanning, Ph.D.
>
> Fanning Software Consulting, Inc.
>
> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
>
> Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|