May 2006 - ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-565 ] ttf2afm fails to include characters specified with uniXXXX
by noreply＠sarovar.org 29 May '06

29 May '06

Bugs item #565, was opened at 2006-05-29 14:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=565&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mike Spivey (spivey) Assigned to: Nobody (None) Summary: ttf2afm fails to include characters specified with uniXXXX Initial Comment: If characters are specified in an encoding vector as uniXXXX (with XXXX a hexadecimal unicode value), then these characters are not included in the AFM output, unlike characters that are specified by name. The same goes for characters specifed by position. A suggested patch is attached. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=565&group_id=106

1 0

[ pdftex-Bugs-564 ] cannot compile pdftex under cygwin anymore
by noreply＠sarovar.org 26 May '06

26 May '06

Bugs item #564, was opened at 2006-05-26 06:01 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=564&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: Nobody (None) Summary: cannot compile pdftex under cygwin anymore Initial Comment: I've recently updated my cygwin system, and since then am not able to compile pdftex anymore. gcc -v gives: | gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125) The last lines of build.sh's output are: | srcdir=../../../src/texk/web2c /bin/sh ../../../src/texk/web2c/web2c/convert tangleboot | gcc -DHAVE_CONFIG_H -I. -I../../../src/texk/web2c -I.. -I../../../src/texk/web2c/.. -g -O2 -c tangleboot.c -o tangleboot.o | In file included from tangleboot.c:94: | tangleboot.h:34: error: conflicting types for 'getline' | /usr/include/sys/stdio.h:31: error: previous declaration of 'getline' was here | tangleboot.h:34: error: conflicting types for 'getline' | /usr/include/sys/stdio.h:31: error: previous declaration of 'getline' was here | make: *** [tangleboot.o] Error 1 What to do? ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-05-26 06:35 Message: Logged In: NO It's a bug in Cygwin. See the following links: http://www.mail-archive.com/tetex@dbs.uni-hannover.de/msg00961.html http://ftp.tug.org/mail/archives/pdftex/2006-February/006370.html Best, v. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=564&group_id=106

1 0

[ pdftex-Bugs-564 ] cannot compile pdftex under cygwin anymore
by noreply＠sarovar.org 26 May '06

26 May '06

Bugs item #564, was opened at 2006-05-26 00:31 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=564&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: Nobody (None) Summary: cannot compile pdftex under cygwin anymore Initial Comment: I've recently updated my cygwin system, and since then am not able to compile pdftex anymore. gcc -v gives: | gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125) The last lines of build.sh's output are: | srcdir=../../../src/texk/web2c /bin/sh ../../../src/texk/web2c/web2c/convert tangleboot | gcc -DHAVE_CONFIG_H -I. -I../../../src/texk/web2c -I.. -I../../../src/texk/web2c/.. -g -O2 -c tangleboot.c -o tangleboot.o | In file included from tangleboot.c:94: | tangleboot.h:34: error: conflicting types for 'getline' | /usr/include/sys/stdio.h:31: error: previous declaration of 'getline' was here | tangleboot.h:34: error: conflicting types for 'getline' | /usr/include/sys/stdio.h:31: error: previous declaration of 'getline' was here | make: *** [tangleboot.o] Error 1 What to do? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=564&group_id=106

1 0

[ pdftex-Bugs-555 ] pdfLaTeX coredumps on OpenBSD
by noreply＠sarovar.org 20 May '06

20 May '06

Bugs item #555, was opened at 2006-05-20 14:16 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=555&group_id=106 Category: None Group: v1.30.0 Status: Open Resolution: None Priority: 5 Submitted By: Dag Leine (dag) Assigned to: Nobody (None) Summary: pdfLaTeX coredumps on OpenBSD Initial Comment: I've found, that pdfLaTeX coredumps on OpenBSD if I use amsmath and microtype in some math environments. Here is a minimal latex document for showing the bug: > cat minidump.tex \documentclass{article} \usepackage{amsmath} \usepackage{microtype} \setlength{\parindent}{0pt} \begin{document} \begin{align} x \end{align} \end{document} % end of minidump.tex > pdflatex minidump This is pdfeTeX, Version 3.141592-1.30.6-2.2 (Web2C 7.5.5) entering extended mode (./minidump.tex LaTeX2e <2003/12/01> Babel <v3.8d> and hyphenation patterns for american, french, german, ngerman, b ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur kish, ukrainian, nohyphenation, loaded. (/usr/local/share/texmf-dist/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/local/share/texmf-dist/tex/latex/base/size10.clo)) (/usr/local/share/texmf-dist/tex/latex/amsmath/amsmath.sty For additional information on amsmath, use the `?' option. (/usr/local/share/texmf-dist/tex/latex/amsmath/amstext.sty (/usr/local/share/texmf-dist/tex/latex/amsmath/amsgen.sty)) (/usr/local/share/texmf-dist/tex/latex/amsmath/amsbsy.sty) (/usr/local/share/texmf-dist/tex/latex/amsmath/amsopn.sty)) (/usr/local/share/texmf-dist/tex/latex/microtype/microtype.sty (/usr/local/share/texmf-dist/tex/latex/graphics/keyval.sty) (/usr/local/share/texmf-dist/tex/latex/microtype/microtype.cfg)) (./minidump.aux) (/usr/local/share/texmf-dist/tex/latex/microtype/mt-cmr.cfg)Segmentation fault (core dumped) A quick look with gdb shows, that it hangs in line 4396 of pdfetex2.c: c = getrpcode ( f , mem [p ].hh.b1 ) ; Here p=999996 and f=-4096 Since f seems to be a table index to pdffontrbase a negative value does not make sense to my mind. I've tryed the same on a LINUX machine. There pdfLaTeX does not crash, but p and f have the same values as under OpenBSD. As the most bad work around after taking *Word I've added a line of code which leaves the routine if f becomes negative. This seems to work in the sense, that there isn't any more a core dump. regards Dag ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=555&group_id=106

1 0

[ pdftex-Feature Requests-429 ] Generate Tagged PDF
by noreply＠sarovar.org 16 May '06

16 May '06

Feature Requests item #429, was opened at 2005-09-12 04:07 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=429&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 4 Submitted By: Timothy O'Brien (oberon101) Assigned to: Martin Schröder (oneiros) Summary: Generate Tagged PDF Initial Comment: Adobe Reader has a'reflow' feature that allows visually impaired users to zoom into properly formatted documents and read them without having to move the viewable area back and forth across the page. PDFs made in MikteX eith pdfte are not properly formatted and reflow without interword spacing, redering them unreadable. I contacted the MikteX people and they referred me here. I beleive Scientific Word also uses pdftex with the same result. Any chance this could be fixed? ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-05-16 17:19 Message: Logged In: NO " The main problem with reflowing is not the missing tags but that pdftex writes interword spaces as a kern (since there is no "space" in TeX, of course). " No, the main problem is that Adobe Reader dropped recognition of "words" based on *spacing* and resorted to the the simplistic approach to use *spaces* instead. This is simply ignorance of Adobe about TeX. Instead of whining about this one can do something for a practical cure: add dummy spaces at the end of every word of zero width which consist of a *space* and a kern -\wd(space). space could come from any font producing explicit spaces in the output (e.g. cmtt). It is most easily done with VF's. As far as I remember a real implementation is already there in Vtex (with some option). " non-trivial: - first pdfTeX would have to be extended with primites for a structure tree (and classes and packages would have to use these primitives) - then primitives for tagging the content are needed and must be used " i) when generating PS-code and distilling via Adobe Distiller there should be no problem to take care of pdfmarks created by classes & packages... ii) I consider the major problem is page building and page dependency of marked contents. It is just like the difficulty to get consistent color in TeX: one can consider color as sort of a "tag". E.g. a marked TeX paragraph is broken accross pages with (tagged) headers and the structure should in general kept linked also under the condition of reordered pages. I suggest first to define what functionality is required at the side of the PDF-Reader (text extraction, save as XML or audio output via screen reader). The packages should then be able to save Latex macro structure as pdfmarks for pdf tags as a prerequisite. Support of pagebreaking of tagged objects will require some assistance from pdftex like linebreaking of weblinks. HS ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2006-05-06 20:50 Message: Logged In: YES user_id=2217 The main problem with reflowing is not the missing tags but that pdftex writes interword spaces as a kern (since there is no "space" in TeX, of course). A rather simple but effective way would be to write the interword spaces in a different font (e.g. non-embedded Times-Roman), and then compensate for the difference between Times's width of space and the width of the glue calculated by TeX. (At least, this is what Distiller does, if you select "Advanced -> Accessibility -> Add Tags to Document".) So that (This)-419(is)-420(an)-419(example) will be turned into: /T1_0 1 Tf (This)Tj /T1_1 1 Tf ( )Tj /T1_0 1 Tf 2.369 0 Td (is)Tj /T1_1 1 Tf ( )Tj /T1_0 1 Tf 1.092 0 Td (an)Tj /T1_1 1 Tf ( )Tj /T1_0 1 Tf 1.475 0 Td (example)Tj where T1_0 is cmr10 and T1_1 is Times-Roman. This would be already a major enhancement with respect to accessibility without any packages being required. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-04-14 17:03 Message: Logged In: NO Maybe a first version can use a very low-level solution, just with a single tagging primitive; there is such a command already (I think it is called pdfliteral) . And the tree can come later. So one could start with little work, assuming one knows tagging. CS ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-04-14 16:42 Message: Logged In: YES user_id=421 I'm changing the summary. Yes, we are aware that tagged pdf is an often requested feature, but implementing it would be non-trivial: - first pdfTeX would have to be extended with primites for a structure tree (and classes and packages would have to use these primitives) - then primitives for tagging the content are needed and must be used ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2005-11-05 01:28 Message: Logged In: NO I would volonteer to test the feature. I am writing a rather long pdf produced with pdftex that is downloadable for free ( http://www.motionmountain.net ) and readers regularly ask why it cannot be read aloud. Pdftex probably would only need to be extended with a single command - something like \writetaghere{tagtype} - and all the rest could be done by extensions to the latex cls and sty files. CS ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=429&group_id=106

1 0

[ pdftex-Bugs-548 ] Forwarded problem with Test.jpg
by noreply＠sarovar.org 10 May '06

10 May '06

Bugs item #548, was opened at 2006-05-10 18:00 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=548&group_id=106 Category: Image inclusion Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Heiko Oberdiek (oberdiek) Assigned to: Martin Schröder (oneiros) Summary: Forwarded problem with Test.jpg Initial Comment: Hello, in de.comp.text.tex Simon Eugster has problems with a jpg file: http://livingshadow.uttx.net/uploads/Test.jpg (Message-ID: <1147112925.079314.323190(a)v46g2000cwv.googlegroups.com>) I don't have a JPEG validator, but mozilla/firefox/ImageMagick/xzgv/file don't show any sign of problems with the JPEG file. Also I could reproduce his problems with pdfTeX 1.40.0-beta-20060213: \pdfximage{Test.jpg} | Error: pdftex (file ./Test.jpg): reading JPEG image failed | ==> Fatal error occurred, no output PDF file produced! Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-05-10 21:50 Message: Logged In: YES user_id=929 The test for JFIF file format was not adequate. Please test the patch. Bear in mind that currently only JFIF files allow to extract the image resolution values. For all others either explicitly give the wished dimensions (usual way), or set \pdfimageresolution. Else you get some default resolution. The problem went away also after treating Test.jpg (which is an EXIF file) by jhead -de, as this removed all EXIF headers. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=548&group_id=106

1 0

[ pdftex-Bugs-548 ] Forwarded problem with Test.jpg
by noreply＠sarovar.org 10 May '06

10 May '06

Bugs item #548, was opened at 2006-05-10 18:00 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=548&group_id=106 Category: Image inclusion Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Heiko Oberdiek (oberdiek) Assigned to: Martin Schröder (oneiros) Summary: Forwarded problem with Test.jpg Initial Comment: Hello, in de.comp.text.tex Simon Eugster has problems with a jpg file: http://livingshadow.uttx.net/uploads/Test.jpg (Message-ID: <1147112925.079314.323190(a)v46g2000cwv.googlegroups.com>) I don't have a JPEG validator, but mozilla/firefox/ImageMagick/xzgv/file don't show any sign of problems with the JPEG file. Also I could reproduce his problems with pdfTeX 1.40.0-beta-20060213: \pdfximage{Test.jpg} | Error: pdftex (file ./Test.jpg): reading JPEG image failed | ==> Fatal error occurred, no output PDF file produced! Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=548&group_id=106

1 0

[ pdftex-Feature Requests-429 ] Generate Tagged PDF
by noreply＠sarovar.org 06 May '06

06 May '06

Feature Requests item #429, was opened at 2005-09-11 22:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=429&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 4 Submitted By: Timothy O'Brien (oberon101) Assigned to: Martin Schröder (oneiros) Summary: Generate Tagged PDF Initial Comment: Adobe Reader has a'reflow' feature that allows visually impaired users to zoom into properly formatted documents and read them without having to move the viewable area back and forth across the page. PDFs made in MikteX eith pdfte are not properly formatted and reflow without interword spacing, redering them unreadable. I contacted the MikteX people and they referred me here. I beleive Scientific Word also uses pdftex with the same result. Any chance this could be fixed? ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2006-05-06 15:20 Message: Logged In: YES user_id=2217 The main problem with reflowing is not the missing tags but that pdftex writes interword spaces as a kern (since there is no "space" in TeX, of course). A rather simple but effective way would be to write the interword spaces in a different font (e.g. non-embedded Times-Roman), and then compensate for the difference between Times's width of space and the width of the glue calculated by TeX. (At least, this is what Distiller does, if you select "Advanced -> Accessibility -> Add Tags to Document".) So that (This)-419(is)-420(an)-419(example) will be turned into: /T1_0 1 Tf (This)Tj /T1_1 1 Tf ( )Tj /T1_0 1 Tf 2.369 0 Td (is)Tj /T1_1 1 Tf ( )Tj /T1_0 1 Tf 1.092 0 Td (an)Tj /T1_1 1 Tf ( )Tj /T1_0 1 Tf 1.475 0 Td (example)Tj where T1_0 is cmr10 and T1_1 is Times-Roman. This would be already a major enhancement with respect to accessibility without any packages being required. ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-04-14 11:33 Message: Logged In: NO Maybe a first version can use a very low-level solution, just with a single tagging primitive; there is such a command already (I think it is called pdfliteral) . And the tree can come later. So one could start with little work, assuming one knows tagging. CS ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-04-14 11:12 Message: Logged In: YES user_id=421 I'm changing the summary. Yes, we are aware that tagged pdf is an often requested feature, but implementing it would be non-trivial: - first pdfTeX would have to be extended with primites for a structure tree (and classes and packages would have to use these primitives) - then primitives for tagging the content are needed and must be used ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2005-11-04 19:58 Message: Logged In: NO I would volonteer to test the feature. I am writing a rather long pdf produced with pdftex that is downloadable for free ( http://www.motionmountain.net ) and readers regularly ask why it cannot be read aloud. Pdftex probably would only need to be extended with a single command - something like \writetaghere{tagtype} - and all the rest could be done by extensions to the latex cls and sty files. CS ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=429&group_id=106

1 0

bug in utils.c of pdftex-1.40-beta-20060213
by Hartmut Henkel 02 May '06

02 May '06

there is a silly but mostly harmless buffer overrun while reading array p, sorry. Below is a patch. Regards, Hartmut --- utils.c.orig 2006-01-21 02:56:17.000000000 +0100 +++ utils.c 2006-05-01 20:48:35.000000000 +0200 @@ -1237,7 +1262,7 @@ { enum { NONUM, DOTNONUM, INT, DOT, LEADDOT, FRAC } s = NONUM, t = NONUM; char *p, *q, *r; - for (p = q = r = a; *q != '\0';) { + for (p = q = r = a; *p != '\0';) { switch (s) { case NONUM: if (*p >= '0' && *p <= '9') @@ -1296,5 +1321,6 @@ *q++ = *p++; t = s; } + *q = '\0'; return a; }

1 0

/Type/FontDescriptor missing
by Hartmut Henkel 01 May '06

01 May '06

it seems that since quite some time and still in 1.40-beta-20060213 font descriptors are not marked by /Type/FontDescriptor which is "required" by PDF Ref. version 1.6, section 5.7, table 5.19. But it seems to be ok also without :-) I'll try to add this. Regards, Hartmut

1 0