- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-741 ] wrong colors for included PDF-image
by noreply＠sarovar.org 02 Mar '07

02 Mar '07

Bugs item #741, was opened at 2007-03-02 00:50 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=741&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Uwe Stöhr (stoehr) Assigned to: Nobody (None) Summary: wrong colors for included PDF-image Initial Comment: Attached is a PDF 1.4 image. When you include this to a document the output generated by pdfetex 1.30.6 the images looks different: The colors are much darker, see attached PDF result. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=741&group_id=106

1 0

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

01 Mar '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-03-01 21:07 Message: Logged In: YES user_id=710 here is a patch that makes disabling ligature optional -- a keyword "nolig" would do that: \letterspacefont\y=\x 100 nolig ---------------------------------------------------------------------- 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-721 ] Missing /Font object of PK file not found
by noreply＠sarovar.org 01 Mar '07

01 Mar '07

Bugs item #721, was opened at 2007-01-23 20:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: Accepted Priority: 7 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing /Font object of PK file not found Initial Comment: There are several cases, the buggy one is no. 3. See test files test1...4.tex in the attached file. 1. No TFM file found in the 1st place. ---> No TeX font will be started. Ok. See test1.tex. 2. TFM file found, map entry existing, but no PFB font file in map line ---> "pdfTeX warning: pdftex: font `CMR' is not a standard font; I suppose it is available to your PDF viewer then". Ok. See test2.tex. 3. TFM file found, no map entry, and no PK font available. ---> "pdfTeX warning: pdftex (file mf-nonexist): Font mf-nonexist at 600 not found". Not ok. See test3.tex. Here a /Font object is referenced, which is not existing, rendering the resulting PDF file buggy. There should be either pdftex_fail() or or at least a /Font object with a dummy /FontDescriptor object should be created (the latter filled with defaults from the TFM file), and the same warning should be given as in case 4 below, since these cases are similar: fontfile expected, but not available. 4. TFM file found, map entry with PFB font file existing, but no PFB font file found. ---> "pdfTeX warning: pdftex (file t1-nonexist.pfb): cannot open Type 1 font file for reading". /FontDescriptor without /FontFile, correct. Ok. See test4.tex. Regards, Hartmut ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-03-01 11:48 Message: Logged In: YES user_id=710 patch updated, a typo was in the previous one. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-03-01 08:58 Message: Logged In: YES user_id=710 Here is a patch to turn some warnings that can lead to invalid pdf output to fatal errors. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106

1 0

[ pdftex-Bugs-721 ] Missing /Font object of PK file not found
by noreply＠sarovar.org 01 Mar '07

01 Mar '07

Bugs item #721, was opened at 2007-01-23 20:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: Accepted Priority: 7 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Hartmut Henkel (hhenkel) Summary: Missing /Font object of PK file not found Initial Comment: There are several cases, the buggy one is no. 3. See test files test1...4.tex in the attached file. 1. No TFM file found in the 1st place. ---> No TeX font will be started. Ok. See test1.tex. 2. TFM file found, map entry existing, but no PFB font file in map line ---> "pdfTeX warning: pdftex: font `CMR' is not a standard font; I suppose it is available to your PDF viewer then". Ok. See test2.tex. 3. TFM file found, no map entry, and no PK font available. ---> "pdfTeX warning: pdftex (file mf-nonexist): Font mf-nonexist at 600 not found". Not ok. See test3.tex. Here a /Font object is referenced, which is not existing, rendering the resulting PDF file buggy. There should be either pdftex_fail() or or at least a /Font object with a dummy /FontDescriptor object should be created (the latter filled with defaults from the TFM file), and the same warning should be given as in case 4 below, since these cases are similar: fontfile expected, but not available. 4. TFM file found, map entry with PFB font file existing, but no PFB font file found. ---> "pdfTeX warning: pdftex (file t1-nonexist.pfb): cannot open Type 1 font file for reading". /FontDescriptor without /FontFile, correct. Ok. See test4.tex. Regards, Hartmut ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-03-01 08:58 Message: Logged In: YES user_id=710 Here is a patch to turn some warnings that can lead to invalid pdf output to fatal errors. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=721&group_id=106

1 0

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

28 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: 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-28 14:16 Message: Logged In: YES user_id=710 Here is an attempt to fix the bug. ---------------------------------------------------------------------- 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-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