comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: weird font issue: string("305B) does not work any more?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: weird font issue: string("305B) does not work any more? [message #61147] Sun, 06 July 2008 18:37
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
biophys writes:

> 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=3D0 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=3D-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).

I would say it is a minor miracle that it works with
True Type fonts at all, and you would be pushing your
luck to expect more. Sounds like you found the
work-around. :-)

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.")
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 Go to previous message
biophys is currently offline  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.")
Re: weird font issue: string("305B) does not work any more? [message #61155 is a reply to message #61149] Sun, 06 July 2008 07:09 Go to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
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.")
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Getting mean from HDF SD files - stack in envi or read into IDL array?
Next Topic: Failed Launching IDLDE 7.0 after CentOS upgrade

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 17:47:14 PDT 2025

Total time taken to generate the page: 0.00496 seconds