On Tue Jun 3 01:42:03 +0200 2025, [email protected] wrote:
> Thanks for the clarification. This makes me wonder if there are two
> different problems or perhaps the problem is caused earlier in the
> process. The plan9port version of page uses the gs on the native
> system, which in my case is version 10.04.0 (2024-09-18) running on
> macOS, while the Plan 9 page uses gs version 8.53 (2005-10-20).
> Looking closer, the error messages are somewhat similar (stack issue),
> but I can't tell. Another rabbithole left unexplored for future
> generations.
All of the pdf files and the jpg image in the repo Edouard linked
render just fine with page(1) on 9front. What doesn't is the document
generated by latexmk at the very end, and the problem there as you
have probably realized is the Cover.jpg image included in the document.
If you use imagemagick's convert(1) to covert that into a pdf first,
then change the \includepdf to use the new Cover.pdf, it works fine:
$ convert Cover.jpg Cover.pdf
$ ed main.tex
37c
\includepdf[pages=1, noautoscale=true]{Cover.pdf}
.
w
q
$ latexmk
Result: http://nopenopenope.net/up/main.pdf
I suggest we just do this.
Thanks all,
qwx
> On Mon, Jun 2, 2025 at 12:20 PM <[email protected]> wrote:
> >
> > On Mon, Jun 02, 2025 at 11:27:40AM -0700, Skip Tavakkolian wrote:
> > > Edouard, I tried viewing the main.pdf from your gitlab.com repo using
> > > page (9legacy/386 and p9p) and it exists with a "stack underflow"
> > > error. Searching for similar errors, it seems like it is due to the
> > > page command's inability to handle embedded images. I'm not sure if
> > > there's a workaround.
> > >
> >
> > The problem is gs(1) behind page. It is old and if something is using
> > transparency, for example, it can't handle it---and no: I don't
> > volunteer to update Ghostscript ;-) The question being in fact if
> > an intermediate step could not be a pdf library---the only thing
> > that may really need Ghostscript full capacities as a programming
> > language could be pic(1) (I haven't looked if it is the case) pic(1).
> >
> > I know that with kerTeX, John Hobby's MetaPost generates PostScript
> > but in fact it could be converted to PDF because the programming
> > capabilities (variables, flow control, conditionals and so on) are
> > handled by MetaPost itself. The result is a description of a fixed
> > image with few primitives.
> >
> > > On Mon, Jun 2, 2025 at 2:23?AM Edouard Klein <[email protected]> wrote:
> > > >
> > > > I'm the one to blame, it appears I've messed it up in more ways than
> > > > one. I've also had reports of breakage from other people directly by
> > > > email.
> > > >
> > > > My apologies. I integrated some post-conferences paper revisions without
> > > > checking the final document as I did for the printed version and this
> > > > was the cause of some of the issues.
> > > >
> > > > I've uploaded the source here:
> > > > https://gitlab.com/edouardklein/11thiwp9_proceedings
> > > > and will move it to shithub when I'll have an account.
> > > >
> > > > I'll try to correct some problems on my own, but please feel free to
> > > > chime in :)
> > > >
> > > > As Skip said, we'll use templates next year to make things easier for
> > > > everyone.
> > > >
> > > > [email protected] writes:
> > > >
> > > > >> you can't read it at all in page(1)
> > > > >
> > > > > how can we attract more plan 9 users to iwp9?
> > > > >
> > > > > sl
> >
> > --
> > Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
> > http://www.kergis.com/
> > http://kertex.kergis.com/
> > Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
------------------------------------------
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T273587b7cce74ef5-Mb0c94a6f690684462bf4c73e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
