[dvipdfmx] Fw: Re: [tex-k] dvipdfmx: Apparent bug

[Laurence Finston]

No, sorry, my mistake:  The current version works (see attachment).  I forgot to use the -r 300 option last time.

Thanks.  Now I just have to get it configured properly.

Laurence

> Gesendet: Dienstag, 10. Mai 2022 um 02:06 Uhr
> Von: "Laurence Finston" <Laurence.Finston at gmx.de>
> An: "Akira Kakuto" <kakuto at jcom.zaq.ne.jp>
> Cc: dvipdfmx at tug.org
> Betreff: Aw: Re: [dvipdfmx] Fw: Re: [tex-k] dvipdfmx: Apparent bug
>
> The result is just the same (see attachment).
>
>  2163 rsync -a --delete --exclude=.svn tug.org::tldevsrc/Build/source .
>  2165  cd source/
>  2168  ./Build
>  ...
>  2175  cd x86_64-pc-linux-gnu/
>
>  In [...]/source/inst/bin/x86_64-pc-linux-gnu
>
>  2177  ./dvipdfmx --version
> -->
> This is dvipdfmx Version 20211117 by the DVIPDFMx project team,
> modified for TeX Live,
> an extended version of dvipdfm-0.13.2c developed by Mark A. Wicks.
>
> Copyright (C) 2002-2021 the DVIPDFMx project team
> Copyright (C) 2006-2021 SIL International.
>
> It didn't work to call this version of dvipdfmx from the directory where I had my sources (I did use
> the full path).
> The files glyphlist.txt, pdfglyphlist.txt and dvipdfmx.cfg weren't found.
> It may have been possible to do this a different way but I just found them and copied them to the
> [...]/x86_64-pc-linux-gnu/.
>
> The TFM file for the `ttemp' was then not found (of course) so I copied it and in fact all of the `ttemp*' files
> to the same directory, although probably only the pk files were needed in addition, and of course ttemp.dvi.
>
> I'm sure there's a way to configure things so that it would work but I didn't really want to get into this at the present time as I just wanted to submit a bug report (and hopefully get things to work).
>
> It was not clear to me how it would be possible to build dvipdfmx without building TeXLive as a whole.  I suppose this might have been possible but it didn't leap out at me and it doesn't seem to be what's intended by the developers.  I don't mean any disrespect, but it does seem like a substantial hurdle for just updating one program.
>
> Thanks,
>
> Laurence
>
> > Gesendet: Dienstag, 10. Mai 2022 um 01:00 Uhr
> > Von: "Akira Kakuto" <kakuto at jcom.zaq.ne.jp>
> > An: "Laurence Finston" <Laurence.Finston at gmx.de>, dvipdfmx at tug.org
> > Betreff: Re: [dvipdfmx] Fw: Re: [tex-k] dvipdfmx: Apparent bug
> >
> > On 2022/05/10 7:10, Laurence Finston wrote:
> > > This is the version I'm using:
> > >
> > > dvipdfmx --version
> > > This is dvipdfmx Version 20190824 by the DVIPDFMx project team,
> > > modified for TeX Live,
> > > an extended version of dvipdfm-0.13.2c developed by Mark A. Wicks.
> > >
> > > Copyright (C) 2002-2019 the DVIPDFMx project team
> > > Copyright (C) 2006-2019 SIL International.
> >
> > Please try a version in the TeX Live 2022:
> >
> > This is dvipdfmx Version 20211117 by the DVIPDFMx project team,
> > modified for TeX Live,
> > an extended version of dvipdfm-0.13.2c developed by Mark A. Wicks.
> >
> > Copyright (C) 2002-2021 the DVIPDFMx project team
> > Copyright (C) 2006-2021 SIL International.
> >
> > Thanks,
> > Akira
> >
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ttemp.pdf
Type: application/pdf
Size: 14561 bytes
Desc: not available
URL: <https://tug.org/pipermail/dvipdfmx/attachments/20220510/fa16f19f/attachment-0001.pdf>