Re: weird font issue: string("305B) does not work any more? [message #61149 is a reply to message #61147] |
Sun, 06 July 2008 16:30   |
biophys
Messages: 68 Registered: July 2004
|
Member |
|
|
Hi, David
Thanks for the comments. It simply doesn't work for both Hershey
Vector fonts or True Type fonts. Maybe I should not mention the !
p.font=0 case which is kinda irrelevant. So to clarify a bit, here's
what works on a linux box but not on my windows xp.
____________________________________________________________ ____
IDL>set_plot,'win'
IDL>!p.font=-1
IDL> XYOUTS,.1, .5, '!3Angstrom symbol:'+STRING("305B), /NORM
____________________________________________________________ ____
It should just work according to the font section of the appendices of
IDL API References Guide. And my current work around is to change
STRING("305B) into !Z(00c5).
bp
On Jul 6, 7:09 am, David Fanning <n...@dfanning.com> wrote:
> biophys writes:
>> It's been a long time since last time I used something like
>> string("305B) to get these special characters. However, this time it
>> doesn't work for me on a windows machine with direct graphics. If I
>> use
>
>> IDL>!p.font=-1 & XYOUTS,.1, .5, '!3Here is an Angstrom symbol: ' +
>> STRING("305B), /NORM, CHARSIZE=3
>> or
>> IDL>!p.font=1 & XYOUTS,.1, .5, '!3Here is an Angstrom symbol: ' +
>> STRING("305B), /NORM, CHARSIZE=3
>
>> the angstrom does not show up.
>
> As far as I know this has never worked with direct graphics
> and hardware fonts. In fact, I don't see how it could.
>
> Cheers,
>
> David
>
> --
> 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.")
|
|
|