| Re: localising IDL programs [message #73928] |
Thu, 09 December 2010 18:23  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
nata writes:
> Are you sure ? I still have problems with that link
Sheesh! I just finished a big image processing chapter
today. Still recovering, I guess. Too many celebratory
beers. :-)
Try this:
http://www.dfanning.com/template_books.html
> Could you send me a png or ps when you are going to
> publish your book ?
I'll do better than that. I'll send you a book. ;-)
Cheers,
David
P.S. 320 pages so far, and still three weeks to go
before I promised myself a first draft. There is a
chance I might make it if I don't have to do any
Christmas shopping! :-)
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: localising IDL programs [message #74006 is a reply to message #73928] |
Sun, 12 December 2010 18:54  |
wallabadah
Messages: 28
Registered: November 2005
|
Junior Member |
|
|
On Dec 10, 1:23 pm, David Fanning <n...@dfanning.com> wrote:
> nata writes:
>> Are you sure ? I still have problems with that link
>
> Sheesh! I just finished a big image processing chapter
> today. Still recovering, I guess. Too many celebratory
> beers. :-)
>
> Try this:
>
> http://www.dfanning.com/template_books.html
>
>> Could you send me a png or ps when you are going to
>> publish your book ?
>
> I'll do better than that. I'll send you a book. ;-)
>
> Cheers,
>
> David
>
> P.S. 320 pages so far, and still three weeks to go
> before I promised myself a first draft. There is a
> chance I might make it if I don't have to do any
> Christmas shopping! :-)
>
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
Thanks for the great responses, using the lookup table approach
appears to have solved the problem.
cheers,
Will.
|
|
|
|
| Re: localising IDL programs [message #85184 is a reply to message #74006] |
Thu, 11 July 2013 10:47 |
Andy Sayer
Messages: 127
Registered: February 2009
|
Senior Member |
|
|
Hi all,
Apologies for bumping an old thread, but I have a similar issue. The lookup table given in previous posts works great for screen output. But, I am having odd behaviour when I try to write to eps output. Specifically, rather than á, 225B gives me Æ (which should be 198B). 198B gives a breve accent. So it doesn't appear to be a swapping of just those two characters, but a different mapping.
Is there some alternate mapping/wizardry I need to do to make it work on eps output? I like to use device,/times and have tested e.g. courier but it gives the same behaviour.
This is using IDL 7.1.1 on a CentOS machine, in case it makes a difference. Any suggestions would be appreciated! I did a Google search and search on this group, but this thread was closest I found to the answer.
Thanks,
Andy
On Sunday, December 12, 2010 9:54:13 PM UTC-5, wallabadah wrote:
> On Dec 10, 1:23 pm, David Fanning <n...@dfanning.com> wrote:
>> nata writes:
>>> Are you sure ? I still have problems with that link
>>
>> Sheesh! I just finished a big image processing chapter
>> today. Still recovering, I guess. Too many celebratory
>> beers. :-)
>>
>> Try this:
>>
>> http://www.dfanning.com/template_books.html
>>
>>> Could you send me a png or ps when you are going to
>>> publish your book ?
>>
>> I'll do better than that. I'll send you a book. ;-)
>>
>> Cheers,
>>
>> David
>>
>> P.S. 320 pages so far, and still three weeks to go
>> before I promised myself a first draft. There is a
>> chance I might make it if I don't have to do any
>> Christmas shopping! :-)
>>
>> --
>> David Fanning, Ph.D.
>> Fanning Software Consulting, Inc.
>> Coyote's Guide to IDL Programming:http://www.dfanning.com/
>> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
>
> Thanks for the great responses, using the lookup table approach
> appears to have solved the problem.
>
> cheers,
>
> Will.
|
|
|
|
| Re: localising IDL programs [message #85200 is a reply to message #85184] |
Fri, 12 July 2013 09:03 |
Andy Sayer
Messages: 127
Registered: February 2009
|
Senior Member |
|
|
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?
Andy
On Thursday, July 11, 2013 1:47:33 PM UTC-4, AMS wrote:
> Hi all,
>
>
>
> Apologies for bumping an old thread, but I have a similar issue. The lookup table given in previous posts works great for screen output. But, I am having odd behaviour when I try to write to eps output. Specifically, rather than á, 225B gives me Æ (which should be 198B). 198B gives a breve accent. So it doesn't appear to be a swapping of just those two characters, but a different mapping.
>
>
>
> Is there some alternate mapping/wizardry I need to do to make it work on eps output? I like to use device,/times and have tested e.g. courier but it gives the same behaviour.
>
>
>
> This is using IDL 7.1.1 on a CentOS machine, in case it makes a difference. Any suggestions would be appreciated! I did a Google search and search on this group, but this thread was closest I found to the answer.
>
>
>
> Thanks,
>
>
>
> Andy
>
>
>
>
>
> On Sunday, December 12, 2010 9:54:13 PM UTC-5, wallabadah wrote:
>
>> On Dec 10, 1:23 pm, David Fanning <n...@dfanning.com> wrote:
>
>>> nata writes:
>
>>>> Are you sure ? I still have problems with that link
>
>>>
>
>>> Sheesh! I just finished a big image processing chapter
>
>>> today. Still recovering, I guess. Too many celebratory
>
>>> beers. :-)
>
>>>
>
>>> Try this:
>
>>>
>
>>> http://www.dfanning.com/template_books.html
>
>>>
>
>>>> Could you send me a png or ps when you are going to
>
>>>> publish your book ?
>
>>>
>
>>> I'll do better than that. I'll send you a book. ;-)
>
>>>
>
>>> Cheers,
>
>>>
>
>>> David
>
>>>
>
>>> P.S. 320 pages so far, and still three weeks to go
>
>>> before I promised myself a first draft. There is a
>
>>> chance I might make it if I don't have to do any
>
>>> Christmas shopping! :-)
>
>>>
>
>>> --
>
>>> David Fanning, Ph.D.
>
>>> Fanning Software Consulting, Inc.
>
>>> Coyote's Guide to IDL Programming:http://www.dfanning.com/
>
>>> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
>
>>
>
>> Thanks for the great responses, using the lookup table approach
>
>> appears to have solved the problem.
>
>>
>
>> cheers,
>
>>
>
>> Will.
|
|
|
|
|
|
| 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.")
|
|
|
|
| Re: localising IDL programs [message #85205 is a reply to message #85204] |
Fri, 12 July 2013 10:36 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
AMS writes:
> 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.
There you go, mystery solved.
Now you see why every time someone so much as touches a Coyote Graphics
command the PostScript device gets configured with COLOR=1,
BITS_PER_PIXEL=8, and /ISOLATIN1. Saves a LOT of problems later on. :-)
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.")
|
|
|
|
| Re: localising IDL programs [message #85207 is a reply to message #85205] |
Fri, 12 July 2013 11:29 |
Andy Sayer
Messages: 127
Registered: February 2009
|
Senior Member |
|
|
Heh. Yeah, I had not known of/had to use /isolatin1 before.
On Friday, July 12, 2013 1:36:22 PM UTC-4, David Fanning wrote:
> AMS writes:
>
>
>
>> 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.
>
>
>
> There you go, mystery solved.
>
>
>
> Now you see why every time someone so much as touches a Coyote Graphics
>
> command the PostScript device gets configured with COLOR=1,
>
> BITS_PER_PIXEL=8, and /ISOLATIN1. Saves a LOT of problems later on. :-)
>
>
>
> 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.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
