| EPS fragment output for latex font interpretation? [message #54942] |
Wed, 25 July 2007 02:42  |
Gernot Hassenpflug
Messages: 18
Registered: April 2001
|
Junior Member |
|
|
Hello all,
I have used IDL to output EPS figures with whatever fonts IDL has
built-in. Now I would like to use IDL to output EPS fragments (in
vector format) with markers for the text information, and .tex files
containing the text corresponding to the markers, with both files to
be later interpreted by LaTeX with an \input statement. With matlab,
which I do not currently have a licence to, this was possible using
the user-contributed laprint program.
With such a splitting of the tasks, it is easy to adjust text size and
font to what is required in the LaTeX document.
Is there any way to do such a task in IDL (I have 6.2 and 6.3 licences
at my workplace).
Alternatively, if there is a way to use Computer Modern fonts with
IDL, I could try to use those in the EPS file directly (then output in
binary format is fine too).
Many thanks
Gernot
--
BOFH excuse #433:
error: one bad user found in front of screen
|
|
|
|
| Re: EPS fragment output for latex font interpretation? [message #54991 is a reply to message #54942] |
Fri, 27 July 2007 13:42  |
George N. White III
Messages: 56
Registered: September 2000
|
Member |
|
|
On Wed, 25 Jul 2007, Paolo_Grigis wrote:
>
>
> [...]
>>
>> Ah, yes, understood. In that case of course the fonts are now fixed,
>> no longer modifiable by the document, as I understand it. But I think
>> you are incorrect in one aspect: IDL produced an EPS file when you
>> gave it the /encapsulated modifier for the device.
>
> Yes, sure, IDL does that, but it was the *dvips* output
> that I converted into eps in the last step.
Is there are reason to avoid "dvips -E" to get eps directly? Some
files may get incorrect bounding boxes, but that can easily be
rectified using ghostscript's bbox device and a wee smidgeon of
perl or IDL code to update the value dvips added to the file.
--
George N. White III <aa056@chebucto.ns.ca>
|
|
|
|
| Re: EPS fragment output for latex font interpretation? [message #55016 is a reply to message #54942] |
Thu, 26 July 2007 08:09 |
Gernot Hassenpflug
Messages: 18
Registered: April 2001
|
Junior Member |
|
|
Paolo_Grigis <pgrigis@astro.phys.ethz.ch> writes:
> [...]
>>
>> Ah, yes, understood. In that case of course the fonts are now fixed,
>> no longer modifiable by the document, as I understand it. But I think
>> you are incorrect in one aspect: IDL produced an EPS file when you
>> gave it the /encapsulated modifier for the device.
>
> Yes, sure, IDL does that, but it was the *dvips* output
> that I converted into eps in the last step.
Ha, asleep at the wheel! :-)
I ma also happy to note that although the axis marks are in the system
font, they too can be accessed using the (non-unique in this case)
string, "0", "1" or whatever. I cannot seem to find the way to set the
axis marks to a user-defined set of labels, but that is indeed
possible I remember. So I can get complete customization of the graph
labels.
Thanks once again,
Gernot
--
Gernot Hassenpflug
|
|
|
|
| Re: EPS fragment output for latex font interpretation? [message #55034 is a reply to message #54942] |
Wed, 25 July 2007 09:23 |
Paolo Grigis
Messages: 171
Registered: December 2003
|
Senior Member |
|
|
[...]
>
> Ah, yes, understood. In that case of course the fonts are now fixed,
> no longer modifiable by the document, as I understand it. But I think
> you are incorrect in one aspect: IDL produced an EPS file when you
> gave it the /encapsulated modifier for the device.
Yes, sure, IDL does that, but it was the *dvips* output
that I converted into eps in the last step.
Ciao,
Paolo
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
