- ntg-pdftex - NTG Mailing Lists

[NTG-context] luatex crash around page 1000
by Akira Kakuto 12 Apr '19

12 Apr '19

> The event manager says, that it is a stack exhaustion (0xc00000fd, > STATUS_STACK_OVERFLOW). Many thanks. I'll increase size of stack. Best, Akira

1 0

Incomplete CharSet causes failure with PDF/A validation
by Ross Moore 29 Jan '19

29 Jan '19

Hi all. I believe there is a problem with the way pdfTeX constructs the CharSet for a subsetted font. Not all fonts are affected, and it only shows up when attempting to validate for PDF/A. I’ve mentioned the problem to Thanh and others, but as there’s been nothing done, I’ll bring it up here, with an example that cannot be worked-around. Attached are two PDF/A documents, using Hebrew text. The main font is the “David” style font from the culmus package: DavidCLM-Medium hebart-david.pdf — produced by pdfTeX hebart-gs.pdf — produced using dvips+GS hebart-david fails PDF/A validation in one aspect only (see image): “CharSet in subset font is incomplete (font contains glyphs that are not listed)"

8 43

Re: [NTG-pdftex] Incomplete CharSet causes failure with PDF/A validation
by Karl Berry 28 Jan '19

28 Jan '19

Ok, now: \pdfomitcharset=0 (default) -> /CharSet included \pdfomitcharset=1 -> /CharSet omitted I warn in the pdftex documentation not to rely on other values, in case we end up ever implementing anything fancier we need a switch for. Just now committed to pdftex and TL repos. Hope it works out this time. -k

1 0

Re: [NTG-pdftex] small problems with newtx fonts
by Ross Moore 04 Oct '18

04 Oct '18

Hi all. I’ve encountered a problem whereby pdfTeX generates different subsets of the same font, containing exactly the same subsetted name. On 1 Oct 2018, at 8:36 am, Karl Berry <karl(a)freefriends.org<mailto:karl@freefriends.org>> wrote: Hi Ross, If you feel like posting the issue to the ntg-pdftex list, or coming up with a patch yourself, so much the better. A simpler test using plain TeX that just typesets two characters in two different fonts and creates the problems would be helpful, too. This coding exhibits the problem. %%% test-duplicate-fonts.tex %%% \font\fonti=fxlri-7alt \font\fontii=fxlri-7letters \font\fontiii=fxlri-7letters at 11pt {\fonti \char"03} {\fontii A B C} {\fontiii A D E} \bye %%%%% end of test-duplicate-fonts.tex %%% Using pdf fonts to see the names of embedded fonts, one gets: name type emb sub uni prob object ID ------------------------------------ ----------------- --- --- --- ---- --------- SAMSAA+LinLibertineI7 Type 1 yes yes yes 4 0 SAMSAA+LinLibertineI7 Type 1 yes yes yes 5 0 SDXKYB+CMR10 Type 1 yes yes yes 6 0 Where the 1st two entries are seen to be identical. Running Preflight checks, this duplication results in error reports as in the image. (BTW, I was using a different filename to the above coding.) [cid:286A2034-C351-4AE2-81BE-6DDBDAE8AB41@telstra.com.au] I think the issue is related to having 2 different fonts (here fxlri-7alt and fxlri-7letters from the newtx fonts ) using characters from the same base font (here LinLibertineI7 ). But this is not an error in itself. The issue must lie with how the subsetting prefix ‘SAMSAA’ is generated. Surely if the same prefix has already been used with an instance of the same font, then the next instance should increment it (e.g., to SAMSAB or SAMSAC or …., say) until a unique name is achieved. It is important to get this fixed, else many otherwise perfectly fine documents will fail Preflight validation checks, for modern PDF standards. All the best, Ross Dr Ross Moore Mathematics Dept | 12 Wally’s Walk, 734 Macquarie University, NSW 2109, Australia T: +61 2 9850 8955 | F: +61 2 9850 8114<tel:%2B61%202%209850%209695> M:+61 407 288 255<tel:%2B61%20409%20125%20670> | E: ross.moore(a)mq.edu.au<mailto:rick.minter@mq.edu.au> http://www.maths.mq.edu.au<http://mq.edu.au/> [cid:image001.png@01D030BE.D37A46F0]<http://mq.edu.au/> CRICOS Provider Number 00002J. Think before you print. Please consider the environment before printing this email.<http://mq.edu.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of Macquarie University.<http://mq.edu.au/>

2 3

\expanded
by Joseph Wright 17 May '18

17 May '18

Hello all, As recently raised on the TeX Live mailing list, the LaTeX team feel that the \expanded primitive, suggested for pdfTeX 1.50 around 10 years ago, would be a useful addition to TeX engines. (It is present in LuaTeX.) Attached is a patch which provides the primitive itself (based on the LuaTeX version), an entry for the pdfTeX manual, and some tests. (This is based on the version in https://github.com/josephwright/texlive-source/tree/expanded, slightly adjusted as the tests there also cover other primitives to support XeTeX additions.) I have chosen the pdfTeX manual as the 'home' for documenting behaviour as the idea comes from pdfTeX and as this is usually where 'utility' primitives have been documented. A similar request has been made for XeTeX (for the code part), whilst the (u)pTeX developers already have a Git branch which would add this functionality. We (the team) do hope that general agreement can be reached to make this available in the main engines (pdfTeX, XeTeX, LuaTeX, e-pTeX, e-upTeX) for TL'19. Regards, Joseph

4 17

\\pdftexrevision is incorrectly defined
by Pali Rohár 25 Mar '18

25 Mar '18

Hi! In current pdftex.web file in stable branch is following code: http://tug.org/svn/pdftex/branches/stable/source/src/texk/web2c/pdftexdir/p… @d pdftex_version==140 { \.{\\pdftexversion} } @d pdftex_revision=="18" { \.{\\pdftexrevision} } @d pdftex_version_string=='-1.40.19' {current \pdfTeX\ version} Therefore banner is set to version 1.40.19, but \pdftexrevision just to version 18. This looks like an error. -- Pali Rohár pali.rohar(a)gmail.com

2 2

Re: [NTG-pdftex] [tex-k] e-TeX \lastnodetype initialization problem
by Akira Kakuto 24 Mar '18

24 Mar '18

Hi Hironobu, > A patch for > * etexdir/tex.ech > * pdftexdir/pdftex.ch > * xetexdir/xetex.ch > is attached. Many thanks. Applied in r47096. Best, Akira

1 0

Re: [NTG-pdftex] \pdffontobjnum assertion failed
by Hironobu Yamashita 26 Jan '18

26 Jan '18

Looking more deeply, I found that LuaTeX also causes Assertion failed: (fo->last_char>=fo->first_char), function create_fontdictionary, file ../../../texk/web2c/luatexdir/font/writefont.w, line 683. Abort trap: 6 when if (!font_has_subset(f)) return; inside do_pdf_font() is removed. Therefore, it seems that the pdfTeX issue can be avoided by applying the attached patch. Hironobu Yamashita

4 6

\pdffontobjnum assertion failed
by Karl Berry 24 Jan '18

24 Jan '18

In case anyone here has a chance to look ... Date: Tue, 23 Jan 2018 15:52:19 +0100 From: Enrico Gregorio <Enrico.Gregorio(a)univr.it> To: TeXLive <tex-live(a)tug.org> Subject: [tex-live] Bug in pdftex. Suggestions on who to report? The following example, compiled with pdftex, \edef\tenitnumber{\pdffontobjnum\tenit} \message{The font number is \tenitnumber} \tenitnumber \bye fails with This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdftex) restricted \write18 enabled. entering extended mode (./alfon.tex{/usr/local/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdftex.m ap} The font number is 1 [1]Assertion failed: (fo->last_char >= fo->first_char), function create_fontdictionary, file ../../../texk/web2c/pdftexdir/writefont.c, line 607. )Abort trap: 6 The similar \edef\first{\pdffeedback fontobjnum\tenit} \first \bye doesnât fail on LuaTeX. Tested both on Mac OS X and Windows (Joseph Wright tested it). [...]

3 11

Re: [NTG-pdftex] \pdffontobjnum assertion failed
by Akira Kakuto 24 Jan '18

24 Jan '18

> I tired to gather similar lines: Sorry, I tried ... Best, Akira

1 0