>>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Amir> Well, after a long break, I've decided that we really ought to
Amir> have the reLyX distributed with LyX 1.0.2 support figures, since
Amir> that's the last remaining "major feature" (as determined by
Amir> yours truly) not currently supported.
In the minor feature department, did you add \lyxarrow for menu
separators?
Amir> Well, I've gotten \epsffile and \epsfbox to work. They're
Amir> equivalent, and they're left over from latex209. I just want to
Amir> make sure of what else I'll need to support.
The list looks pretty exhaustive. You could also try to translate the
raw \special{...} (don't know the syntax, sorry) which does the actual
file inclusion. I think the sybtax is in dvips manual.
Amir> My current plan is to completely ignore input bounding boxes,
Amir> since LyX always just figures it out from the ps file.
LyX does figure it just for displaying on screen. In LaTeX, the macros
also take care of bounding boxes automatically. However, the boudin
box parameters are here for the cases where the ps file is broken.
Amir> Hm. One problem. LyX doesn't support \includegraphics*, does it?
Amir> Which means it also doesn't support the "clip" option to
Amir> \epsfig. So do I not translate \epsfig, or do I just ignore the
Amir> option & hope they didn't want to clip? Or put it in as ERT if
Amir> there's a clip option? (I guess I could theoretically do the
Amir> same with graphicx \includegraphics. Parse the keys in the []
Amir> and use ERT if there are any unsupportable keys. It's just more
Amir> work.)
A solution could be to insert a note inset after the figure describing
what could not be translated. In general, annotating what could have
gone wrong could be interesting.
JMarc
