- ntg-pdftex - NTG Mailing Lists

Time for Type3 bitmap fonts to cause a warning?
by Markus Kuhn 29 Mar '17

29 Mar '17

Type3 bitmap fonts look much worse on most output devices than properly-hinted Type1 fonts. Type3 fonts also can cause problems with PDF interpreters in printers, which sometimes no longer implement all aspects of the Type3 language correctly. Type3 fonts were once a hack that seems no longer widely used outside the TeX community, and therefore are now less well tested and supported by device manufacturers. Type3 bitmap fonts seem an anachronism from the 1980s, when it was customary to output DVI files using Metafont-generated device-specific bitmaps, and when there were only a small number of standard output resolutions in use. Today, I find that in nearly all cases where I encounter pdftex-generated documents with Type3 bitmap fonts, these were actually selected by an inexperienced author by accident, (often as a result of copying a line such as \usepackage[T1]{fontenc} without understanding its font-selection implications). Suggestion: it would be useful to actively discourage in pdftex the use of Type3 fonts. This could be done in steps, e.g.: - initially just output a warning that prominently lists any Type3 fonts used in the PDF produced (plus add an "I know what I do and really want Type3" command-line override option to suppress that warning) - later turn that warning into an error, such that Type3 fonts can now only be included into PDFs using the "I know what I do and really want Type3" command-line option, to make sure they only appear in PDFs as a deliberate choice by an experienced author. [The idea is similar to how HTTPS browsers like Chrome or Firefox gradually added warnings to phase out outdated cryptography.] If Type3 fonts generated a clear warning, this would make it much easier for the authors of document-submission guidelines to tell PDF authors what they need to avoid. At the moment, such guidelines have to rely on more complex instructions to check font types with e.g. pdffonts file.pdf | grep 'Type 3' Markus -- Markus Kuhn, Computer Laboratory, University of Cambridge http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain

3 2

[PATCH v3] pdftex - Add support for encfile and \pdfgentounicode for PK fonts
by Pali Rohár 28 Mar '17

28 Mar '17

... continued thread "[pdftex] pdftex - Encoding for metafont PK fonts" This patch allows to specify encoding file also for bitmap PK fonts (generated by MetaFont) and add support for \pdfgentounicode primitive for these fonts. Example for csb12 (CSFonts, Latin 2 encoding): \nopagenumbers \pdfmapline{+csb12 <csr.enc} \pdfglyphtounicode{ccaron}{010D} \pdfgentounicode=1 \font\csb=csb12 \csb \char232 \bye Char 232 (0xE8) in font csb12 is 'č' (LATIN SMALL LETTER C WITH CARON) and glyph name for 'č' is /ccaron. Unicode character is 0+010D. Note that U+OOE8 (decimal 232) is 'è' (LATIN SMALL LETTER E WITH GRAVE) which is reason why encoding file (csr.enc) is needed. Unicode is extension of Latin 1 (character positions 127-255 are same) so this is reason why Latin 1 PK fonts works fine without encoding files... In V3 version of patch I added check for duplicate glyph names to prevent generating incorrect PDF files. Duplicates of glyph names are not used and default glyph name used by pdftex "\a<number>" is used as before. And I added small extension to pdftex-t.tex documentation as Karl Berry wanted. -- Pali Rohár pali.rohar(a)gmail.com

6 28

svn repo for pdftex now on tug.org
by Karl Berry 13 Mar '17

13 Mar '17

Hi - for the record, the subversion source repository for pdftex has been moved to tug.org, since foundry.supelec.fr is shutting down later this year. The repository was not changed, just moved, so the active work is still taking place under /branches/stable, not /trunk: E.g., svn list svn://tug.org/pdftex/branches/stable (note, the protocol is svn:// rather than http:// or anything else). Can be browsed on the web at http://tug.org/svn/pdftex/branches/stable. I minimally updated the web page (http://pdftex.org) Please continue to use the pdftex mailing list for general discussion and the ntg-pdftex mailing list for development issues. Best, Karl

1 0

Reporting bug? Need help
by Roberto Iacono 30 Aug '16

30 Aug '16

Hi, I get the following message when trying to compile a pdf with my pacthed swp 5.5: pdfTeX error: pdflatex.exe (file cmsy5.ttf) What should I do? Thanks. ************************** Roberto Iacono Associate Professor in Economics and Social Policy Norwegian University of Science and Technology (NTNU) NO-7491, Trondheim, Norway Mobile: +47-90946148 Web: ntnu.edu/employees/roberto.iacono<http://ntnu.edu/employees/roberto.iacono> **************************

1 0

pdftex - Duplicated codes ligatures in glyphtounicode.tex
by Pali Rohár 27 Jun '16

27 Jun '16

Hello, I found another problem in glyphtounicode.tex file. There are duplicate codes for ligatures, see: \pdfglyphtounicode{ff}{FB00} \pdfglyphtounicode{ffi}{FB03} \pdfglyphtounicode{ffl}{FB04} \pdfglyphtounicode{fi}{FB01} ... \pdfglyphtounicode{fl}{FB02} ... \pdfglyphtounicode{IJ}{0132} ... \pdfglyphtounicode{ij}{0133} ... ... \pdfglyphtounicode{ff}{0066 0066} \pdfglyphtounicode{fi}{0066 0069} \pdfglyphtounicode{fl}{0066 006C} \pdfglyphtounicode{ffi}{0066 0066 0069} \pdfglyphtounicode{ffl}{0066 0066 006C} \pdfglyphtounicode{IJ}{0049 004A} \pdfglyphtounicode{ij}{0069 006A} Currently pdftex use last defined value, so first definitions are useless. Can you fix it that file, so there will be only one active definitions? I see that on other places duplicate values are just commented... And why is used decomposited sequence of ascii for those ligatures instead using unicode character for each ligature? -- Pali Rohár pali.rohar(a)gmail.com

4 6

pdftex - Incorrect unicode value for dotlessj
by Pali Rohár 13 Jun '16

13 Jun '16

Hello, in file texmf/tex/generic/pdftex/glyphtounicode.tex is defined wrong unicode value for dotlessj glyph. Currently it is specified as \pdfglyphtounicode{dotlessj}{F6BE}, see: https://foundry.supelec.fr/scm/viewvc.php/trunk/source/texmf/tex/generic/pd… According to unicode standard (since 4.1.0 March 2005) dotlessj glyph has code 0237, see: http://unicode.org/charts/PDF/U0180.pdf Can you fix this code for dotlessj glyph? -- Pali Rohár pali.rohar(a)gmail.com

2 4

Validation problem with PDF files produced by pdftex
by Fabrice Popineau 09 Jun '16

09 Jun '16

Hi folks, There is a recurring problem with PDF files produced by pdftex in France. Whenever PhD thesis documents are submitted to the French national archives, they have to be validated by some automated process which relies on pdftk (apparently). And files compiled by pdftex are rejected. The problem is described here : https://groups.google.com/forum/#!topic/comp.text.pdf/ZnobgbiiDZ4 French pdftex users will have an eternal gratitude to whoever will fix this :-) Best regards, -- Fabrice Popineau ----------------------------- CentraleSupelec Département Informatique 3, rue Joliot Curie 91192 Gif/Yvette Cedex Tel direct : +33 (0) 169851950 Standard : +33 (0) 169851212 ------------------------------

7 11

Re: [NTG-pdftex] Fwd: Supressing PTEX.Fullbanner and Producer version strings
by Norbert Preining 30 Apr '16

30 Apr '16

Hi Akira, hi all, (please cc, not on the list) > (2) New primitives \pdfinfoomitdate and \pdftrailerid. > If \pdfinfoomitdate=1, date is omitted. > If \pdftrailerid{somestring}, somestring is used as the trailer. > It can be \pdftrailerid{}. I am playing with this and found that it doesn't work without problems in ini files: $ pdftex -ini ***\relax entering extended mode *\input pdftexconfig.tex (/home/norbert/tl/2016/texmf-dist/tex/generic/tex-ini-files/pdftexconfig.tex) *\pdfinfoomitdate = 1 *\pdfsuppressptexinfo = 1 *\pdftrailerid{} ! Missing { inserted. <to be read again> { <*> \pdftrailerid{ } ? *\pdftrailerid{} * So the *first* call to \pdftrailerid (and \pdfinfo the same!) fails but the second call works out. It seems that there is a problem withthe caatcode of the { which only gets set after the error handler is entered. That is current TeX Live source (svn) build. All the best Norbert (please cc, not on the list) ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 ------------------------------------------------------------------------

2 3

Deterministic PDFs (switch to disable addition of timestamps and random ID nonces)
by Markus Kuhn 26 Jun '15

26 Jun '15

For some applications, especially where the output of pdftex lives in any kind of version-control system, it would be extremely helpful to have a switch that causes pdftex to output deterministic PDF files. At present, there are three fields in each PDF generated by pdfTeX that change at each run on identical source files: $ pdftex '\hbox{}\vfill\eject\end' Output written on texput.pdf (1 page, 8182 bytes). $ mv texput.pdf texput2.pdf $ pdftex '\hbox{}\vfill\eject\end' Output written on texput.pdf (1 page, 8182 bytes). $ diff -a texput.pdf texput2.pdf 51,52c51,52 < /CreationDate (D:20150619105331+01'00') < /ModDate (D:20150619105331+01'00') --- > /CreationDate (D:20150619105323+01'00') > /ModDate (D:20150619105323+01'00') 76c76 < /ID [<BA26D54E6C14BF8195356C4A7162A40A> <BA26D54E6C14BF8195356C4A7162A40A>] --- > /ID [<D5B098C606C27E75987095F36CDCFED7> <D5B098C606C27E75987095F36CDCFED7>] Looking at the PDF 1.7 specification in ISO 32000 at http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_20… I believe that all these non-deterministic elements are optional, and could be suppressed without violating the PDF specification: Table 317 on page 550 says that the CreatingDate entry of the document information directory is optional, and the ModDate entry is optional unless PieceInfo is present. Pdftex does not output PieceInfo, right? So ModDate is also optional here. Likewise, the ID element appears to be optional as long as the PDF document is not encrypted. For DVI mode, we have already "-output-comment ''" to suppress the addition of a timestamp. Feature request: Would it be possible to add a switch, for example a command-line option like "-deterministic-output" that suppresses the automatic addition of timestamps and random ID byte strings to the generated PDF, such that repeated runs of pdftex produce identical output? Thanks, Markus -- Markus Kuhn, Computer Laboratory, University of Cambridge http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain

4 9

Bug#773668: okular shows "jumping" letters in pdf documents generated using pdflatex with russian babel
by Askar Safin 21 Dec '14

21 Dec '14

Package: okular Version: 4:4.8.4-3+b1 Severity: normal Tags: l10n Steps to reproduce: * Create the following file tex.tex: \documentclass[a4paper]{article} \usepackage[russian]{babel} \begin{document} Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed ... \end{document} * pdflatex tex.tex * okular tex.pdf * Adjust zoom until you will see ugly "jumping" letters (i. e. one letter is up, and the following letter in the same word is down). For example, on my laptop with screen resolution 1600 x 900 pixels and physical size 214.8 cm x 381.9 cm zoom 100 % will go What I see? Well, "jumping" letters. I see something like this: "LOrEm IpSum DOlOr SIT AmEt ...". See screenshot: http://picpaste.com/y-gh3PH69b.png . What I expected to see? Normal beautiful text. Including [russian]{babel} is mandatory to reproduce the bug. [english]{babel} will not go. But the text itself need not to be in Russian. You don't need even \usepackage[...]{inputenc}. latex tex.tex + okular tex.dvi - no bug. latex tex.tex + dvipdfm tex.dvi + okular tex.pdf - no bug. pdflatex tex.tex + okular tex.pdf - bug. pdflatex tex.tex + evince tex.pdf - no bug. pdflatex tex.tex + transfer this tex.pdf to Windows machine + open it with Adobe Reader on Windows - no bug. TeXLive version info: ii texlive-base 2012.20120611-5 all TeX Live: Essential programs and files ii texlive-binaries 2012.20120628-4 amd64 Binaries for TeX Live ii texlive-common 2012.20120611-5 all TeX Live: Base component ii texlive-doc-base 2012.20120611-1 all TeX Live: TeX Live documentation ii texlive-extra-utils 2012.20120611-2 all TeX Live: TeX auxiliary programs ii texlive-font-utils 2012.20120611-2 all TeX Live: Graphics and font utilities ii texlive-fonts-recommended 2012.20120611-5 all TeX Live: Recommended fonts ii texlive-generic-extra 2012.20120611-2 all TeX Live: Extra generic packages ii texlive-generic-recommended 2012.20120611-5 all TeX Live: Recommended generic packages ii texlive-lang-cyrillic 2012.20120611-2 all TeX Live: Cyrillic ii texlive-latex-base 2012.20120611-5 all TeX Live: Basic LaTeX packages ii texlive-latex-extra 2012.20120611-2 all TeX Live: LaTeX supplementary packages ii texlive-latex-recommended 2012.20120611-5 all TeX Live: LaTeX recommended packages ii texlive-math-extra 2012.20120611-2 all TeX Live: Advanced math typesetting ii texlive-metapost 2012.20120611-5 all TeX Live: MetaPost (and Metafont) drawing packages ii texlive-pictures 2012.20120611-5 all TeX Live: Graphics packages and programs -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages okular depends on: ii kde-runtime 4:4.8.4-2 ii libc6 2.18-4 ii libfreetype6 2.4.9-1.1 ii libjpeg8 8d-1+deb7u1 ii libkdecore5 4:4.8.4-4+deb7u1 ii libkdeui5 4:4.8.4-4+deb7u1 ii libkio5 4:4.8.4-4+deb7u1 ii libkparts4 4:4.8.4-4+deb7u1 ii libkprintutils4 4:4.8.4-4+deb7u1 ii libkpty4 4:4.8.4-4+deb7u1 ii libokularcore1 4:4.8.4-3+b1 ii libphonon4 4:4.6.0.0-3 ii libpoppler-qt4-3 0.18.4-6 ii libqca2 2.0.3-4 ii libqimageblitz4 1:0.0.6-4 ii libqt4-dbus 4:4.8.2+dfsg-11 ii libqt4-svg 4:4.8.2+dfsg-11 ii libqt4-xml 4:4.8.2+dfsg-11 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libsolid4 4:4.8.4-4+deb7u1 ii libspectre1 0.2.7-2 ii libstdc++6 4.7.2-5 ii phonon 4:4.6.0.0-3 ii zlib1g 1:1.2.7.dfsg-13 okular recommends no packages. Versions of packages okular suggests: ii ghostscript 9.05~dfsg-6.3+deb7u1 pn jovie <none> ii okular-extra-backends 4:4.8.4-3+b1 ii poppler-data 0.4.5-10 ii texlive-binaries 2012.20120628-4 ii unrar 1:3.9.10-1 -- no debconf information

1 0