- ntg-pdftex - NTG Mailing Lists

epdfview
by Rolf Niepraschk 21 Apr '06

21 Apr '06

Simple PDF viewer using poppler without Gnome dependency. ==> http://www.emma-soft.com/projects/epdfview/ ...Rolf

3 2

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

14 Apr '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-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-Feature Requests-429 ] Generate Tagged PDF
by noreply＠sarovar.org 14 Apr '06

14 Apr '06

Feature Requests item #429, was opened at 2005-09-12 00: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: Martin Schröder (oneiros) Date: 2006-04-14 13: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 20: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

[ pdftex-Bugs-509 ] invalid pdf created if font name contains space
by noreply＠sarovar.org 14 Apr '06

14 Apr '06

Bugs item #509, was opened at 2006-04-13 20:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106 Category: Fonts Group: v1.40.0 Status: Open Resolution: None Priority: 3 Submitted By: Tom Bishop (tbishop) Assigned to: Hartmut Henkel (hhenkel) Summary: invalid pdf created if font name contains space Initial Comment: pdftex 3.141592-1.30.4-2.2 runs the following code without complaining: \pdfmapline{+mssong4e <mssong.ttf <mssong4e.enc} \font\testfont=mssong4e at 20pt \testfont\char"00 \bye -- but the resulting pdf file can't be opened by Adobe Reader or GhostScript. GhostScript reports "Unknown operator: Song". The pdf file includes "/BaseFont /FEVAQU+MS Song". Evidently, the problem is the space in "MS Song", because if I use a hex editor to replace the space with an underscore, then the pdf becomes OK. The same font worked fine with earlier pdftex versions. It's a Chinese Unicode TrueType font, from Microsoft. I haven't tried installing pdftex 1.30.6; is it possible that would fix the problem? I just re-installed TeX using i-Installer for Mac OS X; it still uses pdftex 1.30.4. Here is the output of pdftex when running the test file: This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5) entering extended mode (./test3.tex [1{/Users/tbishop/Library/texmf/fonts/map/pdftex/ updmap/pdftex.map }] )</usr/local/teTeX/share/texmf.tetex/fonts/type1/bluesky/cm/ cmr10.pfb>{/usr/ local/teTeX/share/texmf.local/fonts/enc/pdftex/enc/mssong4e.enc} </usr/local/teT eX/share/texmf.local/fonts/truetype/mssong.ttf> Output written on test3.pdf (1 page, 5067 bytes). Transcript written on test3.log. Thanks in advance for any help! Best wishes, Tom Bishop (wenlin(a)wenlin.com) ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-14 00:16 Message: Logged In: YES user_id=929 well, the PDF ref. says to strip the spaces, and i don't know what consequences such underscores would have. So it seems that just stripping spaces might be a little bit closer to the right thing (in the view that this is only with buggy fonts anyway). ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-04-13 23:58 Message: Logged In: YES user_id=927 why not replace spaces by underscore (just as a precaution) ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 23:25 Message: Logged In: YES user_id=929 patch makes pdftex lenient with (buggy) TTF fonts that have spaces in PostScript name, strips spaces in /BaseFont and /FontName, e. g.: "MS Song" ---> "MSSong" ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 22:54 Message: Logged In: YES user_id=929 ah, after the PDF reference 5. ed. page 388 in case there would be no PostScript name entry we could be cruesome and strip the blank. But there is a wrong PostScript name in the font. So maybe one could flag a warning (or not?) and just strip the blank? (which would be easy) Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 22:39 Message: Logged In: YES user_id=929 This mssong.ttf version seems to be buggy. Here is a diagnostic printout from function ttf_read_name() in writettf.c; these are all available entries from the "Naming Table": i=0 platform_id=1 encoding_id=0 name_id=0 name <(c) Copyright ZHUHAI Stone Computerized typesetting system R&D LTD., 1995-1996> i=1 platform_id=1 encoding_id=0 name_id=1 name <MS Song> i=2 platform_id=1 encoding_id=0 name_id=2 name <Regular> i=3 platform_id=1 encoding_id=0 name_id=3 name <Microsoft:MS Song:1996> i=4 platform_id=1 encoding_id=0 name_id=4 name <MS Song> i=5 platform_id=1 encoding_id=0 name_id=5 name <Version 1.00> i=6 platform_id=1 encoding_id=0 name_id=6 name <MS Song> ---> ttf_read_name <MS Song> There is no usable PostScript name in: The TTF standard tells that under name_id=6 there should be the Postscript font, but here it is "MS Song" with a blank. As long as the font does not contain a valid PostScript name, i have no idea how to tweak this correctly... Other clues anybody? Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106

1 0

[ pdftex-Bugs-509 ] invalid pdf created if font name contains space
by noreply＠sarovar.org 14 Apr '06

14 Apr '06

Bugs item #509, was opened at 2006-04-13 18:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106 Category: Fonts Group: v1.40.0 Status: Open Resolution: None Priority: 3 Submitted By: Tom Bishop (tbishop) Assigned to: Hartmut Henkel (hhenkel) Summary: invalid pdf created if font name contains space Initial Comment: pdftex 3.141592-1.30.4-2.2 runs the following code without complaining: \pdfmapline{+mssong4e <mssong.ttf <mssong4e.enc} \font\testfont=mssong4e at 20pt \testfont\char"00 \bye -- but the resulting pdf file can't be opened by Adobe Reader or GhostScript. GhostScript reports "Unknown operator: Song". The pdf file includes "/BaseFont /FEVAQU+MS Song". Evidently, the problem is the space in "MS Song", because if I use a hex editor to replace the space with an underscore, then the pdf becomes OK. The same font worked fine with earlier pdftex versions. It's a Chinese Unicode TrueType font, from Microsoft. I haven't tried installing pdftex 1.30.6; is it possible that would fix the problem? I just re-installed TeX using i-Installer for Mac OS X; it still uses pdftex 1.30.4. Here is the output of pdftex when running the test file: This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5) entering extended mode (./test3.tex [1{/Users/tbishop/Library/texmf/fonts/map/pdftex/ updmap/pdftex.map }] )</usr/local/teTeX/share/texmf.tetex/fonts/type1/bluesky/cm/ cmr10.pfb>{/usr/ local/teTeX/share/texmf.local/fonts/enc/pdftex/enc/mssong4e.enc} </usr/local/teT eX/share/texmf.local/fonts/truetype/mssong.ttf> Output written on test3.pdf (1 page, 5067 bytes). Transcript written on test3.log. Thanks in advance for any help! Best wishes, Tom Bishop (wenlin(a)wenlin.com) ---------------------------------------------------------------------- >Comment By: Hans Hagen (hagen) Date: 2006-04-13 21:58 Message: Logged In: YES user_id=927 why not replace spaces by underscore (just as a precaution) ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 21:25 Message: Logged In: YES user_id=929 patch makes pdftex lenient with (buggy) TTF fonts that have spaces in PostScript name, strips spaces in /BaseFont and /FontName, e. g.: "MS Song" ---> "MSSong" ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 20:54 Message: Logged In: YES user_id=929 ah, after the PDF reference 5. ed. page 388 in case there would be no PostScript name entry we could be cruesome and strip the blank. But there is a wrong PostScript name in the font. So maybe one could flag a warning (or not?) and just strip the blank? (which would be easy) Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 20:39 Message: Logged In: YES user_id=929 This mssong.ttf version seems to be buggy. Here is a diagnostic printout from function ttf_read_name() in writettf.c; these are all available entries from the "Naming Table": i=0 platform_id=1 encoding_id=0 name_id=0 name <(c) Copyright ZHUHAI Stone Computerized typesetting system R&D LTD., 1995-1996> i=1 platform_id=1 encoding_id=0 name_id=1 name <MS Song> i=2 platform_id=1 encoding_id=0 name_id=2 name <Regular> i=3 platform_id=1 encoding_id=0 name_id=3 name <Microsoft:MS Song:1996> i=4 platform_id=1 encoding_id=0 name_id=4 name <MS Song> i=5 platform_id=1 encoding_id=0 name_id=5 name <Version 1.00> i=6 platform_id=1 encoding_id=0 name_id=6 name <MS Song> ---> ttf_read_name <MS Song> There is no usable PostScript name in: The TTF standard tells that under name_id=6 there should be the Postscript font, but here it is "MS Song" with a blank. As long as the font does not contain a valid PostScript name, i have no idea how to tweak this correctly... Other clues anybody? Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106

1 0

[ pdftex-Bugs-509 ] invalid pdf created if font name contains space
by noreply＠sarovar.org 14 Apr '06

14 Apr '06

Bugs item #509, was opened at 2006-04-13 20:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106 Category: Fonts >Group: v1.40.0 Status: Open Resolution: None >Priority: 3 Submitted By: Tom Bishop (tbishop) Assigned to: Hartmut Henkel (hhenkel) Summary: invalid pdf created if font name contains space Initial Comment: pdftex 3.141592-1.30.4-2.2 runs the following code without complaining: \pdfmapline{+mssong4e <mssong.ttf <mssong4e.enc} \font\testfont=mssong4e at 20pt \testfont\char"00 \bye -- but the resulting pdf file can't be opened by Adobe Reader or GhostScript. GhostScript reports "Unknown operator: Song". The pdf file includes "/BaseFont /FEVAQU+MS Song". Evidently, the problem is the space in "MS Song", because if I use a hex editor to replace the space with an underscore, then the pdf becomes OK. The same font worked fine with earlier pdftex versions. It's a Chinese Unicode TrueType font, from Microsoft. I haven't tried installing pdftex 1.30.6; is it possible that would fix the problem? I just re-installed TeX using i-Installer for Mac OS X; it still uses pdftex 1.30.4. Here is the output of pdftex when running the test file: This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5) entering extended mode (./test3.tex [1{/Users/tbishop/Library/texmf/fonts/map/pdftex/ updmap/pdftex.map }] )</usr/local/teTeX/share/texmf.tetex/fonts/type1/bluesky/cm/ cmr10.pfb>{/usr/ local/teTeX/share/texmf.local/fonts/enc/pdftex/enc/mssong4e.enc} </usr/local/teT eX/share/texmf.local/fonts/truetype/mssong.ttf> Output written on test3.pdf (1 page, 5067 bytes). Transcript written on test3.log. Thanks in advance for any help! Best wishes, Tom Bishop (wenlin(a)wenlin.com) ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 23:25 Message: Logged In: YES user_id=929 patch makes pdftex lenient with (buggy) TTF fonts that have spaces in PostScript name, strips spaces in /BaseFont and /FontName, e. g.: "MS Song" ---> "MSSong" ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 22:54 Message: Logged In: YES user_id=929 ah, after the PDF reference 5. ed. page 388 in case there would be no PostScript name entry we could be cruesome and strip the blank. But there is a wrong PostScript name in the font. So maybe one could flag a warning (or not?) and just strip the blank? (which would be easy) Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 22:39 Message: Logged In: YES user_id=929 This mssong.ttf version seems to be buggy. Here is a diagnostic printout from function ttf_read_name() in writettf.c; these are all available entries from the "Naming Table": i=0 platform_id=1 encoding_id=0 name_id=0 name <(c) Copyright ZHUHAI Stone Computerized typesetting system R&D LTD., 1995-1996> i=1 platform_id=1 encoding_id=0 name_id=1 name <MS Song> i=2 platform_id=1 encoding_id=0 name_id=2 name <Regular> i=3 platform_id=1 encoding_id=0 name_id=3 name <Microsoft:MS Song:1996> i=4 platform_id=1 encoding_id=0 name_id=4 name <MS Song> i=5 platform_id=1 encoding_id=0 name_id=5 name <Version 1.00> i=6 platform_id=1 encoding_id=0 name_id=6 name <MS Song> ---> ttf_read_name <MS Song> There is no usable PostScript name in: The TTF standard tells that under name_id=6 there should be the Postscript font, but here it is "MS Song" with a blank. As long as the font does not contain a valid PostScript name, i have no idea how to tweak this correctly... Other clues anybody? Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106

1 0

[ pdftex-Bugs-509 ] invalid pdf created if font name contains space
by noreply＠sarovar.org 14 Apr '06

14 Apr '06

Bugs item #509, was opened at 2006-04-13 20:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106 Category: Fonts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tom Bishop (tbishop) Assigned to: Hartmut Henkel (hhenkel) Summary: invalid pdf created if font name contains space Initial Comment: pdftex 3.141592-1.30.4-2.2 runs the following code without complaining: \pdfmapline{+mssong4e <mssong.ttf <mssong4e.enc} \font\testfont=mssong4e at 20pt \testfont\char"00 \bye -- but the resulting pdf file can't be opened by Adobe Reader or GhostScript. GhostScript reports "Unknown operator: Song". The pdf file includes "/BaseFont /FEVAQU+MS Song". Evidently, the problem is the space in "MS Song", because if I use a hex editor to replace the space with an underscore, then the pdf becomes OK. The same font worked fine with earlier pdftex versions. It's a Chinese Unicode TrueType font, from Microsoft. I haven't tried installing pdftex 1.30.6; is it possible that would fix the problem? I just re-installed TeX using i-Installer for Mac OS X; it still uses pdftex 1.30.4. Here is the output of pdftex when running the test file: This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5) entering extended mode (./test3.tex [1{/Users/tbishop/Library/texmf/fonts/map/pdftex/ updmap/pdftex.map }] )</usr/local/teTeX/share/texmf.tetex/fonts/type1/bluesky/cm/ cmr10.pfb>{/usr/ local/teTeX/share/texmf.local/fonts/enc/pdftex/enc/mssong4e.enc} </usr/local/teT eX/share/texmf.local/fonts/truetype/mssong.ttf> Output written on test3.pdf (1 page, 5067 bytes). Transcript written on test3.log. Thanks in advance for any help! Best wishes, Tom Bishop (wenlin(a)wenlin.com) ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 22:54 Message: Logged In: YES user_id=929 ah, after the PDF reference 5. ed. page 388 in case there would be no PostScript name entry we could be cruesome and strip the blank. But there is a wrong PostScript name in the font. So maybe one could flag a warning (or not?) and just strip the blank? (which would be easy) Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 22:39 Message: Logged In: YES user_id=929 This mssong.ttf version seems to be buggy. Here is a diagnostic printout from function ttf_read_name() in writettf.c; these are all available entries from the "Naming Table": i=0 platform_id=1 encoding_id=0 name_id=0 name <(c) Copyright ZHUHAI Stone Computerized typesetting system R&D LTD., 1995-1996> i=1 platform_id=1 encoding_id=0 name_id=1 name <MS Song> i=2 platform_id=1 encoding_id=0 name_id=2 name <Regular> i=3 platform_id=1 encoding_id=0 name_id=3 name <Microsoft:MS Song:1996> i=4 platform_id=1 encoding_id=0 name_id=4 name <MS Song> i=5 platform_id=1 encoding_id=0 name_id=5 name <Version 1.00> i=6 platform_id=1 encoding_id=0 name_id=6 name <MS Song> ---> ttf_read_name <MS Song> There is no usable PostScript name in: The TTF standard tells that under name_id=6 there should be the Postscript font, but here it is "MS Song" with a blank. As long as the font does not contain a valid PostScript name, i have no idea how to tweak this correctly... Other clues anybody? Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106

1 0

[ pdftex-Bugs-509 ] invalid pdf created if font name contains space
by noreply＠sarovar.org 14 Apr '06

14 Apr '06

Bugs item #509, was opened at 2006-04-13 20:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106 Category: Fonts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tom Bishop (tbishop) Assigned to: Hartmut Henkel (hhenkel) Summary: invalid pdf created if font name contains space Initial Comment: pdftex 3.141592-1.30.4-2.2 runs the following code without complaining: \pdfmapline{+mssong4e <mssong.ttf <mssong4e.enc} \font\testfont=mssong4e at 20pt \testfont\char"00 \bye -- but the resulting pdf file can't be opened by Adobe Reader or GhostScript. GhostScript reports "Unknown operator: Song". The pdf file includes "/BaseFont /FEVAQU+MS Song". Evidently, the problem is the space in "MS Song", because if I use a hex editor to replace the space with an underscore, then the pdf becomes OK. The same font worked fine with earlier pdftex versions. It's a Chinese Unicode TrueType font, from Microsoft. I haven't tried installing pdftex 1.30.6; is it possible that would fix the problem? I just re-installed TeX using i-Installer for Mac OS X; it still uses pdftex 1.30.4. Here is the output of pdftex when running the test file: This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5) entering extended mode (./test3.tex [1{/Users/tbishop/Library/texmf/fonts/map/pdftex/ updmap/pdftex.map }] )</usr/local/teTeX/share/texmf.tetex/fonts/type1/bluesky/cm/ cmr10.pfb>{/usr/ local/teTeX/share/texmf.local/fonts/enc/pdftex/enc/mssong4e.enc} </usr/local/teT eX/share/texmf.local/fonts/truetype/mssong.ttf> Output written on test3.pdf (1 page, 5067 bytes). Transcript written on test3.log. Thanks in advance for any help! Best wishes, Tom Bishop (wenlin(a)wenlin.com) ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-13 22:39 Message: Logged In: YES user_id=929 This mssong.ttf version seems to be buggy. Here is a diagnostic printout from function ttf_read_name() in writettf.c; these are all available entries from the "Naming Table": i=0 platform_id=1 encoding_id=0 name_id=0 name <(c) Copyright ZHUHAI Stone Computerized typesetting system R&D LTD., 1995-1996> i=1 platform_id=1 encoding_id=0 name_id=1 name <MS Song> i=2 platform_id=1 encoding_id=0 name_id=2 name <Regular> i=3 platform_id=1 encoding_id=0 name_id=3 name <Microsoft:MS Song:1996> i=4 platform_id=1 encoding_id=0 name_id=4 name <MS Song> i=5 platform_id=1 encoding_id=0 name_id=5 name <Version 1.00> i=6 platform_id=1 encoding_id=0 name_id=6 name <MS Song> ---> ttf_read_name <MS Song> There is no usable PostScript name in: The TTF standard tells that under name_id=6 there should be the Postscript font, but here it is "MS Song" with a blank. As long as the font does not contain a valid PostScript name, i have no idea how to tweak this correctly... Other clues anybody? Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106

1 0

[ pdftex-Bugs-509 ] invalid pdf created if font name contains space
by noreply＠sarovar.org 13 Apr '06

13 Apr '06

Bugs item #509, was opened at 2006-04-13 11:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106 Category: Fonts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tom Bishop (tbishop) Assigned to: Hartmut Henkel (hhenkel) Summary: invalid pdf created if font name contains space Initial Comment: pdftex 3.141592-1.30.4-2.2 runs the following code without complaining: \pdfmapline{+mssong4e <mssong.ttf <mssong4e.enc} \font\testfont=mssong4e at 20pt \testfont\char"00 \bye -- but the resulting pdf file can't be opened by Adobe Reader or GhostScript. GhostScript reports "Unknown operator: Song". The pdf file includes "/BaseFont /FEVAQU+MS Song". Evidently, the problem is the space in "MS Song", because if I use a hex editor to replace the space with an underscore, then the pdf becomes OK. The same font worked fine with earlier pdftex versions. It's a Chinese Unicode TrueType font, from Microsoft. I haven't tried installing pdftex 1.30.6; is it possible that would fix the problem? I just re-installed TeX using i-Installer for Mac OS X; it still uses pdftex 1.30.4. Here is the output of pdftex when running the test file: This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5) entering extended mode (./test3.tex [1{/Users/tbishop/Library/texmf/fonts/map/pdftex/ updmap/pdftex.map }] )</usr/local/teTeX/share/texmf.tetex/fonts/type1/bluesky/cm/ cmr10.pfb>{/usr/ local/teTeX/share/texmf.local/fonts/enc/pdftex/enc/mssong4e.enc} </usr/local/teT eX/share/texmf.local/fonts/truetype/mssong.ttf> Output written on test3.pdf (1 page, 5067 bytes). Transcript written on test3.log. Thanks in advance for any help! Best wishes, Tom Bishop (wenlin(a)wenlin.com) ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=509&group_id=106

1 0

[ pdftex-Bugs-505 ] file with only \immediate\pdfobj stream results in garbage
by noreply＠sarovar.org 08 Apr '06

08 Apr '06

Bugs item #505, was opened at 2006-04-06 00:50 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=505&group_id=106 Category: None >Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: Hartmut Henkel (hhenkel) Summary: file with only \immediate\pdfobj stream results in garbage Initial Comment: The input \pdfcompresslevel=0 \immediate\pdfobj stream {xx} \end results in the message No pages of output. but produces the garbage pdf attached. Confirmed with 1.30.2 and the last 1.40.0-beta. ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-04-08 08:45 Message: Logged In: YES user_id=929 tried 2 approaches: 1) try to make a complete PDF file without pages, like: << /Type /Pages /Count 0 /Kids [] >> Then xpdf shows a white background, but acroread complains. So this can't be done. 2a) silently delete faulty PDF. But one should give at least a warning. 2b) flag warning and delete faulty PDF. That's the current patch for 1.40.0-beta-20060213. Now it says: This is pdfTeXk, Version 3.141592-1.40.0-beta-20060213 (Web2C 7.5.5) (format=pdftex 2006.4.8) 8 APR 2006 07:41 %&-line parsing enabled. **test1 (./test1.tex ) No pages of output. Warning: pdftex: dangling objects discarded, no output file produced. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=505&group_id=106

1 0