Richard Heck wrote:
> Certainly it seems to be a mistake to use this same format for both
> purposes, even independently of this problem. So I'd say "yes". And
> "thank you".
I endorse that.
Jürgen
On 03/17/2013 03:54 PM, Georg Baum wrote:
Richard Heck wrote:
On 03/17/2013 01:05 PM, Jürgen Spitzmüller wrote:
Due to the existence of an OpenDocument > PDF converter (unoconv -f pdf
-- stdout $$i > $$o), the ps2pdf route fails for me in trunk. LyX tries
to go the route via odt instead of the
Richard Heck wrote:
> On 03/17/2013 01:05 PM, Jürgen Spitzmüller wrote:
>> Due to the existence of an OpenDocument > PDF converter (unoconv -f pdf
>> -- stdout $$i > $$o), the ps2pdf route fails for me in trunk. LyX tries
>> to go the route via odt instead of the preferred latex > dvi > ps > pdf
>
On 03/17/2013 01:05 PM, Jürgen Spitzmüller wrote:
Due to the existence of an OpenDocument > PDF converter (unoconv -f pdf --
stdout $$i > $$o), the ps2pdf route fails for me in trunk. LyX tries to go the
route via odt instead of the preferred latex > dvi > ps > pdf route.
Since we cannot yet pre
Due to the existence of an OpenDocument > PDF converter (unoconv -f pdf --
stdout $$i > $$o), the ps2pdf route fails for me in trunk. LyX tries to go the
route via odt instead of the preferred latex > dvi > ps > pdf route.
Since we cannot yet prevent that (AFAICS), I opt for removing this convert
