- ntg-pdftex - NTG Mailing Lists

[ pdftex-Patches-738 ] new primitive \pdfreplacefont
by noreply＠sarovar.org 27 Feb '07

27 Feb '07

Patches item #738, was opened at 2007-02-27 22:31 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=738&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Hartmut Henkel (hhenkel) Summary: new primitive \pdfreplacefont Initial Comment: This primitive controls whether font replacement should be done when embedding pdf's. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=738&group_id=106

1 0

[ pdftex-Bugs-722 ] PDF generation does not support VF fonts correctly
by noreply＠sarovar.org 27 Feb '07

27 Feb '07

Bugs item #722, was opened at 2007-01-24 08:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=722&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: Accepted Priority: 5 Submitted By: Achim Blumensath (blume) Assigned to: The Thanh Han (hanthethanh) Summary: PDF generation does not support VF fonts correctly Initial Comment: I've a problem with using VF fonts in PDF mode (using pdftex 1.40.1, pdftex 1.20b does work correctly). When using glyphs that are composed of several other glyphs the various parts appear not at their correct position. The following example requires the MnSymbol and the MinionPro packages. \documentclass{minimal} \usepackage[T1]{fontenc} \usepackage[minionint]{MinionPro} \begin{document} $$\iint \quad \oint$$ \end{document} If you create a DVI and use dvips + ps2pdf the output is as expected (one double integral and one closed integral). If you use pdflatex to create a PDF file directly then the output is wrong. The double integral consists of just one integral sign and the closed integral consists of a circle followed by an integral sign. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-02-27 22:29 Message: Logged In: YES user_id=710 Bugfix resubmitted, this time without the new primitive \pdfreplacefont ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-31 08:41 Message: Logged In: YES user_id=4173 The patch seems to work fine. Thanks. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-29 19:46 Message: Logged In: YES user_id=710 I made some changes in pdftex. Your test file looks almost ok now :). Can you please try the patch to see whether it works for you. Since I don't have exactly the same fonts you used, it might be helpful if you try the patch with your tex setup. Thanks. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-26 10:55 Message: Logged In: YES user_id=710 indeed this is a bug of pdftex. I found the bug, should be fixed soon. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-26 08:47 Message: Logged In: YES user_id=4173 Sorry, I forgot to mention that I couldn't include the pfb for copyright reasons. You need the opticals version of MinionPro to get MinionPro-ItDisp.pfb. If you don't have the optical fonts the easiest workaround is to create a PFB with just one glyph named /integral of width 310 units. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-26 07:47 Message: Logged In: YES user_id=710 I still got: pdfTeX warning: pdftex (file MinionPro-ItDisp.pfb): cannot open Type 1 font file for reading I checked out the cvs version of MinionPro and run the makeall script as described in README-src, but still I didn't see MinionPro-ItDisp.pfb. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-26 06:21 Message: Logged In: YES user_id=4173 I've simplified the test case to plain TeX. The requested files are attached. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-01-25 14:01 Message: Logged In: YES user_id=421 Note that the -recorder cmdline switch also works quite well with kpathsea. :-) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-25 08:43 Message: Logged In: YES user_id=710 I tested the file again with the fonts you uploaded, but still I cannot reproduce the problem. I attached a small script that creates a list of all files opened by tex. Usage: unpack, put list-tex-files.vim under ~/vim and run: sh list-tex-files pdflatex testfile it will report the filename of the list, which can be used then to pack everything needed to rerun the job. You may want to review the list to remove a few files that are not relevant, for example the format. ---------------------------------------------------------------------- Comment By: Achim Blumensath (blume) Date: 2007-01-25 06:54 Message: Logged In: YES user_id=4173 In order to preproduce the bug you need the CVS version on MinionPro and perhaps also a recent version of the lcdf-typetools. The problem seems to be that the font MnSymbolFI10.vf refers again to a virtual font MinionPro-It-integral.vf. I've attached the corresponding VPL files. (I didn't have the time to create the requested PDF files. Will do so shortly.) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-24 18:52 Message: Logged In: YES user_id=710 I compiled the test file and got normal output (see attached screenshot). ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-01-24 14:56 Message: Logged In: YES user_id=421 Please attach the PDFs generated by ps2pdf and pdflatex, best generated with \pdfcompresslevel=0. And the log from pdflatex. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=722&group_id=106

1 0

warning messages
by Reinhard Kotucha 26 Feb '07

26 Feb '07

Hi, I just got the warning message: pdfTeX warning (Object streams): \pdfobjcompresslevel > 0 requires \pdfminorversion > 4. Object streams disabled now. maybe the last sentence should be changed to: Object stream compression disabled now. It's confusing that there are stream objects and object streams and that object streams become stream objects when object stream compression is applied and object stream compression cannot be applied to stream objects, and so on. The expression "compression disabled" tells people that nothing will be missing in the generated PDF file, something will just not be compressed. But who knows what "object streams" are and what happens if they are disabled? Should TeX users be bothered with this low-level stuff? Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------

1 0

[ pdftex-Bugs-737 ] Missing pfbs lead to invalid pdf
by noreply＠sarovar.org 26 Feb '07

26 Feb '07

Bugs item #737, was opened at 2007-02-25 16:03 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=737&group_id=106 Category: Fonts Group: v1.40.1 >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing pfbs lead to invalid pdf Initial Comment: Try this file: ----------- \pdfmapline{} \nopagenumbers \font\ugqb ugqb8r at 10pt \ugqb foo \bye ----------- with ugqb8r.tfm in your texmf, but without the pfb. Here is the log from pdftex: ----------- This is pdfTeX, Version 3.141592-1.50.0-alpha-20070219 (Web2C 7.5.6) entering extended mode (./fonts20070225.tex [1]kpathsea: Running mktexpk --mfmode / --bdpi 1200 --mag 1+0/1200 --dpi 1200 ugqb8r mktexpk: don't know how to create bitmap font for ugqb8r. kpathsea: Appending font creation commands to missfont.log. ) pdfTeX warning: pdftex (file ugqb8r): Font ugqb8r at 1200 not found Output written on fonts20070225.pdf (1 page, 1018 bytes). Transcript written on fonts20070225.log. ----------- So a pdf is written, but it's invalid: > pdffonts fonts20070225.pdf ----------- name type emb sub uni object ID ------------------------------------ ------------ --- --- --- --------- Error: font resource is not a dictionary ----------- indeed the font object (#4) doesn't even exist. pdfTeX shall not generate invalid pdfs, so in this case it should abort. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-02-26 08:56 Message: Logged In: YES user_id=710 this problem is already meantioned in bug #721. In a mail I sent to Hartmut: when you fix bug 721, can you please go through those pdftex_warn's to see whether any other of them should be changed to pdftex_fatal as well? Personally I always vote for the approach "quit at any problem", however from time to time somebody asked to change an error to a warning and usually I did it without much checking. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-02-25 16:18 Message: Logged In: YES user_id=421 This all started in a thread on texhax: http://tug.org/pipermail/texhax/2007-February/007916.html ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=737&group_id=106

1 0

[ pdftex-Bugs-737 ] Missing pfbs lead to invalid pdf
by noreply＠sarovar.org 26 Feb '07

26 Feb '07

Bugs item #737, was opened at 2007-02-25 15:03 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=737&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing pfbs lead to invalid pdf Initial Comment: Try this file: ----------- \pdfmapline{} \nopagenumbers \font\ugqb ugqb8r at 10pt \ugqb foo \bye ----------- with ugqb8r.tfm in your texmf, but without the pfb. Here is the log from pdftex: ----------- This is pdfTeX, Version 3.141592-1.50.0-alpha-20070219 (Web2C 7.5.6) entering extended mode (./fonts20070225.tex [1]kpathsea: Running mktexpk --mfmode / --bdpi 1200 --mag 1+0/1200 --dpi 1200 ugqb8r mktexpk: don't know how to create bitmap font for ugqb8r. kpathsea: Appending font creation commands to missfont.log. ) pdfTeX warning: pdftex (file ugqb8r): Font ugqb8r at 1200 not found Output written on fonts20070225.pdf (1 page, 1018 bytes). Transcript written on fonts20070225.log. ----------- So a pdf is written, but it's invalid: > pdffonts fonts20070225.pdf ----------- name type emb sub uni object ID ------------------------------------ ------------ --- --- --- --------- Error: font resource is not a dictionary ----------- indeed the font object (#4) doesn't even exist. pdfTeX shall not generate invalid pdfs, so in this case it should abort. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-02-26 07:56 Message: Logged In: YES user_id=710 this problem is already meantioned in bug #721. In a mail I sent to Hartmut: when you fix bug 721, can you please go through those pdftex_warn's to see whether any other of them should be changed to pdftex_fatal as well? Personally I always vote for the approach "quit at any problem", however from time to time somebody asked to change an error to a warning and usually I did it without much checking. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-02-25 15:18 Message: Logged In: YES user_id=421 This all started in a thread on texhax: http://tug.org/pipermail/texhax/2007-February/007916.html ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=737&group_id=106

1 0

[ pdftex-Patches-735 ] patch for simplified horizontal positional tracking
by noreply＠sarovar.org 25 Feb '07

25 Feb '07

Patches item #735, was opened at 2007-02-19 22:00 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=735&group_id=106 Category: Positioning Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) Summary: patch for simplified horizontal positional tracking Initial Comment: 1. simpler calculations for horizontal position update when inside []TJ arrays, now by pure additions within a fontsize/10000 raster; no rounding errors can accumulate. Gives about 7 % pdftex speed gain when typesetting fiction-type stuff. 2. writet3.c now also with standard /FontMatrix [0.001 0 0 0.001 0 0], tidied up a little (.pgc part untested). No need anymore (hope it's right) to handle PK fonts specially by adv_char_width() in pdftex.web. 3. wrong use of printf() at a few places corrected by Martin. Work in progess, not safe for production. Needs more testing, particularly with PK fonts. Regards, Hartmut ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2007-02-25 23:51 Message: Logged In: YES user_id=929 The previous patch 735 is now extended to general text and graphics positioning on the PDF page. pdf_set_origin() (now pdf_move_to()), pdf_set_textmatrix(), and pdf_begin_string() are rewritten. In low placement resolution (e. g. \pdfdecimaldigits=0) now the glyph placement is corrected within the []TJ array by a leading number, like [7(a)...]TJ, if required, so that always full TeX precision is kept (very early pdftex versions might have used this also). Any accumulation of rounding errors should be avoided now by the used calculation principle. Needs lots of testing. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=735&group_id=106

1 0

[ pdftex-Bugs-737 ] Missing pfbs lead to invalid pdf
by noreply＠sarovar.org 25 Feb '07

25 Feb '07

Bugs item #737, was opened at 2007-02-25 16:03 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=737&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing pfbs lead to invalid pdf Initial Comment: Try this file: ----------- \pdfmapline{} \nopagenumbers \font\ugqb ugqb8r at 10pt \ugqb foo \bye ----------- with ugqb8r.tfm in your texmf, but without the pfb. Here is the log from pdftex: ----------- This is pdfTeX, Version 3.141592-1.50.0-alpha-20070219 (Web2C 7.5.6) entering extended mode (./fonts20070225.tex [1]kpathsea: Running mktexpk --mfmode / --bdpi 1200 --mag 1+0/1200 --dpi 1200 ugqb8r mktexpk: don't know how to create bitmap font for ugqb8r. kpathsea: Appending font creation commands to missfont.log. ) pdfTeX warning: pdftex (file ugqb8r): Font ugqb8r at 1200 not found Output written on fonts20070225.pdf (1 page, 1018 bytes). Transcript written on fonts20070225.log. ----------- So a pdf is written, but it's invalid: > pdffonts fonts20070225.pdf ----------- name type emb sub uni object ID ------------------------------------ ------------ --- --- --- --------- Error: font resource is not a dictionary ----------- indeed the font object (#4) doesn't even exist. pdfTeX shall not generate invalid pdfs, so in this case it should abort. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-02-25 16:18 Message: Logged In: YES user_id=421 This all started in a thread on texhax: http://tug.org/pipermail/texhax/2007-February/007916.html ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=737&group_id=106

1 0

[ pdftex-Bugs-737 ] Missing pfbs lead to invalid pdf
by noreply＠sarovar.org 25 Feb '07

25 Feb '07

Bugs item #737, was opened at 2007-02-25 16:03 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=737&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing pfbs lead to invalid pdf Initial Comment: Try this file: ----------- \pdfmapline{} \nopagenumbers \font\ugqb ugqb8r at 10pt \ugqb foo \bye ----------- with ugqb8r.tfm in your texmf, but without the pfb. Here is the log from pdftex: ----------- This is pdfTeX, Version 3.141592-1.50.0-alpha-20070219 (Web2C 7.5.6) entering extended mode (./fonts20070225.tex [1]kpathsea: Running mktexpk --mfmode / --bdpi 1200 --mag 1+0/1200 --dpi 1200 ugqb8r mktexpk: don't know how to create bitmap font for ugqb8r. kpathsea: Appending font creation commands to missfont.log. ) pdfTeX warning: pdftex (file ugqb8r): Font ugqb8r at 1200 not found Output written on fonts20070225.pdf (1 page, 1018 bytes). Transcript written on fonts20070225.log. ----------- So a pdf is written, but it's invalid: > pdffonts fonts20070225.pdf ----------- name type emb sub uni object ID ------------------------------------ ------------ --- --- --- --------- Error: font resource is not a dictionary ----------- indeed the font object (#4) doesn't even exist. pdfTeX shall not generate invalid pdfs, so in this case it should abort. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=737&group_id=106

1 0

[CTAN] qstest
by Martin Schröder 23 Feb '07

23 Feb '07

---------- Forwarded message ---------- From: CTAN Announcements <ctan-ann(a)dante.de> Date: 22.02.2007 22:54 Subject: CTAN has a new bundle: qstest To: ctan-ann(a)dante.de On Wed, 21 Feb 2007, David Kastrup submitted the qstest bundle to CTAN. Location on CTAN: /macros/latex/contrib/qstest Summary description: Bundle for unit tests and pattern matching License type: lppl Announcement text: ---------------------------------------------------------------------- This is the public release of the qstest bundle (written for DocScape Publisher <URL:http://www.docscape.de>) (C) 2006, 2007 QuinScape GmbH <URL:http://www.quinscape.de> The bundle contains the packages `makematch' for matching patterns to targets (with a generalization in the form of pattern lists and keyword lists), and `qstest' for performing unit tests, allowing to run a number of logged tests ensuring the consistency of values, properties and call sequences during execution of test code. Both packages make extensive use of qstest in their package documentation, provided illustrated examples that are automatically verified to work as expected. Check the README file for details. David Kastrup <dak(a)gnu.org> QuinScape GmbH http://www.QuinScape.de ---------------------------------------------------------------------- This bundle is located at http://dante.ctan.org/tex-archive/macros/latex/contrib/qstest . More information is at http://tug.ctan.org/info/?id=qstest (if the package is new it may take a day for that information to appear). We are supported by the TeX Users Group http://www.tug.org . Please join a users group; see http://www.tug.org/usergroups.html . _______________________________________________ Thanks for the upload. For the CTAN Team Rainer Schöpf

1 0

[ pdftex-Bugs-736 ] font expansion leads to wrong log output of \kerns.
by noreply＠sarovar.org 22 Feb '07

22 Feb '07

Bugs item #736, was opened at 2007-02-22 03:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=736&group_id=106 Category: hz Group: v1.40.1 Status: Open >Resolution: Accepted >Priority: 3 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion leads to wrong log output of \kerns. Initial Comment: When applying font expansion, implicit kerns will be output *with* a space in the log file, which makes them appear like explicit kerns. The following \tracingoutput1 \pdfadjustspacing2 \pdffontexpand\font 20 20 5 autoexpand bye\bye will yield ...\tenrm b ...\kern -0.27779 ...\tenrm y ...\kern -0.27779 ...etc. instead of ...\tenrm b ...\kern-0.27779 ...\tenrm y ...\kern-0.27779 ...etc. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-02-22 11:46 Message: Logged In: YES user_id=710 I confirm the bug. Will try to fix it soon. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=736&group_id=106

1 0

[ pdftex-Bugs-736 ] font expansion leads to wrong log output of \kerns.
by noreply＠sarovar.org 22 Feb '07

22 Feb '07

Bugs item #736, was opened at 2007-02-22 02:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=736&group_id=106 Category: hz Group: v1.40.1 Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion leads to wrong log output of \kerns. Initial Comment: When applying font expansion, implicit kerns will be output *with* a space in the log file, which makes them appear like explicit kerns. The following \tracingoutput1 \pdfadjustspacing2 \pdffontexpand\font 20 20 5 autoexpand bye\bye will yield ...\tenrm b ...\kern -0.27779 ...\tenrm y ...\kern -0.27779 ...etc. instead of ...\tenrm b ...\kern-0.27779 ...\tenrm y ...\kern-0.27779 ...etc. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-02-22 10:46 Message: Logged In: YES user_id=710 I confirm the bug. Will try to fix it soon. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=736&group_id=106

1 0

[ pdftex-Bugs-712 ] problems with \letterspacefont
by noreply＠sarovar.org 22 Feb '07

22 Feb '07

Bugs item #712, was opened at 2006-12-12 02:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106 Category: hz Group: v1.40.0 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: problems with \letterspacefont Initial Comment: % Testing the new \letterspacefont, I found: % % (1) it's certainly not correct to have the spacing % relative to character widths (look at `minimal'!) % (2) everything's shifted to the right % (3) when trying to expand the letter-spaced font, I % get the warning `font should be expanded before % its first use' (even before its first use), and % then pdftex segfaults. \pdfadjustspacing2 \hsize13cm This is normal text This is normal text This is normal text This is normal text This is normal text This is normal text {\letterspacefont\lspfont=\font 1000 %\pdffontexpand\lspfont 20 20 5 autoexpand % segfault \lspfont This isn't normal text This isn't normal text This isn't normal text This is minimal text} This is normal text This is normal text This is normal text \bye ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-02-22 09:31 Message: Logged In: YES user_id=710 yes it sounds reasonable. Or we can extend the syntax of \letterspacefont so that if an optional keyword like 'nolig' is found then ligatures will be disabled. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-02-22 02:54 Message: Logged In: YES user_id=2217 The current situation with regards to the lack of kerning of letterspaced fonts is not really satisfying. After some consideration, I therefore think it is actually better *not* to disable ligatures, and hence kerning, for letterspaced fonts. So I would propose to remove the line: set_no_ligatures(k); {disable ligatures for letter-spaced fonts} It is easy enough for the high-level interfaces (microtype, context) to (automatically) disable selected ligatures only, so that kerning for the rest of the characters is still available. What do you think? \letterspacefont\lsfont\font 100 \lsfont \tagcode\lsfont`f -1 VALID off -- \bye ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-02-02 13:54 Message: Logged In: YES user_id=710 the warning message can be removed. I left it there since I don't know what happens if a virtual font is loaded, used and then expanded and used again with font expansion. It should be alright to do so, but I am not very sure. Anyway, I will change the warning to be issued for non-virtual fonts only. It turned to be a design mistake that the \pdffontexpand primitive takes a base font and turns it to an expanded font. It would be better it was more like \letterspacefont, ie it should create a new font and leave the original font intact. ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2007-02-02 07:30 Message: Logged In: YES user_id=1608 > I hope luatex will abolish with this nonsensical connexion of ligatures and kerns? Yes. ligatures and kerns are totally separate in luatex. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-02-01 19:02 Message: Logged In: YES user_id=2217 If the warning is misleading, should it not be removed? On a different matter: Since \letterspacefont issues set_no_ligatures, there won't be any kerning, either. There's no way around that, I guess? (I hope luatex will abolish with this nonsensical connexion of ligatures and kerns?) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-04 15:59 Message: Logged In: YES user_id=710 The warning is misleading but harmless. The reason of the warning is that pdftex checks whether a font has not been used before expansion (its type has not been examined and is new/unknown yet). \letterspacefont sets the type of \y as a virtual font, thus pdftex thinks the font might have been used before. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-01-04 00:40 Message: Logged In: YES user_id=2217 I'm a bit confused about the status of (3): letterspacing and expansion: When expanding a letterspaced font, pdftex issues the warning: ``font should be expanded before its first use'', but apart from that, I cannot see any problems -- the font is both letterspaced and expanded. Or is there a reason for the warning? \pdfadjustspacing2 \font\x=cmr10 \x \letterspacefont\y=\x 100 \y \pdffontexpand\y 20 20 5 autoexpand ... \bye ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-12-21 16:09 Message: Logged In: YES user_id=421 A patch for this will be included in the next version (1.40). ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-12 17:47 Message: Logged In: YES user_id=710 oops, I disabled ligature for letter-spaced font, but this should not affect the base font. Will have to rethink. Most likely the syntax will change like follows: \letterspacefont\f=cmr10 at 11pt 100 \f text ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2006-12-12 15:50 Message: Logged In: YES user_id=2217 % and here's % (4) ligatures will be broken up, not only in the % letter-spaced font (which is probably acceptable), % but in all subsequent uses of the base font, too fi\par {\letterspacefont\lspfont=\font 100 \lspfont fi}\par fi \bye ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-12 13:31 Message: Logged In: YES user_id=710 I fixed (1) and (2); (3) is disabled now, ie you cannot expand a letter-spaced font. Please wait for another release from Martin. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106

1 0

[ pdftex-Bugs-736 ] font expansion leads to wrong log output of \kerns.
by noreply＠sarovar.org 22 Feb '07

22 Feb '07

Bugs item #736, was opened at 2007-02-22 02:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=736&group_id=106 Category: hz Group: v1.40.1 Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion leads to wrong log output of \kerns. Initial Comment: When applying font expansion, implicit kerns will be output *with* a space in the log file, which makes them appear like explicit kerns. The following \tracingoutput1 \pdfadjustspacing2 \pdffontexpand\font 20 20 5 autoexpand bye\bye will yield ...\tenrm b ...\kern -0.27779 ...\tenrm y ...\kern -0.27779 ...etc. instead of ...\tenrm b ...\kern-0.27779 ...\tenrm y ...\kern-0.27779 ...etc. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=736&group_id=106

1 0

[ pdftex-Bugs-712 ] problems with \letterspacefont
by noreply＠sarovar.org 22 Feb '07

22 Feb '07

Bugs item #712, was opened at 2006-12-12 02:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106 Category: hz Group: v1.40.0 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: problems with \letterspacefont Initial Comment: % Testing the new \letterspacefont, I found: % % (1) it's certainly not correct to have the spacing % relative to character widths (look at `minimal'!) % (2) everything's shifted to the right % (3) when trying to expand the letter-spaced font, I % get the warning `font should be expanded before % its first use' (even before its first use), and % then pdftex segfaults. \pdfadjustspacing2 \hsize13cm This is normal text This is normal text This is normal text This is normal text This is normal text This is normal text {\letterspacefont\lspfont=\font 1000 %\pdffontexpand\lspfont 20 20 5 autoexpand % segfault \lspfont This isn't normal text This isn't normal text This isn't normal text This is minimal text} This is normal text This is normal text This is normal text \bye ---------------------------------------------------------------------- >Comment By: Robert (schlcht) Date: 2007-02-22 02:54 Message: Logged In: YES user_id=2217 The current situation with regards to the lack of kerning of letterspaced fonts is not really satisfying. After some consideration, I therefore think it is actually better *not* to disable ligatures, and hence kerning, for letterspaced fonts. So I would propose to remove the line: set_no_ligatures(k); {disable ligatures for letter-spaced fonts} It is easy enough for the high-level interfaces (microtype, context) to (automatically) disable selected ligatures only, so that kerning for the rest of the characters is still available. What do you think? \letterspacefont\lsfont\font 100 \lsfont \tagcode\lsfont`f -1 VALID off -- \bye ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-02-02 13:54 Message: Logged In: YES user_id=710 the warning message can be removed. I left it there since I don't know what happens if a virtual font is loaded, used and then expanded and used again with font expansion. It should be alright to do so, but I am not very sure. Anyway, I will change the warning to be issued for non-virtual fonts only. It turned to be a design mistake that the \pdffontexpand primitive takes a base font and turns it to an expanded font. It would be better it was more like \letterspacefont, ie it should create a new font and leave the original font intact. ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2007-02-02 07:30 Message: Logged In: YES user_id=1608 > I hope luatex will abolish with this nonsensical connexion of ligatures and kerns? Yes. ligatures and kerns are totally separate in luatex. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-02-01 19:02 Message: Logged In: YES user_id=2217 If the warning is misleading, should it not be removed? On a different matter: Since \letterspacefont issues set_no_ligatures, there won't be any kerning, either. There's no way around that, I guess? (I hope luatex will abolish with this nonsensical connexion of ligatures and kerns?) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-04 15:59 Message: Logged In: YES user_id=710 The warning is misleading but harmless. The reason of the warning is that pdftex checks whether a font has not been used before expansion (its type has not been examined and is new/unknown yet). \letterspacefont sets the type of \y as a virtual font, thus pdftex thinks the font might have been used before. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-01-04 00:40 Message: Logged In: YES user_id=2217 I'm a bit confused about the status of (3): letterspacing and expansion: When expanding a letterspaced font, pdftex issues the warning: ``font should be expanded before its first use'', but apart from that, I cannot see any problems -- the font is both letterspaced and expanded. Or is there a reason for the warning? \pdfadjustspacing2 \font\x=cmr10 \x \letterspacefont\y=\x 100 \y \pdffontexpand\y 20 20 5 autoexpand ... \bye ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-12-21 16:09 Message: Logged In: YES user_id=421 A patch for this will be included in the next version (1.40). ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-12 17:47 Message: Logged In: YES user_id=710 oops, I disabled ligature for letter-spaced font, but this should not affect the base font. Will have to rethink. Most likely the syntax will change like follows: \letterspacefont\f=cmr10 at 11pt 100 \f text ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2006-12-12 15:50 Message: Logged In: YES user_id=2217 % and here's % (4) ligatures will be broken up, not only in the % letter-spaced font (which is probably acceptable), % but in all subsequent uses of the base font, too fi\par {\letterspacefont\lspfont=\font 100 \lspfont fi}\par fi \bye ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-12 13:31 Message: Logged In: YES user_id=710 I fixed (1) and (2); (3) is disabled now, ie you cannot expand a letter-spaced font. Please wait for another release from Martin. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106

1 0

[ pdftex-Patches-735 ] patch for simplified horizontal positional tracking
by noreply＠sarovar.org 19 Feb '07

19 Feb '07

Patches item #735, was opened at 2007-02-19 22:00 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=735&group_id=106 Category: Positioning Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) Summary: patch for simplified horizontal positional tracking Initial Comment: 1. simpler calculations for horizontal position update when inside []TJ arrays, now by pure additions within a fontsize/10000 raster; no rounding errors can accumulate. Gives about 7 % pdftex speed gain when typesetting fiction-type stuff. 2. writet3.c now also with standard /FontMatrix [0.001 0 0 0.001 0 0], tidied up a little (.pgc part untested). No need anymore (hope it's right) to handle PK fonts specially by adv_char_width() in pdftex.web. 3. wrong use of printf() at a few places corrected by Martin. Work in progess, not safe for production. Needs more testing, particularly with PK fonts. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=735&group_id=106

1 0

[ pdftex-Bugs-733 ] CVE-2007-0104
by noreply＠sarovar.org 16 Feb '07

16 Feb '07

Bugs item #733, was opened at 2007-02-16 15:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=733&group_id=106 Category: xpdf Group: v1.40.0 >Status: Closed >Resolution: Fixed Priority: 3 Submitted By: Martin Schröder (oneiros) Assigned to: Martin Schröder (oneiros) Summary: CVE-2007-0104 Initial Comment: Another bug in xpdf was found: http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-0104 http://projects.info-pull.com/moab/MOAB-06-01-2007.html As pdftex uses xpdf, this can be used to crash pdftex. A patch for this is attached and will be included in the next release. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=733&group_id=106

1 0

[ pdftex-Bugs-733 ] CVE-2007-0104
by noreply＠sarovar.org 16 Feb '07

16 Feb '07

Bugs item #733, was opened at 2007-02-16 15:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=733&group_id=106 Category: xpdf Group: v1.40.0 Status: Open Resolution: None Priority: 3 Submitted By: Martin Schröder (oneiros) Assigned to: Martin Schröder (oneiros) Summary: CVE-2007-0104 Initial Comment: Another bug in xpdf was found: http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-0104 http://projects.info-pull.com/moab/MOAB-06-01-2007.html As pdftex uses xpdf, this can be used to crash pdftex. A patch for this is attached and will be included in the next release. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=733&group_id=106

1 0

runptex API
by Thanh Han The 13 Feb '07

13 Feb '07

Hi, I have put the documented API of runptex, a wrapper to run pdftex, to http://runptex.sarovar.org/ Comments welcome very much. Source codes, installation and usage guide will be added soon. Thanh

1 0

Re: [NTG-pdftex] another problem -- of pdftex or gs?
by Thanh Han The 11 Feb '07

11 Feb '07

On Sat, Feb 10, 2007 at 10:52:09PM +0100, Thanh Han The wrote: > yes I also got very varying results from gs, depending on > version, configuration and also the output device. > However, I know of another way to check whether a ps file is > valid. sorry, typo. I *don't* know of another way to check ps files. Thanh

1 0

Re: [NTG-pdftex] another problem -- of pdftex or gs?
by Thanh Han The 10 Feb '07

10 Feb '07

Hi Reinhard, On Sat, Feb 10, 2007 at 09:58:12PM +0100, Reinhard Kotucha wrote: > I'm not sure that there is something wrong with the ps file and I'm > not able to reproduce this with gs-8.01. However, there are problems > with other versions. Some versions hang, so I had to limit CPU time > in order to ba able to check with all versions I have installed. > > [...] > > Curiously you get different results depending on -dNOPAUSE and > -dDEBUG. I tried with gs-7.22. > > [...] > > I suppose that gs is so buggy that it doesn't make sense to use it as > a validator. > > Maybe you get another result too if you add -dDEBUG too. > > In my opinion gs is too unstable to rely on it. yes I also got very varying results from gs, depending on version, configuration and also the output device. However, I know of another way to check whether a ps file is valid. The ps file I uploaded is probably too complex to analyze what is wrong with it. However I think the problem is that the ps doesn't contain all the needed fonts -- type3 fonts from the pdf are missing if they are used in XObject forms only. I recompiled the pdf with all fonts embedded as type1 or truetype, and then the ps is ok. > There are two ways to extract and examine Type1 fonts: > > 1. My Perl script xtractfonts extracts Type1 fonts from pdf files > (using pdftops at the moment but should work with acroread also) > and disassembles them using t1diasm. Adding Eddie's t1lint can be > done easily. > > 2. pdftosrc can be used to extract objects from a pdf file and Hartmut > successfully retrieved some fonts and disassembled them using the > t1utils. > > I suppose that pdftosrc can be used to extract other things too and > external programs can be used for validation. yes probably it's a good idea to extract all fonts from a pdf and check whether they are ok. I suppose this should not be hard to do using xpdf sources. > Thanh, I find http://www.sendspace.com extremely annoying. > > Unless you forgot your passwd you can copy files to > thanh(a)ms25.ath.cx/public_html and ask people to download them from > http://ms25.ath.cx/~thanh . ah, thanks for reminding me that. I will take use of it next time. Regards, Thanh

1 0

another problem -- of pdftex or gs?
by Thanh Han The 10 Feb '07

10 Feb '07

Hi, the following file caused gs to segfault: http://www.sendspace.com/file/ol6tlx The command I used is: ,-------- | gs -dNOPAUSE -sDEVICE=nullpage -sOutputFile=/dev/null -dBATCH survey-vn.ps `-------- and gs -v gave: ,-------- | GPL Ghostscript 8.01 (2004-01-30) | Copyright (C) 2004 artofcode LLC, Benicia, CA. All rights reserved. `-------- The ps file was converted by pdftops from survey-vn.pdf, the vietnamese translation of the free math font survey by Stephen G. Hartke, compiled by pdftex. The pdf itself and the ps converted by acroread didn't cause the problem with the above command. Another thing to notice is that the problem doesn't occur with other devices, for example gv showed the file quite normally, and the device ppm also works fine. Maybe some PS guru here (eg Reinhard) can figure out what is wrong with the ps file? Thanh

3 2

building a set of test files
by Thanh Han The 10 Feb '07

10 Feb '07

Hi, I am setting up a set of test files to check if there is some problem with pdftex. Those test files should be run after each change made to pdftex, hopefully to detect some errors before they slip to end users. Each file from the set is tested as follows: - recompile the test file - check whether the pdf is ok, using as many as possible available tools. At the moment the tools being used are listed in the script checkpdf I posted, plus pdftool from fitz. The output of such a check would look like: ,-------- | Checking microtype.pdf using pdfvalidator... | PDF library evaluation version, created Dec 2006 | Checking microtype.pdf using Multivalent Validate tool... | Checking microtype.pdf using Ghostscript... | Checking microtype.pdf using pdftoppm (xpdf)... | Checking microtype.pdf using pdftool (fitz)... | Printing microtype.pdf to microtype.ps using Acrobat Reader... | Checking microtype.ps using Ghostscript... | Printing microtype.pdf to microtype.ps using pdftops (xpdf)... | Checking microtype.ps using Ghostscript... | done. `-------- [Next version of xpdf will allow checking pdf using xpdf in "batch mode", ie without user interaction. This should catch more errors than pdftoppm] - then the pdf file is compared against another (verified) pdf to see if there are any differences. The comparison is done by: - using pdftoppm to print all pages from both pdf to images and compare the image (using diff) - if the images in the above step differ, use the 'compare' tool from ImageMagick to compare the images. If the difference is "big enough", the pages will be considered as "different". - at the moment the set consists of the following files: ,-------- | encguide - the latex encoding guide | microtype - the microtype manual | MnSymbol - the MnSymbol manual | mscore-sample - sample of mscore (TrueType) fonts | survey - the free math font survey | survey-vn - Vietnamese version of the survey `-------- Your comments are welcome. Thanh PS: while testing those files, I found one issue with pdf inclusion: if the included pdf contains any type3 font, the result will fail to print to PS by acroread (type3 fonts in XOject forms are not exported to PS). Maybe we need to write some warning if a type3 font is found during pdf inclusion.

1 0

Re: [NTG-pdftex] problem of acrobat reader 4.0 or pdftex?
by Thanh Han The 09 Feb '07

09 Feb '07

maybe it's related to this (copied from pdftex sources in older versions): ,-------- | @!pdf_first_space_corr: integer; {amount of first word spacing while drawing a string; | for some reason it is not taken into account of the length of the string, so we | have to save it in order to adjust spacing when string drawing is finished} `-------- I have verified this as follows: uncompressed microtype.pdf, used a text editor to find where the line 3.1 Micro-Typographic Options . . . . . . . . . . . . . . . . . . . . . . 6 is drawn. It looks as follows: ,-------- | /F95 9.9626 Tf 14.944 -13.993 Td [(3.1)-910(Micro-)37(T)93(ypographic)-278(Options)]TJ | 0 g 0 G | [-970(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)- 500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)-500(.)]TJ | 0 g 0 G | [-1740(6)]TJ `-------- According to the above note, the first space is not taken into account of the string length, so I tried to add it (ie -970) to the space after the current TJ operator (ie to -1740 in the following TJ, so now it became -2710). After this the digit 6 ended up aligned as expected (but now it looks bad in xpdf). Thanh On Thu, Feb 08, 2007 at 11:16:02PM +0100, Hartmut Henkel wrote: > On Thu, 8 Feb 2007, w.m.l(a)gmx.net wrote: > > > On 07.02.2007 10:45, Thanh Han The wrote: > > > while viewing the microtype manual (from texlive2007) using > > > acr4.0 on linux, I found some oddities as shown here: > > > > Same under Windows, Acrobat Reader 4.05. Additionally, the page numbers > > on the right-hand side in the TOC are completely mis-aligned. > > > > It appears fine when created with (miktex's) pdftex 1.30. > > this still uses \pdfliteral {} without "direct", so you find (lengthy) > coordinate transforms like this around color change commands in the PDF: > > 1 0 0 1 498.65 487.517 cm > 0 g 0 G > 1 0 0 1 -338.982 -13.027 cm > 0.02 0.04 0.48 rg 0.02 0.04 0.48 RG > 1 0 0 1 -159.668 -474.49 cm > > With pdftex-1.40 now hyperref seems to use the more compact \pdfliteral > direct {} version. > > > With 1.40, it looks OK if I set hyperref's colorlinks option to false > > (ie., have the links surrounded by boxes instead of coloured). > > then the color change commands between the []TJ sections go away. It > appears that acro4.0 doesn't like legal PDF like this: > > 0 g 0 G > /F51 8.9664 Tf 22.908 -11.955 Td [([)]TJ > 0.02 0.04 0.48 rg 0.02 0.04 0.48 RG > [(Protrusion)]TJ > 0 g 0 G > [-343(\025)-342(49])-370([)]TJ > 0.02 0.04 0.48 rg 0.02 0.04 0.48 RG % <--- acro4.0 bug with these lines > [(Expansion)]TJ > 0 g 0 G > [-343(\025)-342(56])-371([)]TJ > 0.02 0.04 0.48 rg 0.02 0.04 0.48 RG > [(In)29(terw)28(ord)-342(Spacing)-343(\050Glue\051)]TJ > > Regards, Hartmut > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

1 0

problem of acrobat reader 4.0 or pdftex?
by Thanh Han The 08 Feb '07

08 Feb '07

Hi, while viewing the microtype manual (from texlive2007) using acr4.0 on linux, I found some oddities as shown here: http://www.sendspace.com/file/25thl2 But the problem doesn't occur with acr7.0, xpdf or gv. So it's likely a bug of acr4 on linux? Thanh

4 4

Re: [NTG-pdftex] tools to check whether a pdf is invalid
by Thanh Han The 08 Feb '07

08 Feb '07

On Thu, Feb 08, 2007 at 02:41:47PM +0100, Martin Schroeder wrote: > 2007/2/8, Thanh Han The <hanthethanh(a)gmail.com>: > > if someone knows of another tool which can be added, please > > share your experience. Or if someone is interested in the > > script, I will post it here. > > Have a look at Fitz/Apparition at http://ccxvii.net/apparition/ thanks for the tip -- it seems to be somehow related to gs? How to you use this tool to check pdf? I took a quick look and use 'pdftool draw -r 72' as the command for checking. > And poppler also has the xpdf tools, probably with an improved pdf parser. > > And yes, I'm interested in the script. :-) I attached the script as a zip file. If it doesn't get to the ml, I will resend via private mail. Thanh

1 0