March 2007 - ntg-pdftex - NTG Mailing Lists

Re: [NTG-pdftex] [tex-live] Debian TeX -- new packages
by Taco Hoekwater 02 Apr '07

02 Apr '07

Hi, From a discussion on TeX-Live with regard to the debian texlive packages for texlive and the complications raised by libpoppler: Sanjoy Mahajan wrote: > [What I describe below is not a Debian problem, but the proposed > change would make the packages easier for Ubuntu users to use. > > I added dev-context to the CC: list since the pkg deps affect Ubuntu > users -- e.g. me -- who use your excellent ConTeXt packages.] > > I'm using Ubuntu 6.10 (edgy) with all your tug.org stanzas. An > "apt-get install texlive-base-bin" or "apt-get install context" fails > when going from the TL2005 packages to the 2007 ones. The blocking > package is texlive-base-bin: > > # apt-get install texlive-base-bin > texlive-base-bin: > Depends: libpng12-0 (>= 1.2.13-4) but 1.2.8rel-5.1ubuntu0.1 is to be installed > Depends: libpoppler0c2 (>= 0.4.2) but it is not installable > E: Broken packages > > I'll upgrade to the Ubuntu 7.04 beta, which will solve the libpng12-0 > problem because Ubuntu 7.04 uses libpng 1.2.15. But libpoppler0c2 > would still be missing. Here are the libpoppler pkgs in versions of If I understand that thread correctly, the use of poppler instead of xpdf is now really a requirement on both debian and ubuntu? And you cannot share the binary packages between the various linuxes because there are packaging differences that cannot be resolved, at all? And that there are different versions of (dynamic) libpoppler that are mutually exclusive, even at compile-time? But at the same time, static binaries with xpdf linked in are not usable or 'not done' for some reason? If this is a sign of things to come, I may have to reconsider switching to MacOSX or freebsd. Taco

6 12

buf-size
by Hans Hagen 31 Mar '07

31 Mar '07

Hi, It seems that the buffer size of pdftex is maximized to 300K while in practice much larger files show up (at least here); for instance xml files can be 1 meg one-liners. Is it possible to set the max to (say) 10.000.000? (tex.web) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

6 9

[ pdftex-Bugs-747 ] \letterspacefont and \pdffontexpand, again
by noreply＠sarovar.org 31 Mar '07

31 Mar '07

Bugs item #747, was opened at 2007-03-09 03:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=747&group_id=106 Category: hz Group: v1.40.1 Status: Open Resolution: Accepted Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: \letterspacefont and \pdffontexpand, again Initial Comment: When expanding a letterspaced font, the base font will be expanded, too, resulting in the error `font has been expanded with different parameters' when the base font is expanded again: \letterspacefont\lsfont\font 100 \pdffontexpand\lsfont 20 20 5 autoexpand \pdffontexpand\font 20 20 5 autoexpand Z\bye ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-03-31 09:52 Message: Logged In: YES user_id=710 either name is ok with me. We need a new pritimive to load a new font and expand it, since the current one doesn't load a new font and hence is making trouble. I would wait for a while to see how Robert sees it before making any change. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2007-03-19 11:07 Message: Logged In: NO Hello, I do not think that \pdfexpandfont is a good name for a new primitive, as it is too easy to confuse with \pdffontexpand. What about \pdfexpandnewfont, as -- if I understand correctly -- a new font is loaded? Jonathan P.S: Thank you for creating pdfTeX! ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-03-10 20:18 Message: Logged In: YES user_id=710 Phil Taylor has a suggestion that seems great to me: introduce a new primitive \pdfexpandfont instead. How do you see it? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-10 19:24 Message: Logged In: YES user_id=421 Forget that comment. Of course a change of \pdffontexpand has to be considered carefully. By you. :-) ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-10 19:22 Message: Logged In: YES user_id=421 No. It's an undocumented primitive. ;-) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-03-09 17:28 Message: Logged In: YES user_id=710 sigh. A mistake when implementing the \pdffontexpand primitive: it should load a new font for expansion, instead of expanding a loaded font. Too late for change now? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=747&group_id=106

1 0

Re: [NTG-pdftex] [tex-live] buf-size
by Akira Kakuto 30 Mar '07

30 Mar '07

Hi Karl, > For regular old tex, ie, TL's Build/source/texk/web2c/tex.ch, I tacked > on a couple of zeros to sup_buf_size: > @!sup_buf_size = 30000000; > > Martin, can you make the analogous change for pdftex please? > (Assuming you have no objection.) > > Jonathan, if buf_size is still relevant in xetex-land, you may as well > do it too? Your change may automatically be reflected to pdftex and xetex. luatex has its own large value: @!sup_buf_size = 100000000; But you have to change com16bit-rc2.ch for aleph and com16bit.ch for omega. Best regards, Akira

1 0

Which is the right way of sending messages to this list?
by Javier Múgica de Rivera 29 Mar '07

29 Mar '07

I have reviewed the march archive of messages and my message was obviously sent in a different way. I simply send the message to ntg-pdf at ntg.nl. How should one proceed in order that my message apear as (say) a feature request? Thanks, Javier

1 0

\expandaftern and other
by Javier Múgica de Rivera 22 Mar '07

22 Mar '07

1 0

[ pdftex-Bugs-747 ] \letterspacefont and \pdffontexpand, again
by noreply＠sarovar.org 19 Mar '07

19 Mar '07

Bugs item #747, was opened at 2007-03-09 08:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=747&group_id=106 Category: hz Group: v1.40.1 Status: Open Resolution: Accepted Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: \letterspacefont and \pdffontexpand, again Initial Comment: When expanding a letterspaced font, the base font will be expanded, too, resulting in the error `font has been expanded with different parameters' when the base font is expanded again: \letterspacefont\lsfont\font 100 \pdffontexpand\lsfont 20 20 5 autoexpand \pdffontexpand\font 20 20 5 autoexpand Z\bye ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2007-03-19 16:37 Message: Logged In: NO Hello, I do not think that \pdfexpandfont is a good name for a new primitive, as it is too easy to confuse with \pdffontexpand. What about \pdfexpandnewfont, as -- if I understand correctly -- a new font is loaded? Jonathan P.S: Thank you for creating pdfTeX! ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-03-11 01:48 Message: Logged In: YES user_id=710 Phil Taylor has a suggestion that seems great to me: introduce a new primitive \pdfexpandfont instead. How do you see it? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-11 00:54 Message: Logged In: YES user_id=421 Forget that comment. Of course a change of \pdffontexpand has to be considered carefully. By you. :-) ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-11 00:52 Message: Logged In: YES user_id=421 No. It's an undocumented primitive. ;-) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-03-09 22:58 Message: Logged In: YES user_id=710 sigh. A mistake when implementing the \pdffontexpand primitive: it should load a new font for expansion, instead of expanding a loaded font. Too late for change now? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=747&group_id=106

1 0

[ pdftex-Patches-746 ] Patch PromptFileName
by noreply＠sarovar.org 10 Mar '07

10 Mar '07

Patches item #746, was opened at 2007-03-07 17:41 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=746&group_id=106 >Category: User interaction >Group: v1.40.0 Status: Open >Resolution: Postponed Priority: 5 Submitted By: Heiko Oberdiek (oberdiek) >Assigned to: Martin Schröder (oneiros) Summary: Patch PromptFileName Initial Comment: Subject: Patch PromptFileName Date: 2007/03/07 Author: Heiko Oberdiek The patches are based on pdfTeX 1.40.3 There is some discussion in the tex-live list: List: tex-live(a)tug.org Date: March 2007 Subject: Bug in TexLive 2005 and 2007? Non-writable aux-file If TeX asks for a file name, what action should be taken, if the user doesn't provide a file name? The current behaviour has changed from Web2C 7.5.2 to 7.5.6 and is quite impredictible: * Append some default extension if file extension is not given. * Use previous file name part, if this part is empty. Sometimes this behaves as "retry action" by chance, sometimes a source file gets overwritten. Two patches are provided that implement alternative actions: * Retry.diff If the user doesn't specify a file name, then the whole previous file name is used including the area and extension parts. * Abort.diff If the user doesn't specify a file name, then the job is aborted. Unhappily Ctrl-C (or Ctrl-D) have only a retarded effect after the file name is used again (and eventually causing harm). This is a clean way to end the job even if there isn't a valid file name to provide. Both files patches web2c/texk/tex.ch. Of course they cannot be used at the same time. And both patches also show the default name extension, when the user is prompted for a file name. Have fun, Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-03-10 23:57 Message: Logged In: YES user_id=421 Both patches are interesting, but we should wait for further discussion on tex-implementors etc. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=746&group_id=106

1 0

[ pdftex-Bugs-747 ] \letterspacefont and \pdffontexpand, again
by noreply＠sarovar.org 10 Mar '07

10 Mar '07

Bugs item #747, was opened at 2007-03-09 03:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=747&group_id=106 Category: hz Group: v1.40.1 Status: Open Resolution: Accepted Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: \letterspacefont and \pdffontexpand, again Initial Comment: When expanding a letterspaced font, the base font will be expanded, too, resulting in the error `font has been expanded with different parameters' when the base font is expanded again: \letterspacefont\lsfont\font 100 \pdffontexpand\lsfont 20 20 5 autoexpand \pdffontexpand\font 20 20 5 autoexpand Z\bye ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-03-10 20:18 Message: Logged In: YES user_id=710 Phil Taylor has a suggestion that seems great to me: introduce a new primitive \pdfexpandfont instead. How do you see it? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-10 19:24 Message: Logged In: YES user_id=421 Forget that comment. Of course a change of \pdffontexpand has to be considered carefully. By you. :-) ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-10 19:22 Message: Logged In: YES user_id=421 No. It's an undocumented primitive. ;-) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-03-09 17:28 Message: Logged In: YES user_id=710 sigh. A mistake when implementing the \pdffontexpand primitive: it should load a new font for expansion, instead of expanding a loaded font. Too late for change now? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=747&group_id=106

1 0

[ pdftex-Bugs-747 ] \letterspacefont and \pdffontexpand, again
by noreply＠sarovar.org 10 Mar '07

10 Mar '07

Bugs item #747, was opened at 2007-03-09 04:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=747&group_id=106 Category: hz Group: v1.40.1 Status: Open Resolution: Accepted Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: \letterspacefont and \pdffontexpand, again Initial Comment: When expanding a letterspaced font, the base font will be expanded, too, resulting in the error `font has been expanded with different parameters' when the base font is expanded again: \letterspacefont\lsfont\font 100 \pdffontexpand\lsfont 20 20 5 autoexpand \pdffontexpand\font 20 20 5 autoexpand Z\bye ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-03-10 20:24 Message: Logged In: YES user_id=421 Forget that comment. Of course a change of \pdffontexpand has to be considered carefully. By you. :-) ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-10 20:22 Message: Logged In: YES user_id=421 No. It's an undocumented primitive. ;-) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-03-09 18:28 Message: Logged In: YES user_id=710 sigh. A mistake when implementing the \pdffontexpand primitive: it should load a new font for expansion, instead of expanding a loaded font. Too late for change now? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=747&group_id=106

1 0