comp.lang.idl-pvwave archive: archive » Re: ps/eps ouput from object graphic

Home » Public Forums » archive » Re: ps/eps ouput from object graphic

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: ps/eps ouput from object graphic [message #48504]

Thu, 27 April 2006 17:23

Karl Schultz
Messages: 341
Registered: October 1999

Senior Member

On Thu, 27 Apr 2006 09:44:42 -0600, David Fanning wrote:

> David Fanning writes:
>
>> In 30 minutes of fooling around, the only way I could
>> get an epsilon symbol so far is like this:
>>
>> xobjview,obj_new('IDLgrText',Enable_Formatting=1,'!4' + String(101B), $
>> font=obj_new('idlgrfont', name='hershey'))
>>
>> Something here is not quite right. :-(
>
> Well, progress of sorts. I try this command:
>
> xobjview,obj_new('IDLgrText',font=obj_New('idlgrfont', name='symbol'), $
> enable_formatting=1, "!Z('65'x)")
>
> And I get a nice epsilon symbol along with all sorts of garbage:
>
> IDL> xobjview,obj_new('IDLgrText',font=obj_New('idlgrfont',
> name='symbol'), enable_formatting=1, "!Z('65'x)")
> IDLGRSRCDEST::GETTEXTDIMENSIONS: Select Charmap failure (Encoding:
> 0x756e6963) (FreeType error info: (6) invalid argument).
> IDLGRSRCDEST::GETTEXTDIMENSIONS: Select Charmap failure (Encoding:
> 0x756e6963) (FreeType error info: (6) invalid argument).
> IDLGRSRCDEST::DRAW: Select Charmap failure (Encoding: 0x756e6963)
> (FreeType error info: (6) invalid argument).
> IDLGRSRCDEST::DRAW: Select Charmap failure (Encoding: 0x756e6963)
> (FreeType error info: (6) invalid argument).
>
> Help!

I fixed a bug almost exactly like this back around IDL 6.1. I think that
the only difference was the character code. That bug happened with a
bigger character code (> 255). The Symbol font has been a bit problematic
for us because it is pretty old and doesn't have a Unicode table in it, or
something along those lines. The larger char code caused an access past
the end of the font table. Apparently, the fix made back then took care
of the big char code problem, but IDL still tries to use unicode encoding
to access the symbol font. I'll file a bug report, but your workaround
for the meantime is to avoid using unicode encoding to access the symbol
font, as you seem to have worked out. You shouldn't need unicode to do it
anyway, since the font doesn't have enough glyphs in it to require unicode.

Karl

Report message to a moderator

[Message index]

		Re: ps/eps ouput from object graphic By: Karl Schultz on Thu, 27 April 2006 17:23
		Re: ps/eps ouput from object graphic By: David Fanning on Thu, 27 April 2006 10:19
		Re: ps/eps ouput from object graphic By: David Fanning on Thu, 27 April 2006 09:42
		Re: ps/eps ouput from object graphic By: David Fanning on Thu, 27 April 2006 09:27
		Re: ps/eps ouput from object graphic By: David Fanning on Thu, 27 April 2006 09:09
		Re: ps/eps ouput from object graphic By: David Fanning on Thu, 27 April 2006 08:44
		Re: ps/eps ouput from object graphic By: David Fanning on Thu, 27 April 2006 08:17
		Re: ps/eps ouput from object graphic By: btt on Thu, 27 April 2006 07:58
		Re: ps/eps ouput from object graphic By: David Fanning on Thu, 27 April 2006 07:18
		Re: ps/eps ouput from object graphic By: btt on Thu, 27 April 2006 06:58
		Re: ps/eps ouput from object graphic By: snfinder@naver.com on Thu, 27 April 2006 06:01
		Re: ps/eps ouput from object graphic By: btt on Thu, 27 April 2006 05:37

Previous Topic:	ps/eps ouput from object graphic
Next Topic:	Saving the IDL terminal datastream

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 13:58:04 PDT 2025

Total time taken to generate the page: 0.00449 seconds