Special characters in PostScript [message #63714] |
Tue, 18 November 2008 06:55  |
Bernhard Reinhardt
Messages: 26 Registered: October 2008
|
Junior Member |
|
|
Hi,
is it possible to print special charakters like umlaut vowels in a
simple way to postscript files?
I´ve read Davids article "How can I place a less-than-or-equal sign (≤)
in my PostScript output?". But that is to complicated for routine use.
Is there something like setting a variable at startup to "ISO 8859-1".
The worst thing I´d accept would be a string converter-function. Like
title=convert_special_chars('Viele Umlaute: üöüöäßß')
plot, TITLE=title
Does something like that exist? If not, I rather resign on these characters.
Best regards
Bernhard
|
|
|
|
|
|
Re: Special characters in PostScript [message #63857 is a reply to message #63714] |
Thu, 20 November 2008 07:14   |
R.Bauer
Messages: 1424 Registered: November 1998
|
Senior Member |
|
|
David Fanning schrieb:
> Bernhard Reinhardt writes:
>
>> David Fanning wrote:
>>> Bernhard Reinhardt writes:
>>>
>>>> Solved the problem. The workbench saves the files in UTF-8. After
>>>> setting the Text file encoding at Preferences->General-> Workspace to
>>>> ISO-8859-1 everything is fine.
>>> Are we talking about *graphical* output, or something else?
>> We are talking about a plot with a title.
>> Is that graphical output? Who knows?
>
> So, let me get this straight. To get a character with an umlat,
> say, in the title of my IDL plot, I have to change the encoding
> of the Workbench *editor*? Even for IDL, that seems too weird.
> Are you sure about this? Can you give me an example?
Hi David
yes it is true. I am not sure if an email to the news server has an
unicode (utf-8) encoding already.
plot,findgen(10),title='J�lich', chars=3
but however the � char changes in different encoding
and you have no chance to change the idl prompt. :(
cheers
Reimar
>
> Cheers,
>
> David
>
|
|
|
Re: Special characters in PostScript [message #63910 is a reply to message #63714] |
Fri, 21 November 2008 03:36  |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
Bernhard Reinhardt writes:
> My Workbench saved the .pro-files in UTF8. I don�t know what idl does
> when I execute them. My guess is that the idl-interpreter expects
> ISO-Encoded files and thus is messing up with the UFT8-Files.
>
> After setting the default to ISO. The � was broken in the Workbench,
> too. After I corrected this and saved the file it worked.
I have a feeling this subject is going to be a bit like
coordinates and map projections. Every once in awhile, you
feel like you *almost* understand it, only to see your
understanding shaken by the next example. :-(
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: Special characters in PostScript [message #63912 is a reply to message #63846] |
Fri, 21 November 2008 03:27  |
Bernhard Reinhardt
Messages: 26 Registered: October 2008
|
Junior Member |
|
|
David Fanning wrote:
> Reimar Bauer writes:
>
>> yes it is true. I am not sure if an email to the news server has an
>> unicode (utf-8) encoding already.
>>
>> plot,findgen(10),title='J�lich', chars=3
>>
>> but however the � char changes in different encoding
>>
>> and you have no chance to change the idl prompt. :(
>
> Maybe I am still misunderstanding something. I've
> typed this command with *several* different encoding
> changes in my Workbench and I see *absolutely* no
> difference in the graphical output. (Which is what
> I expected to see, actually.)
>
> Are you seeing something different? My output is
> "wrong", of course. A capital A with a tilde over
> it, followed by a 1/4 sign. But I can't see how
> changing the editor text encoding will help here.
My Workbench saved the .pro-files in UTF8. I don�t know what idl does
when I execute them. My guess is that the idl-interpreter expects
ISO-Encoded files and thus is messing up with the UFT8-Files.
After setting the default to ISO. The � was broken in the Workbench,
too. After I corrected this and saved the file it worked.
Regards
Bernhard
|
|
|