Re: 3.6.1 produces eps files that are unusable on Debian wheezy

[Daniel J Sebald]

On 03/03/2012 04:32 PM, Daniel J Sebald wrote:
> On 03/03/2012 03:59 PM, Mike Miller wrote:
> > Dmitri, thanks for testing this.
> [snip]
[snip]
> > > But I do think that octave should setup some reasonable default.
> >
> > Definitely, otherwise octave cannot build docs from a clean hg source
> > on my system. This is how I first ran into this problem, part of the
> > build uses octave to generate png files for the docs, that stage of
> > the build is continually failing for me, I have to "make -i" in the
> > doc directory to finish the build.
>
> I second that sentiment. There's no such font as {} and a PostScript
> file should be self-consistent.
>
> I think the easiest thing for Mike to do right now, until a fix works it
> way through upgrades, is to simply add a line like:
>
> set(0, 'defaultaxesfontname', 'Helvetica')
>
> inside his Octave startup script file, using the font of his choice for
> consistency with the rest of the text. That should produce EPS files
> without missing fonts (if you have the specified font on your system).

BTW, I'd like to point out that this is why I like having the 
combination PostScript/LaTeX option as part of Octave.  Being able to 
compile the text under LaTeX means that the same fonts are used in the 
figures as well as text, and when it is all compiled the fonts 
themselves can be easily embedded inside the document.

I even found the Xfig output to be useful the other day, but I think 
that needs some tweaking inside Octave because Xfig is an allowable 
color terminal and the output ended up with lines of all different 
colors which I then manually changed.  (Can be done inside Xfig or on 
the ascii file itself.)  Then Xfig has the PS/LaTeX option, etc.

Dan