March 2011 - ntg-pdftex - NTG Mailing Lists

Fwd: [poppler] [PATCH] Fixup LaTeX composed characters
by Lev Bishop 30 Mar '11

30 Mar '11

> On 25-3-2011 2:40, Martin Schröder wrote: > > FYI. > > Don't ask me what's the problem with our PDF seems to be... > > indeed. > > if we even consider this for luatex, it should be an option that is not > applied by default ... tweaking an included pdf file should never happen > automatically as overlapping can be intentional ... I think the point of the message was not that pdftex should be fixing included files, but that pdftex should not be doing something that the pdf viewers then have to work around. As far as I understand it, the poppler people are complaining that copying accented text out of the pdf doesn't work right, because instead of an "á" character, the file contains "a" and the accent as separate glyphs, correctly positioned to look like if it was an "á", which is fine for viewing, but not for text-extraction. I suspect that this behaviour is too deeply embedded in tex to be easily fixable. Lev -- Lev Bishop Joint Quantum Institute

1 0

Fwd: [poppler] [PATCH] Fixup LaTeX composed characters
by Martin Schröder 25 Mar '11

25 Mar '11

FYI. Don't ask me what's the problem with our PDF seems to be... ---------- Forwarded message ---------- From: Tim Brody <tdb2(a)ecs.soton.ac.uk> Date: 2011/3/25 Subject: [poppler] [PATCH] Fixup LaTeX composed characters To: poppler(a)lists.freedesktop.org Hi All, Attached is a patch to address the previous problem I wrote about with pdflatex-produced PDFs that contain overlapping-diacritics/accents. This patch contains: - a table of diacritic to Unicode combining character code-points - if an overlapping character is detected checks whether the first (in stream-sequence) character is in the table - pops the diacritic off the word - appends the diacritic to the character as a Unicode combining character This does not fix \b{o} or \d{o} because TeX places them on the next line (so aren't detected as overlapping). Yes, this is an issue with pdflatex but there are 100,000s of TeX-produced PDFs for which we don't have source for ... -- All the best, Tim. _______________________________________________ poppler mailing list poppler(a)lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/poppler

2 1

[pdftex-Feature Requests][4333] Provide information about \write18 calls
by pdftex-featurerequests＠sarovar.org 18 Mar '11

18 Mar '11

Feature Requests item #4333, was opened at 2011-03-18 19:15 Status: Open Priority: 3 Submitted By: Martin Scharrer (martin_scharrer) Assigned to: Nobody (None) Summary: Provide information about \write18 calls Category: Interface Improvements (example) Group: None Resolution: None Initial Comment: Further information about \write18 calls should be provided. At the moment \pdfshellescape tells if shell escape is disabled, enabled or restricted in general but no status information is provided for specific \write18 calls. It would be very useful to be able to access the following information: * Was the program executed or disallowed because of restricted mode. In other words: Is the program listed as trusted or not. * Can the program be found? * Return code of the program that is executed. * Quoting specification for the command call. Using this information a package could test if the external program was really successfully executed or not and why and provide appropriate information to the user. References: This topic has been discussed as "Testing success of \write18" on comp.text.tex (http://groups.google.com/group/comp.text.tex/tree/browse_frm/thread/eee73e7…) and TeX.SX (http://tex.stackexchange.com/questions/13226/test-success-of-write18) ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=4333&group_id=106

1 0

[pdftex-Bugs][4332] pdflatex enters endless loop on malformed align-environment in nonstopmode
by pdftex-bugs＠sarovar.org 18 Mar '11

18 Mar '11

Bugs item #4332, was opened at 2011-03-18 13:28 Status: Open Priority: 3 Submitted By: Mike Rofone (mikerofone) Assigned to: Nobody (None) Summary: pdflatex enters endless loop on malformed align-environment in nonstopmode Category: Build process Group: v1.40.1 Resolution: None Initial Comment: On compiling the attached minimal example containing a malformed "align" environment, pdftex seems to enter an endless loop (does not terminate and 100% CPU load) if invoked as pdftex \nonstopmode \input{test.tex} which is how rubber seems to invoke pdftex. If run without nonstopmode, compilation immediately stops at an error prompt (as expected). I do not know if this is an error with the amsmath-package defining the align-environment, but as it looks a little similar to bug #909 ( http://sarovar.org/tracker/?func=detail&atid=493&aid=909&group_id=106 ) I hope that it does fit here. I do not have another LaTeX compiler to test with. Further detail: [mikerofone@ente ~/Desktop]$ pdflatex --version pdfTeX 3.1415926-1.40.11-2.2 (TeX Live 2010/Arch Linux) kpathsea version 6.0.0 Copyright 2010 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). There is NO warranty. Redistribution of this software is covered by the terms of both the pdfTeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the pdfTeX source. Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Compiled with libpng 1.4.5; using libpng 1.4.5 Compiled with zlib 1.2.5; using zlib 1.2.5 Compiled with poppler version 0.16.2 ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=4332&group_id=106

1 0

[pdftex-Feature Requests][4328] Avoid the generation of /ID optionally
by pdftex-featurerequests＠sarovar.org 10 Mar '11

10 Mar '11

Feature Requests item #4328, was opened at 2011-03-10 13:24 Status: Open Priority: 3 Submitted By: Jens Mueller (jens) Assigned to: Nobody (None) Summary: Avoid the generation of /ID optionally Category: PDF generation Group: v1.40 Resolution: None Initial Comment: pdftex will always set /ID in the file trailer. But setting it is optional, if /Encrypt is not set (see section 7.5.5 in ISO 32000-1; can be obtained here http://www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_2008.pdf) Because /ID is always set it will change for each run because the current time is used for generating it. This can be annoying because it makes regeneration of the very same PDF (looking at the file contents) very difficult (see e.g. http://superuser.com/questions/130347/how-do-i-produce-bytewise-consistent-…) I suggest to add a flag to pdftex that allows to disable the generation of \ID. Something like [-no]-id=<value> to disable the generation of \ID or specifying the value on command line. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=4328&group_id=106

1 0