August 2008 - ntg-pdftex - NTG Mailing Lists

pdftex-1.40.9 release
by Thanh Han The 16 Aug '08

16 Aug '08

Hi, a new stable release is available at http://sarovar.org/frs/download.php/1240/pdftex-1.40.9.tar.bz2 -------------------------------------------------- pdfTeX 3.1415926-1.40.9 was released on 2008-08-16 -------------------------------------------------- - bugfixes: - pdf inclusion (inconsistent use of -DDISABLE_OUTLINE) - bug #2068 (cross-platform format dumping/undumping) - bug #2082 (font_dim[FONTNAME_CODE] not initialized) - bug #2083 (unchecked assignment) Thanh

1 0

Fwd: [png-mng-implement] libpng-1.0.38 and libpng-1.2.30 available
by Martin Schröder 15 Aug '08

15 Aug '08

---------- Forwarded message ---------- From: Glenn Randers-Pehrson <glennrp(a)gmail.com> Date: 2008/8/15 Subject: [png-mng-implement] libpng-1.0.38 and libpng-1.2.30 available To: PNG/MNG implementation discussion list <png-mng-implement(a)lists.sourceforge.net> libpng-1.0.38 and libpng-1.2.30 are available from ftp://ftp.simpleystems.org/pub/png/src/ and from http://libpng.sf.net There are many cosmetic changes from 1.2.29, and a potential DoS due to memory leaking on read error is fixed. Reding and writing of chunk length and chunk type are combined into a single i/o operation. Glenn ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ png-mng-implement mailing list png-mng-implement(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/png-mng-implement

1 0

[pdftex-Bugs][2083] problem with copyStream() (file pdftoepdf.cc)
by pdftex-bugs＠sarovar.org 12 Aug '08

12 Aug '08

Bugs item #2083, was opened at 2008-08-12 15:50 Status: Open Priority: 3 Submitted By: The Thanh Han (hanthethanh) Assigned to: The Thanh Han (hanthethanh) Summary: problem with copyStream() (file pdftoepdf.cc) Resolution: Accepted Group: None Category: PDF inclusion Initial Comment: the assignment pdflastbyte = pdfbuf[pdfptr - 1]; in copyStream() (file pdftoepdf.cc) may cause segfault, since there is no checking if pdfptr is > 0. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2083&group_id=106

1 0

[pdftex-Bugs][2082] font_dim[FONTNAME_CODE] not initialized (writefont.c)
by pdftex-bugs＠sarovar.org 12 Aug '08

12 Aug '08

Bugs item #2082, was opened at 2008-08-12 15:45 Status: Open Priority: 3 Submitted By: The Thanh Han (hanthethanh) Assigned to: The Thanh Han (hanthethanh) Summary: font_dim[FONTNAME_CODE] not initialized (writefont.c) Resolution: Accepted Group: None Category: Fonts Initial Comment: I found an issue with writefont.c: when a new en_entry is created, the value of font_dim[FONTNAME_CODE] is not initialized. For T1 fonts this is not a problem since all T1 fonts have fontname, but for TT fonts some weird fonts might not have [I ran into this problem during a test on some large TT fonts with valgrind] Here is the suggested patch: Index: source/src/texk/web2c/pdftexdir/writefont.c =================================================================== --- source/src/texk/web2c/pdftexdir/writefont.c (revision 508) +++ source/src/texk/web2c/pdftexdir/writefont.c (revision 509) @@ -81,7 +81,7 @@ fd->fn_objnum = 0; fd->all_glyphs = false; fd->write_ttf_glyph_names = false; - for (i = 0; i < INT_KEYS_NUM; i++) { + for (i = 0; i < FONT_KEYS_NUM; i++) { fd->font_dim[i].val = 0; fd->font_dim[i].set = false; } ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2082&group_id=106

1 0

Re: [NTG-pdftex] Question related to .ttc support
by Thanh Han The 10 Aug '08

10 Aug '08

On Sat, Aug 09, 2008 at 05:03:29PM +0100, Philip TAYLOR wrote: > >how about this: rename (or symlink) the ttc font to ttf, and > >document this trick in the manual. The way it works is more > >or less the same, but we don't have to change anything in > >the sources. > > I can see that renaming would work, but that > would prevent the .ttc font from working > in other applications that require and expect > a .ttc, but wouldn't symbolic linking cause > a problem in that it would then find /two/ > fonts, one .ttc and one .ttf, the former of > which it would treat as type-1 and the latter > as truetype ?! pdftex would look only for what is specified in map files. But I do also agree that this causes more confusion than simply applying the patch. Regards, Thanh

1 0

Re: [NTG-pdftex] Question related to .ttc support
by Thanh Han The 10 Aug '08

10 Aug '08

it looks like applying the patch and document it well would be simpler than any other hacks. Thanks for all comments. Regards, Thanh On Sun, Aug 10, 2008 at 09:22:34AM +0800, hzluo wrote: > Friends, > I forgot to mention some properties related to .ttc files. > For many .ttc files of CJK, all fonts in one .ttc file have > identical CJK glyphs. Only the latin glyphs are different. > But for latex systems, we use these fonts to typeset > CJK glyphs only. We have much better latin fonts > to typeset latin glyphs. As a result, supporting the > first font in .ttc file is good enough for most such > applications. > In addition, Windows does not support symbolic linking. > Only latest Windows versions support hardlink via junction, > but it can't work on early versions. > Certainly, supporting only the first font of .ttc file > is not equal to supporting .ttc file. Better way is to > add parameters to select fonts in .ttc file. But it needs > significant work. I do not know how to achieve this. > So, I think we can apply this patch, and claim in manual > that we support "the first font of .ttc file". Maybe someone > will work on a patch for full .ttc support later on, if s/he > is troubled by the problem. (If no one is troubled, > then no need to patch it, right? > - that's one of the spirit of opensource :) > > The aboves are only my two cents. > > Regards, > Hangzai > > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

1 0

Re: [NTG-pdftex] Question related to .ttc support
by Thanh Han The 10 Aug '08

10 Aug '08

On Sat, Aug 09, 2008 at 02:53:07PM +0200, Taco Hoekwater wrote: > Thanh Han The wrote: > > > >Your patch changes pdftex so that it will treat TTC like > >truetype font. While it works for your case, I am not > >confident that it's the right way to do that. Someone with a > >thorough understanding of TTC format can comment on this? > > IIRC, the patch will give access to the *first* font in the > collection, because that has an offset of zero (which makes > the first font in the ttc behave the same as a standalone ttf > font, when the ttc header is ignored). > > You could apply the patch but not document support for ttc > files (because the really patch doesn't implement that). This > gives a small subset of ttc functionality, but still better > than mishandling the format completely. how about this: rename (or symlink) the ttc font to ttf, and document this trick in the manual. The way it works is more or less the same, but we don't have to change anything in the sources. Thanh

3 2

Re: [NTG-pdftex] Question related to .ttc support
by Thanh Han The 09 Aug '08

09 Aug '08

On Fri, Aug 08, 2008 at 07:07:37PM +0800, hzluo wrote: > Friends, > I recently tested pdflatex with a Chinese font simsun.ttc, > pdflatex report the following error: > > !pdfTeX error: pdflatex (file simsun.ttc): cannot open Type 1 font file for > reading > > I checked the source code of pdflatex, found that pdflatex > only takes .ttf files as the truetype fonts, there is no test > for .ttc suffix. So, simsun.ttc is assumed to be a Type 1 font. > Apparently it is wrong. the manual says that if a fontfile has unknown extension, it will be treated as type1. Not quite right, but that's the expected bahaviour of pdftex in this case. > Is there any special reason to give up the .ttc support > in pdflatex? I found that dvipdfmx supports simsun.ttc smoothly, > so pdflatex should also do that, and it is quite simple. > I have attached a tiny patch to fix this. Could anyone confirm it? TTC is not truetype, but truetype collection. It's not supported by pdftex yet, since I don't know enough about this format yet and there seems to be very little interest in this format. Your patch changes pdftex so that it will treat TTC like truetype font. While it works for your case, I am not confident that it's the right way to do that. Someone with a thorough understanding of TTC format can comment on this? Regards, Thanh

2 1

Question related to .ttc support
by hzluo 08 Aug '08

08 Aug '08

Friends, I recently tested pdflatex with a Chinese font simsun.ttc, pdflatex report the following error: !pdfTeX error: pdflatex (file simsun.ttc): cannot open Type 1 font file for reading I checked the source code of pdflatex, found that pdflatex only takes .ttf files as the truetype fonts, there is no test for .ttc suffix. So, simsun.ttc is assumed to be a Type 1 font. Apparently it is wrong. Is there any special reason to give up the .ttc support in pdflatex? I found that dvipdfmx supports simsun.ttc smoothly, so pdflatex should also do that, and it is quite simple. I have attached a tiny patch to fix this. Could anyone confirm it? Regards, Hangzai

1 0

Including many files
by Martin Schröder 04 Aug '08

04 Aug '08

A follow-up to #2077: ------------------ File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> [7683] <./input/tuftecmr10-7684.pdf> <./input/tuftecmr10-7684.pdf> !pdfTeX error: pdflatex (file ./input/t): cannot find image file ==> Fatal error occurred, no output PDF file produced! ------------------ Looks like a silent buffer overflow somewhere. ./input/tuftecmr10-7684.pdf exists. Best Martin

1 0