> > Oh, BTW, this has nothing to do with libpaper (I don't know why you > think it does, gs doesn't depend on libpaper, and has been reading > /etc/papersize before the existance of libpaper.) > > I do wonder if libpaper does a better job,
Yes it does ;-) That's its big advantage: centralize such bugs in one place so that we're sure all packages get fixed at once (who said I wanted to share features too? ;-)) > and I do wonder if gs really should read "A4 ". Some people were really > glad I added a wrapper to allow gs to read /etc/papersize. Some are > angry it didn't read "A4 ". Well, you never please them all! Can you try my gsfrontend.c in libpaper 0.3? It would be nice if you used it for these reasons: - people will benefit from new paper sizes immediately; - I think if something else than me provides a working package using libpaper, other package maintainers will start adopting it; - I won't have to overwrite your gs with my wrapper each time you make a new package ;-). If you use my wrapper (please, please...), I suggest installing the real gs as 'ghostscript' (a meaningfull name, no?) and the wrapper as 'gs' of course. Apparently people were confused by your gs-papersize being the gs that does not handle papersize despite its name. Yves. P.S.: I run this wrapper for some weeks now without problems.