November 2006 - ntg-pdftex - NTG Mailing Lists

[ pdftex-Patches-705 ] Patch to allow vf_nf grow dynamically
by noreply＠sarovar.org 26 Nov '06

26 Nov '06

Patches item #705, was opened at 2006-11-22 20:52 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106 Category: Fonts >Group: v1.40.0 Status: Open Resolution: Accepted Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Hartmut Henkel (hhenkel) Summary: Patch to allow vf_nf grow dynamically Initial Comment: This patch allows the array vf_e_fnts and vf_i_fnts grow dynamically, instead of having fixed size font_max as currently. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-11-26 21:01 Message: Logged In: YES user_id=421 This has been included in version 1.40 ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-11-25 10:58 Message: Logged In: NO Hi! It's been applied on Debian/unstable, and it works! Top notch! Thanks Danai SAE-HAN ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-11-23 08:18 Message: Logged In: YES user_id=710 yes. this patch also contains a fix by Akira the segfault bug (one line added) and a fix for bug #692 (another line). It's not hard to fix bug #694 and #696 too. However I didn't mention them, as I am considering to remove the relevant code. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-11-23 02:26 Message: Logged In: NO Hi! Does this mean that the bug "SGML output fails with pdflatex" will also be solved? Cheers Danai SAE-HAN ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106

1 0

[ pdftex-Patches-705 ] Patch to allow vf_nf grow dynamically
by noreply＠sarovar.org 26 Nov '06

26 Nov '06

Patches item #705, was opened at 2006-11-22 20:52 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106 >Category: Fonts >Group: v1.30.0 Status: Open >Resolution: Accepted Priority: 5 Submitted By: The Thanh Han (hanthethanh) >Assigned to: Hartmut Henkel (hhenkel) Summary: Patch to allow vf_nf grow dynamically Initial Comment: This patch allows the array vf_e_fnts and vf_i_fnts grow dynamically, instead of having fixed size font_max as currently. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-11-26 21:01 Message: Logged In: YES user_id=421 This has been included in version 1.40 ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-11-25 10:58 Message: Logged In: NO Hi! It's been applied on Debian/unstable, and it works! Top notch! Thanks Danai SAE-HAN ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-11-23 08:18 Message: Logged In: YES user_id=710 yes. this patch also contains a fix by Akira the segfault bug (one line added) and a fix for bug #692 (another line). It's not hard to fix bug #694 and #696 too. However I didn't mention them, as I am considering to remove the relevant code. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-11-23 02:26 Message: Logged In: NO Hi! Does this mean that the bug "SGML output fails with pdflatex" will also be solved? Cheers Danai SAE-HAN ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106

1 0

[ pdftex-Patches-705 ] Patch to allow vf_nf grow dynamically
by noreply＠sarovar.org 25 Nov '06

25 Nov '06

Patches item #705, was opened at 2006-11-23 01:22 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: Patch to allow vf_nf grow dynamically Initial Comment: This patch allows the array vf_e_fnts and vf_i_fnts grow dynamically, instead of having fixed size font_max as currently. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-11-25 15:28 Message: Logged In: NO Hi! It's been applied on Debian/unstable, and it works! Top notch! Thanks Danai SAE-HAN ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-11-23 12:48 Message: Logged In: YES user_id=710 yes. this patch also contains a fix by Akira the segfault bug (one line added) and a fix for bug #692 (another line). It's not hard to fix bug #694 and #696 too. However I didn't mention them, as I am considering to remove the relevant code. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-11-23 06:56 Message: Logged In: NO Hi! Does this mean that the bug "SGML output fails with pdflatex" will also be solved? Cheers Danai SAE-HAN ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106

1 0

Re: [NTG-pdftex] About the font_max limitation for vf_nf
by Thanh Han The 24 Nov '06

24 Nov '06

Hi, I took a closer look at the problem. vf_nf grows very fast because vf_nf = <number of vf fonts> * <number of tfm in each vf> We cannot reduce this, because the number of tfm inside a vf (let's call it the local tfm) is used to render the characters inside a vf. Hence pdftex must remember all local for all vf, which is the above number. However it seems reasonable to allow the limit to be much higher than font_max. I will submit a patch soon. Thanh On Wed, Nov 22, 2006 at 09:44:10PM +0800, Jie Luo wrote: > Hi, > > There is a GB.tex in the test.tar.bz2 which is a modification of GB.tex > in CJK package. This file can be compiled with TeXLive. When processing > this file with pdflatex, the vf_nf value reaches 1978 which is close to > the present font_max ( = 2000 ). I also attach the log files of another > two tex documents, hope to be helpful. > > Thanks, > > Jie > > Thanh Han The wrote: > >Hi, > > > >can you please send me a minimal test file so I can > >reproduce the problem? It is best to use fonts that are > >available in TeXLive so I can compile it. > > > >Thanks, > >Thanh > > > >On Wed, Nov 22, 2006 at 05:38:35PM +0800, Jie Luo wrote: > >>Hi Thanh, > >> > >>Thanh Han The wrote: > >>>Hi, > >>> > >>>I don't know whether this is a bug or not, unless I can > >>>reproduce the behaviour. You can verify by checking how many > >>>tfm fonts are opened by pdftex. If the total number of tfm > >>>fonts is much less than vf_nf, then it's likely a bug. > >>>However there are a few things to consider: > >>> > >>>- tex (and hence pdftex) loads the same tfm for different > >>> sizes, ef \font\f=cmr10 and \font\f=cmr10 at 12pt will > >>> load the tfm twice. > >>> > >>>- the same applies for vf. In the above example, if cmr10 is > >>> a virtual font containing 2 tfm, the number of loaded > >>> fonts will be 4. So you get the idea how quick it grows. > >>> > >>> > >>>You can use the script I attached to see which fonts have > >>>been opened during a tex run. Usage: > >>> > >>>,-------- > >>>| list-tex-files pdftex foo.tex > >>>`-------- > >>> > >>>It will run pdftex and saves the list of opened files into a > >>>temporary file. > >>> > >>>HTH, > >>>Thanh > >> > >>I did some tests using this script. > >> > >>GB.tex > >>vf_nf = 3114 > >>opened tfm files with pdflatex = 408 > >>opened tfm files with latex = 59 > >> > >>book.tex > >>vf_nf = 11834 > >>opened tfm files with pdflatex = 1075 > >>opened tfm files with latex = 364 > >> > >>So it seems that the vf_nf is about 10 times of the opened tfm files, > >>this maybe a bug. By the way, I do not have the list-tex-files.vim file, > >>is this a problem? > >> > >>Thanks, > >> > >>Jie > >> > >>> > >>>On Wed, Nov 22, 2006 at 01:12:56PM +0800, Jie Luo wrote: > >>>>Hi Thanh, > >>>> > >>>>When using pdflatex to processing tex documents contain more than two > >>>>Chinese GBK virtual fonts, pdflatex always failed with a divide by zero > >>>>error. I read the mail archive of pdftex list and find it said to be > >>>>related to the font_max limitation. I add some statement to debug this, > >>>>and find that the vf_nf value is about 2300 when using two Chinese GBK > >>>>virtual fonts. But when I use pdflatex to compile a book with about 250 > >>>>pages, the value of vf_nf is about 12000 with less than 100 type1 fonts > >>>>embedded in the pdf file. Is there any problem with the vf_nf? Or it is > >>>>the expected value. > >>>> > >>>> > >>>>Jie > >>> > >>>------------------------------------------------------------------------ > >>> > >>>#!/bin/sh > >>> > >>>if test "x$1" = x; then > >>> echo Usage: "$0 <tex command>" > >>> echo Example: "$0 latex myfile" > >>> exit 1 > >>>fi > >>>export KPATHSEA_DEBUG=4 > >>>f=/tmp/kpof.$$.1 > >>> > >>>$* 2>$f > >>>vim -S ~/vim/list-tex-files.vim $f > >>>echo "List of opened files saved to $f" > >>> > >> > > >

3 5

status of pending bugs
by Thanh Han The 24 Nov '06

24 Nov '06

Hi, it seems that it's too late now to remove some extensions. Though it's trivial to do so regards coding, the impact might be undesired so it is better to do that after TL has been released. So at the meantime I will try to fix some of the pending bugs. Here is the current status: 692, 694: fixed 693: still trying 695: unlikely to be fixed, even in the future. 696: Harmut and I are working on this, we hope to fix it during the wekend. Thanh

1 0

[ pdftex-Patches-705 ] Patch to allow vf_nf grow dynamically
by noreply＠sarovar.org 23 Nov '06

23 Nov '06

Patches item #705, was opened at 2006-11-22 19:52 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: Patch to allow vf_nf grow dynamically Initial Comment: This patch allows the array vf_e_fnts and vf_i_fnts grow dynamically, instead of having fixed size font_max as currently. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2006-11-23 07:18 Message: Logged In: YES user_id=710 yes. this patch also contains a fix by Akira the segfault bug (one line added) and a fix for bug #692 (another line). It's not hard to fix bug #694 and #696 too. However I didn't mention them, as I am considering to remove the relevant code. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-11-23 01:26 Message: Logged In: NO Hi! Does this mean that the bug "SGML output fails with pdflatex" will also be solved? Cheers Danai SAE-HAN ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106

1 0

[ pdftex-Patches-705 ] Patch to allow vf_nf grow dynamically
by noreply＠sarovar.org 22 Nov '06

22 Nov '06

Patches item #705, was opened at 2006-11-23 01:22 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: Patch to allow vf_nf grow dynamically Initial Comment: This patch allows the array vf_e_fnts and vf_i_fnts grow dynamically, instead of having fixed size font_max as currently. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-11-23 06:56 Message: Logged In: NO Hi! Does this mean that the bug "SGML output fails with pdflatex" will also be solved? Cheers Danai SAE-HAN ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106

1 0

[ pdftex-Patches-705 ] Patch to allow vf_nf grow dynamically
by noreply＠sarovar.org 22 Nov '06

22 Nov '06

Patches item #705, was opened at 2006-11-22 19:52 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: Patch to allow vf_nf grow dynamically Initial Comment: This patch allows the array vf_e_fnts and vf_i_fnts grow dynamically, instead of having fixed size font_max as currently. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=705&group_id=106

1 0

removal of some extensions -- yes or no?
by Thanh Han The 22 Nov '06

22 Nov '06

Dear list, I am considering to remove some extensions I added to pdftex recently, as it's hard to make them work reliably, and they also seem little useful. In short they are: ,-------- | \pdfadjustinterwordglue, \knbscode, \stbscode, \shbscode: | adjust the interglue space according to the charater before | the glue | | \pdfprependkern, \knbccode: auto-insertion of a kern before a char | | \pdfappendkern, \knaccode: auto-insertion of a kern after a char `-------- Before I make a decision, I would like to listen to other opinions. So please let me know what you think of this. Thanks, Thanh

1 0

Re: [NTG-pdftex] [ pdftex-Bugs-695 ] Confusion when changing kerning settings within a paragraph
by Thanh Han The 21 Nov '06

21 Nov '06

Hi Hans, removing those features is trivial. The question is: - is it worthwhile to have them, at least with some limitations? - are they already used and hence removing them can cause trouble? AFAIK only Robert Schlicht and Ulrich Dirr have been playing with them a little bit, but nobody has made any use of those in serious work. Please correct me if I am wrong. Of course I am happy to play with those features when luatex is ready for that. Thanh On Sun, Nov 19, 2006 at 11:07:38PM +0100, Hans Hagen wrote: > Hi Thanh, > >I think it was not a good decision to introduce those new > >features, as they touch a very sensitive area of tex and > >it's hard to get them right. I wonder whether it is better > >to discard them all. > > > removing them is tricky since they may be in use already but don't spend to > much time on fixing things that are hard to fix in current tex; once luatex > is in a state where fontdata has no longer the global properties and where > we can have more control over font related featurss, you can probably > rewrite most of the code in a cleaner way > 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 > ----------------------------------------------------------------- >

4 3