Hi Philipp,
Le 8 janv. 09 à 10:47, Philipp Lohmann a écrit :
Hi all,
for various reasons we (hdu and me in this case) would like to move
the code now residing in psprint into vcl.
That's a good idea.
reasons to do so:
- font subsetting code is in psprint and on many platforms linked
statically into vcl anyway.
- future CUPS versions will migrate from PostScript to PDF as their
primary spool file format. moving psprint to vcl will make it
easier to do this migration in OOo, too.
- vcl is psprint's only customer anyway.
- there is code duplication between psprint and vcl currently that
can be removed after this changed.
All are good reasons, and simplify cannot be bad.
However this will mean there will be a CWS that will make this
migration and changes to psprint in other CWS will be moot (see the
discussion about svn not warning about committing to moved files).
So consider yourself warned that we will announce a time at which
no changes to psprint should be made until a certain CWS is
integrated (not that there are that many people doing that
anyway :-) )
Noticed :)
At the same time we could do a little cleanup and first thing
coming to mind is the MACOSX specific code which could be removed.
That would however mean that the old MacOSX X11 port would not
really work anymore (at least WRT to printing). So I want to ask:
do we really continue to have the X11 Mac port in the 3.0 line ?
Are there any compelling arguments for this ?
AFAIK, nobody works on maintain X11 (not only printing) version on
Mac, and nobody will complain. And to be honest, I think 2.4.3 (I
still continue to believe maxleofix4x11 will be integrated a day) is
the very last version to have X11 working, and I agree to no longer
support it in 3.x line.
So : +1 from me for your proposal
Kind regards,
Eric
P.S. : any news for an ATSUI replacement ? IMHO, Apple should provide
something soon, no ?
--
qɔᴉɹə
