- ntg-pdftex - NTG Mailing Lists

\expanded (was: Misleading cs names?)
by Heiko Oberdiek 11 Dec '07

11 Dec '07

Hello, On Sun, Dec 09, 2007 at 08:14:31PM +0100, Morten Høgholm wrote: > Usually the x expansion meant "uses \edef" and so they were all > non-expandable. But now that we have pdfeTeX'ed the l3 kernel, we have > functions doing full expansion like \numexpr and friends and \pdfstrcmp > (does \edef on both arguments) used in \tlist_if_eq:xxTF. This reminds me: > the notes from the Oldenburg meeting mentions an \expanded primitive: > \expanded <general text> > Expandable command returning the full expansion > of the tokens in <general text>. > So since this pretty much exists inside \pdfstrcmp as it is now, it could > go into pdfTeX 1.50 and we would be free of these problems. Except of > course, \expanded is already used a lot in ConTeXt with different > semantics. > > Any opinions from the ConTeXt/pdfTeX people here? I miss "\expanded", too. A workaround for a \detokenize with expanded argument: \pdfunescapehex{\pdfunescapehex{...}} For LuaTeX \pdf(|un)escapehex are defined in package `pdftexcmds': \pdf@unescapehex and \pdf@escapehex, both are expandable. Disadvantages of the workaround: * slower * no <general text>, but macro argument * detokenization happens. But I assume, you want only expansion, not detokenization? (then the latter can be achieved by \detokenize\expandafter{\expanded{...}}) Biggest problem is probably a good name: a) \expanded would be a nice name, but it clashes with ConTeXt. I remember trouble with \unexpanded :-( b) It would belong to e-TeX, but there isn't a e-TeX prefix: \etexexpanded or \etexexpand c) pdfTeX's convention with prefix "\pdf" (see \pdfstrcmp, \pdfescape*): \pdfexpanded or \pdfexpand d) longer names My preference is c) to avoid trouble with macro name clashes. I can live with a), then my package etexcmds would get a new macro \etex@expanded. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> PS: ntg-pdftex list added.

6 10

[ pdftex-Bugs-856 ] build.sh can't handle pathnames with spaces
by noreply＠sarovar.org 29 Nov '07

29 Nov '07

Bugs item #856, was opened at 2007-08-14 09:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106 Category: Build process Group: v1.40.4 Status: Open Resolution: Postponed >Priority: 1 Submitted By: Francky Leyn (leyn) Assigned to: Martin Schröder (oneiros) Summary: build.sh can't handle pathnames with spaces Initial Comment: Dear, I want to compile pdftex for cygwin. I untarred the distribution in /cygdrive/c/Document and Settings/Francky Leyn/My Documents/LaTeX leyn@newyork ~/LaTeX/pdftex-1.40.5 $ ./build.sh ... build.sh stops with the following error: configure: error: can not run /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file exists and is executable: $ ls -lh "/cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub" -rwx------+ 1 leyn None 32K Jul 31 19:00 /cygdrive/c/Documents and Settings/Francky Leyn/My Documents/LaTeX/pdftex- 1.40.5/build/../src/config/config.sub The file /cygdrive/c/Documents doesn't exist of course and that is why buid.sh stops its execution. Could the scripts be modified so that they can handle spaces? Best regards, Francky Leyn ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-08-15 01:52 Message: Logged In: YES user_id=421 I'm sorry, but fixing this needs a change in the whole autofoo system of TL, which is not likely to happen soon. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-08-14 10:50 Message: Logged In: YES user_id=421 This needs a new configure script; I've pushed this upstream (to TeXlive). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=856&group_id=106

1 0

[ pdftex-Bugs-884 ] Letterspacing and non-autoexpanded fonts
by noreply＠sarovar.org 29 Nov '07

29 Nov '07

Bugs item #884, was opened at 2007-11-27 10:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=884&group_id=106 Category: hz Group: v1.40.5 Status: Open Resolution: Accepted >Priority: 3 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: Letterspacing and non-autoexpanded fonts Initial Comment: While auto-expanding letterspaced fonts works fine now, there still is a problem with non-automatic expansion. The following will complain about a missing tfm file. It doesn't make a difference whether the expanded font instance is created from an mf file (like below), via `ExtendFont' in the map file, or even whether it was created from a MM font (ie., the expanded instance actually exists as a pfb file). The latter case is what bothers me the most. \pdfadjustspacing2 \pdfmapline{ cmr10} \pdfmapline{+cmr10+100} \font\cmr=cmr10 \cmr \letterspacefont\cmrls=\cmr 100 \pdffontexpand\cmrls 100 0 100 %autoexpand \cmrls Hamburgefonts\par \parfillskip 0pt Hamburgefonts \bye PS: what about the `invalid entry' complaint for the map lines? Are they not legal? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-27 11:05 Message: Logged In: YES user_id=421 A map line needs either a psname (for not-embedded fonts) or the file name (for embedded fonts) ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=884&group_id=106

1 0

[ pdftex-Bugs-741 ] wrong colors for included PDF-images (page groups)
by noreply＠sarovar.org 29 Nov '07

29 Nov '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: PDF inclusion Group: v1.30.0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Uwe Stöhr (stoehr) Assigned to: Martin Schröder (oneiros) Summary: wrong colors for included PDF-images (page groups) 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. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-29 15:49 Message: Logged In: YES user_id=421 A fix for this will be included in the next release (1.40.6/1.50.0). ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-03 20:51 Message: Logged In: YES user_id=421 Fix is in the works. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-01 07:08 Message: Logged In: YES user_id=421 Adding /Group to the /Page is not an option for us (and probably wrong): What should we do when we have more than one included pdf on a page and they have different /CS entries? And why does transparency in an /XObject need an entry in the /Page? The entry in the /XObject should suffice. I wouldn't be surprised if AR is faulty here. ---------------------------------------------------------------------- Comment By: Adrian Johnson (ajohnson) Date: 2007-10-01 02:04 Message: Logged In: YES user_id=4699 After adding /Group << /CS /DeviceRGB /Type /Group /S /Transparency >> to the /Page object in newfile2-1.pdf it displays correctly in Acrobat. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-01 01:04 Message: Logged In: YES user_id=421 The attached file newfile2-1.pdf has a copied page group, which as I now know, should be correct. Still, AR8@Linux shows different colours for it and TestSkizze.pdf . ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-10-01 00:51 Message: Logged In: YES user_id=3168 > Why is this WONTFIX? Sorry, this bug was once closed when this additional info was not available. -> I reopened this bug. ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-10-01 00:46 Message: Logged In: YES user_id=3168 Why is this WONTFIX? I mean: > The file TestSkizze.pdf specifies the color blending space > with "/CS /DeviceRGB" in the transparency group. In > the PDF produced by pdftex this has been stripped out. So the bug is that pdftex strips out the color space. If you really think it's WONTFIX, then tell me what is the correct way of specifying the color space so that I can forward this to the Inkscape developers. ---------------------------------------------------------------------- Comment By: Adrian Johnson (ajohnson) Date: 2007-09-30 15:34 Message: Logged In: YES user_id=4699 The file TestSkizze.pdf specifies the color blending space with "/CS /DeviceRGB" in the transparency group. In the PDF produced by pdftex this has been stripped out. When the color space is not specified Acrobat defaults to CMYK. This results in RGB colors being converted to CMYK, blended in CMYK color space, then converted back to RGB. This will produce different results compared to blending the colors in RGB space. This problem was also reported to the cairo list: http://lists.cairographics.org/archives/cairo/2007-September/011471.html ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-03-03 19:41 Message: Logged In: YES user_id=3168 > To my eye the Harlequin results are the same for both > file, Yes and the result is correct. > while Jaws has to different results. In my eyes the Jaws results are identical but wrong. So it seems that pdftex is not the problem here, but it would be nice if pdftex could handle page groups in one of the next releases: >"PDF inclusion: Page Group detected which pdfTeX can't > handle. Ignoring it." So I'm not sure to close this bug or mark it as enhancement. Thanks for your help. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-03 15:48 Message: Logged In: YES user_id=421 I've attached the results of two professional RIPs: Global Graphics Jaws & Harlequin. To my eye the Harlequin results are the same for both file, while Jaws has to different results. :-{ ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-02 13:16 Message: Logged In: YES user_id=421 Your document is using Page Groups (see PDF Reference 7.3.6). Including pdfs that use this is a grey area; see the notes in NEWS and pdftoepdf.cc. It works most of the times and with most RIPs. I'll look into it again, but I don't have much hope. Btw: pdftex warns you: "PDF inclusion: Page Group detected which pdfTeX can't handle. Ignoring it." ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-03-02 13:05 Message: Logged In: YES user_id=3168 > problem in AR7 - but only there. But how could this be a bug in Acrobat when Adobe set the standards? Why is this correctly shown before the pdftex-run. The display is the same here in Acrobat 5 - 8 so I think they would have fixed it when it's a bug since Acrobat 5. Hmm but OK, when I open the result with GSview besides the GS bug, the color tones are correctly be displayed. So close this bug report again, when you are sure that pdftex follows here exactly the PDF-specification. ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-03-02 12:57 Message: Logged In: YES user_id=3168 > It's a bug in AR; No! Acrobat is correct: I created this image with Inkscape 0.45 and exported it the as PDF. I designed e.g. the green as light green. And Acrobat 7 and 8 shows this exactly as designed while the pdftex result has wrong color tones, see the attached screenshots. (Ghostscript is btw. not able to render the PDF-image correctly - I reported this to the GS people who confirmed it.) ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-02 01:05 Message: Logged In: YES user_id=421 You don't say it, but I see the same problem in AR7 - but only there. It's a bug in AR; try kpdf or ghostscript instead. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=741&group_id=106

1 0

[ pdftex-Bugs-884 ] Letterspacing and non-autoexpanded fonts
by noreply＠sarovar.org 27 Nov '07

27 Nov '07

Bugs item #884, was opened at 2007-11-27 10:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=884&group_id=106 Category: hz Group: v1.40.5 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: Letterspacing and non-autoexpanded fonts Initial Comment: While auto-expanding letterspaced fonts works fine now, there still is a problem with non-automatic expansion. The following will complain about a missing tfm file. It doesn't make a difference whether the expanded font instance is created from an mf file (like below), via `ExtendFont' in the map file, or even whether it was created from a MM font (ie., the expanded instance actually exists as a pfb file). The latter case is what bothers me the most. \pdfadjustspacing2 \pdfmapline{ cmr10} \pdfmapline{+cmr10+100} \font\cmr=cmr10 \cmr \letterspacefont\cmrls=\cmr 100 \pdffontexpand\cmrls 100 0 100 %autoexpand \cmrls Hamburgefonts\par \parfillskip 0pt Hamburgefonts \bye PS: what about the `invalid entry' complaint for the map lines? Are they not legal? ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-11-27 11:05 Message: Logged In: YES user_id=421 A map line needs either a psname (for not-embedded fonts) or the file name (for embedded fonts) ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=884&group_id=106

1 0

[ pdftex-Bugs-884 ] Letterspacing and non-autoexpanded fonts
by noreply＠sarovar.org 27 Nov '07

27 Nov '07

Bugs item #884, was opened at 2007-11-27 09:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=884&group_id=106 Category: hz Group: v1.40.5 Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: Letterspacing and non-autoexpanded fonts Initial Comment: While auto-expanding letterspaced fonts works fine now, there still is a problem with non-automatic expansion. The following will complain about a missing tfm file. It doesn't make a difference whether the expanded font instance is created from an mf file (like below), via `ExtendFont' in the map file, or even whether it was created from a MM font (ie., the expanded instance actually exists as a pfb file). The latter case is what bothers me the most. \pdfadjustspacing2 \pdfmapline{ cmr10} \pdfmapline{+cmr10+100} \font\cmr=cmr10 \cmr \letterspacefont\cmrls=\cmr 100 \pdffontexpand\cmrls 100 0 100 %autoexpand \cmrls Hamburgefonts\par \parfillskip 0pt Hamburgefonts \bye PS: what about the `invalid entry' complaint for the map lines? Are they not legal? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=884&group_id=106

1 0

[ pdftex-Patches-880 ] Support reordering of pages
by noreply＠sarovar.org 26 Nov '07

26 Nov '07

Patches item #880, was opened at 2007-11-13 10:45 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=880&group_id=106 Category: Primitives Group: v1.50.0 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Martin Schröder (oneiros) Summary: Support reordering of pages Initial Comment: In order to e.g. allow the generation of tocs in one pass, pdftex should allow the manipulation of the page tree to reorder the pages. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-26 16:35 Message: Logged In: YES user_id=421 This patch will be included in the upcoming 1.50 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-26 15:12 Message: Logged In: YES user_id=421 Attached is an example use in LaTeX; use at your own risk. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-11-25 16:59 Message: Logged In: YES user_id=929 added README file describing how these commands ought to work. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-11-24 01:01 Message: Logged In: YES user_id=929 this patch against today's pdftex-svn should now also handle \pdfpageundivert. Lists and tree generation are now separated. But \pdfpagedivnum will be difficult as it's known only at shipout time. Thanks to Martin for the handy pages_entry structure. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-23 17:12 Message: Logged In: YES user_id=421 Attached is a first stab at a patch supporting page diversions like in m4 with \pdfpagedivert. \pdfpageundivert exists but doesn't work yet. \pdfpagedivnum is missing. Thanks to Hartmut for providing the idea and the first code. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=880&group_id=106

1 0

[ pdftex-Patches-880 ] Support reordering of pages
by noreply＠sarovar.org 26 Nov '07

26 Nov '07

Patches item #880, was opened at 2007-11-13 10:45 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=880&group_id=106 Category: Primitives Group: v1.50.0 Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Martin Schröder (oneiros) Summary: Support reordering of pages Initial Comment: In order to e.g. allow the generation of tocs in one pass, pdftex should allow the manipulation of the page tree to reorder the pages. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-11-26 15:12 Message: Logged In: YES user_id=421 Attached is an example use in LaTeX; use at your own risk. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-11-25 16:59 Message: Logged In: YES user_id=929 added README file describing how these commands ought to work. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-11-24 01:01 Message: Logged In: YES user_id=929 this patch against today's pdftex-svn should now also handle \pdfpageundivert. Lists and tree generation are now separated. But \pdfpagedivnum will be difficult as it's known only at shipout time. Thanks to Martin for the handy pages_entry structure. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-23 17:12 Message: Logged In: YES user_id=421 Attached is a first stab at a patch supporting page diversions like in m4 with \pdfpagedivert. \pdfpageundivert exists but doesn't work yet. \pdfpagedivnum is missing. Thanks to Hartmut for providing the idea and the first code. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=880&group_id=106

1 0

[ pdftex-Patches-880 ] Support reordering of pages
by noreply＠sarovar.org 25 Nov '07

25 Nov '07

Patches item #880, was opened at 2007-11-13 10:45 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=880&group_id=106 Category: Primitives Group: v1.50.0 Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Martin Schröder (oneiros) Summary: Support reordering of pages Initial Comment: In order to e.g. allow the generation of tocs in one pass, pdftex should allow the manipulation of the page tree to reorder the pages. ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2007-11-25 16:59 Message: Logged In: YES user_id=929 added README file describing how these commands ought to work. ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2007-11-24 01:01 Message: Logged In: YES user_id=929 this patch against today's pdftex-svn should now also handle \pdfpageundivert. Lists and tree generation are now separated. But \pdfpagedivnum will be difficult as it's known only at shipout time. Thanks to Martin for the handy pages_entry structure. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-23 17:12 Message: Logged In: YES user_id=421 Attached is a first stab at a patch supporting page diversions like in m4 with \pdfpagedivert. \pdfpageundivert exists but doesn't work yet. \pdfpagedivnum is missing. Thanks to Hartmut for providing the idea and the first code. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=880&group_id=106

1 0

[ pdftex-Support Requests-883 ] How to allow Adobe Reader comments on generated pdf files?
by noreply＠sarovar.org 24 Nov '07

24 Nov '07

Support Requests item #883, was opened at 2007-11-24 02:17 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=494&aid=883&group_id=106 Category: None Group: None >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Axel Boldt (axelboldt) Assigned to: Nobody (None) Summary: How to allow Adobe Reader comments on generated pdf files? Initial Comment: Hi, thanks a lot for pdftex, wonderful program. When I create a PDF file using pdflatex and view it with Adobe Reader 8.1.1, under Documents/Security I see "Commenting: Not allowed". This means that my correspondents can't add little yellow sticky notes to my file using their Adobe Reader's annotation feature. Is there a pdftex option with which I can allow commenting? Thanks and cheers, Axel Boldt ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-11-24 02:30 Message: Logged In: YES user_id=421 No. Search the list archives and see http://en.wikipedia.org/wiki/Adobe_LiveCycle_Reader_Extensions ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=494&aid=883&group_id=106

1 0