Re: Missing items to make Cairo ready

[Jonas Hahnfeld]

On Sat, 2023-01-07 at 22:05 +0100, Jean Abou Samra wrote:
> Le 07/01/2023 à 21:53, Jonas Hahnfeld a écrit :
> > Furthermore, I'm not a fan of recommending two different ways of
> > creating PDFs to users (once directly via Cairo and once with ps2pdf),
> > unless we really, really have to.
> 
> We don't really, really have to, but the advantage of dropping \epsfile
> and \postscript isn't big either, as their Cairo implementation is not
> complicated and can largely share code with the implementation of
> other image formats. It may also be useful for people who still use
> the PS/EPS output directly and not PDF output (there probably aren't
> many for PS, but EPS might be a bit more common?).

That's not really my point; if we keep markup commands that only work
via this very specific ps2pdf conversion, we have to guarantee that
users get the same visual output as direct PDF output. Do we want to
support this? Does Cairo guarantee this for all possible cases that we
run into? I highly doubt this is a good rabbit hole to go into...

If we don't do that the error text of \epsfile and \postscript in the
default PDF mode has to be "please use this ps2pdf conversion (which we
don't even ship with our binaries), and by the way, your PDF will look
different". That sounds horrible.

signature.asc
Description: This is a digitally signed message part