- ntg-pdftex - NTG Mailing Lists

[pdftex-Bugs][2100] colors on page influenced by included pdf image
by pdftex-bugs＠sarovar.org 10 Oct '08

10 Oct '08

Bugs item #2100, was opened at 2008-10-09 00:18 Status: Open Priority: 3 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Nobody (None) Summary: colors on page influenced by included pdf image Category: PDF inclusion >Group: v1.40.8 Resolution: None Initial Comment: I've got a problem with defined colors on a page when I include a pdf image. The original file (regression-org.pdf) is included on the second page: blue and red on that page are different from the blue and red on the other pages. However, if I convert the included pdf image to ps via pdftops and back to pdf via pstopdf (regression.pdf), there's no problem as shown on the last page. Is this a bug in pdftex, or am I using an "incorrectly" generated pdf image file, since a double conversion seems to produce the correct output? (I'm using texlive's 2008 pdftex 1.40.9) Best regards Stefan ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-10-10 10:56 Message: I don't think the problem here is transparency (I don't find a /Group), but ICC, as regression-org.pdf uses an /ICCbased colorspace. Oh, and I get the same colours here with 1.40.9 and AR8 on Linux. ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2008-10-10 10:13 Message: It's a known problem of later AR versions if transparency is involved. Then AR seems to be using a different method for displaying the page and colors may change. PostScript doesn't support transparency, thus converting to PS and back to PDF gets rid of the transparency. Tested with: * AR7/Linux, AR8/Linux: wrong displayed colors * AR5/Linux: correct colors * xpdf3.00: correct colors * gs8.54: correct colors, but warnings for second page: CS/cs (setcolorspace) operand not a name: [/ICCBased -dict-] * gs8.62: fails on page two with /unknownerror. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2100&group_id=106

1 0

[pdftex-Bugs][2100] colors on page influenced by included pdf image
by pdftex-bugs＠sarovar.org 10 Oct '08

10 Oct '08

Bugs item #2100, was opened at 2008-10-09 00:18 Status: Open Priority: 3 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Nobody (None) Summary: colors on page influenced by included pdf image Category: PDF inclusion Group: None Resolution: None Initial Comment: I've got a problem with defined colors on a page when I include a pdf image. The original file (regression-org.pdf) is included on the second page: blue and red on that page are different from the blue and red on the other pages. However, if I convert the included pdf image to ps via pdftops and back to pdf via pstopdf (regression.pdf), there's no problem as shown on the last page. Is this a bug in pdftex, or am I using an "incorrectly" generated pdf image file, since a double conversion seems to produce the correct output? (I'm using texlive's 2008 pdftex 1.40.9) Best regards Stefan ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2008-10-10 10:13 Message: It's a known problem of later AR versions if transparency is involved. Then AR seems to be using a different method for displaying the page and colors may change. PostScript doesn't support transparency, thus converting to PS and back to PDF gets rid of the transparency. Tested with: * AR7/Linux, AR8/Linux: wrong displayed colors * AR5/Linux: correct colors * xpdf3.00: correct colors * gs8.54: correct colors, but warnings for second page: CS/cs (setcolorspace) operand not a name: [/ICCBased -dict-] * gs8.62: fails on page two with /unknownerror. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2100&group_id=106

1 0

[pdftex-Bugs][2100] colors on page influenced by included pdf image
by pdftex-bugs＠sarovar.org 09 Oct '08

09 Oct '08

Bugs item #2100, was opened at 2008-10-09 00:18 Status: Open Priority: 3 Submitted By: Stefan Becuwe (sbecuwe) Assigned to: Nobody (None) Summary: colors on page influenced by included pdf image Category: PDF inclusion Group: None Resolution: None Initial Comment: I've got a problem with defined colors on a page when I include a pdf image. The original file (regression-org.pdf) is included on the second page: blue and red on that page are different from the blue and red on the other pages. However, if I convert the included pdf image to ps via pdftops and back to pdf via pstopdf (regression.pdf), there's no problem as shown on the last page. Is this a bug in pdftex, or am I using an "incorrectly" generated pdf image file, since a double conversion seems to produce the correct output? (I'm using texlive's 2008 pdftex 1.40.9) Best regards Stefan ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2100&group_id=106

1 0

[pdftex-Patches][2098] Fix for xref_offset_width
by pdftex-patches＠sarovar.org 30 Sep '08

30 Sep '08

Patches item #2098, was opened at 2008-09-30 11:58 Status: Open Priority: 3 Submitted By: Martin Schröder (oneiros) Assigned to: Nobody (None) Summary: Fix for xref_offset_width Resolution: None Group: v1.50.0 Category: Large File Support Initial Comment: We have observed corrupted PDFs with PDF 1.5, object compression and moderately large files (200MB). Apparently the code to set xref_offset_width is not really portable; I've instead of Pascal implemented it in C and made it more robust. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=2098&group_id=106

1 0

SyncTeX, file names with spaces and other funny characters
by LAURENS Jérôme 19 Sep '08

19 Sep '08

Hi, there is actually a bug when SyncTeX has to manage spaces in file names. This bug only appears in pdfTeX, but not in XeTeX. Here it is: xetex --synctex=1 "my file" creates a file named <my file.synctex.gz>, whereas pdftex --synctex=1 "my file" creates a file named <"my file".synctex.gz>. Note that the 2 quote chars are considered by pdftex part of the name. This difference is due to some "normalize_quotes" function being used differently in XeTeX and pdfTeX. As usual, it is really difficult to understand how TeX handles things internally. This is why I submit you my simple fix before texlive is updated, you may have a better approach. The fix is simply to rely on the output_file_name (instead of the jobname), remove the terminating path extension and append to one required by SyncTeX. It works for the very simple tests I could think of. Do you agree? BTW, it is natural to ask whether different but similar problems may occur. Assuming the funny file named <tes"t.tex> exists xetex tes\"t.tex works properly whereas pdftex tes\"t.tex breaks in the normalize_quotes function with the message: ! Unbalanced quotes in argument tes"t.tex Are there reasons for such a discrimination?

2 1

[pdftex-Bugs][2092] Ligatures and special characters in included pdf disappear in typesetted document
by pdftex-bugs＠sarovar.org 18 Sep '08

18 Sep '08

Bugs item #2092, was opened at 2008-09-18 10:36 Status: Open Priority: 3 Submitted By: Jan Michael (jan) Assigned to: Nobody (None) Summary: Ligatures and special characters in included pdf disappear in typesetted document >Resolution: Accepted Group: None Category: PDF inclusion Initial Comment: Dear Readers, as the subject already states, my documents created with pdflatex are loosing their ligatures and other special characters from included pdf documents which were typesetted by other applications (Word, Excel, Omnigraffle ...). (a) Situation ------------- This is how the behaviour can be reproduced and how it happens in my case: (1) Import Latin Modern fonts as otf into system wide font location (2) Create a document with Latin Modern Roman font and use ff, fi, fl ligatures (3) Save Document as PDF (in OS X it's just "Save as PDF ...") - the pdf still shows the ligatures (4) Include the created pdf into a *.tex document with \includegraphics (5) Typeset the document with pdflatex (6) Ligatures from included pdf document disappear while inline ligature are typeset as usual. (b) Minimal Example ------------------- \documentclass[ngerman]{scrreprt} \usepackage{graphicx} \begin{document} \begin{figure}[htbp!] \centering\includegraphics[width=1.1\textwidth]{ligaturen.pdf} \end{figure} \end{document} ligaturen.pdf can be downloaded from <https://dl.getdropbox.com/u/73200/ligaturen.pdf> (c) Problem Analysis -------------------- This is what the the German tex usenet group de.comp.text.tex has already figured out: - problem can be reproduced with MiKTeX 2.6 and TexLive 2008 (Windows) - names of ligature glyphs in included pdf (f_i, f_l, f_f) differ from names used by pdftex (fi, fl, ff) - font from included pdf is replaced by pdftex -> glyphs f_i, ... won't be found anymore - behaviour can be suppressed by using \pdfmapfile{} - behaviour can be suppressed by removing or renaming related fonts in pdftex.map - behaviour can be suppressed by typesetting the pdf with xe(la)tex before including it in pdf(la)tex document. XeTeX redeclares the font in ligaturen.pdf from JTSEMF+LMRoman10-Regular to ASKXQL+LMRoman10-Regular-Identity-H. The related thread, in German language, can be found here: <http://groups.google.de/group/de.comp.text.tex/browse_frm/thread/4c0245d37c…> Right now I use the workaround with XeTeX to get my documents right. What do you think? Cheers, Jan ------------------------------------------------------------ p.s. Please see pdf(la)tex version information below: (from TexLive 2007 shipped with MacTeX 2007 package on MacBook C2D running OS X 10.5.5) $ pdflatex -v pdfTeX 3.141592-1.40.3-2.2 (Web2C 7.5.6) kpathsea version 3.5.6 Copyright 2007 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Kpathsea is copyright 2007 Karl Berry and Olaf Weber. There is NO warranty. Redistribution of this software is covered by the terms of both the pdfTeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the pdfTeX source. Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Kpathsea written by Karl Berry, Olaf Weber, and others. Compiled with libpng 1.2.15; using libpng 1.2.15 Compiled with zlib 1.2.3; using zlib 1.2.3 Compiled with xpdf version 3.01 ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2008-09-18 12:06 Message: yes this is an unfortunate situation: both the font from included pdf and the font on disk use the same name (LMRoman10-Regular), but they differ. Workarounds have been also mentioned; in short they fall into 2 methods: - disable font subsetting globally, or - change the font name in included pdf to something else, hence pdftex will not think this is the same font as the one on disk none is perfect, and also it's not clear how pdftex should handle such cases. Needs more thinking... ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2092&group_id=106

1 0

Re: [NTG-pdftex] Possible Bug: Ligatures and special Character in included pdf disappear in typetted document
by Thanh Han The 18 Sep '08

18 Sep '08

Hello Michael, thanks for the bug report. Can you please also submit it to the pdftex bug tracker http://sarovar.org/tracker/?atid=493&group_id=106&func=browse thanks, Thanh On Thu, Sep 18, 2008 at 12:51:18PM +0200, Jan Michael wrote: > Dear Readers, > > as the subject already states, my documents created with pdflatex are > loosing their ligatures and other special characters from included pdf > documents which were typesetted by other applications (Word, Excel, > Omnigraffle ...). > > > (a) Situation > ------------- > > This is how the behaviour can be reproduced and how it happens in my > case: > > (1) Import Latin Modern fonts as otf into system wide font location > (2) Create a document with Latin Modern Roman font and use ff, fi, fl > ligatures > (3) Save Document as PDF (in OS X it's just "Save as PDF ...") - the > pdf still shows the ligatures > (4) Include the created pdf into a *.tex document with \includegraphics > (5) Typeset the document with pdflatex > (6) Ligatures from included pdf document disappear while inline > ligature are typeset as usual. > > (b) Minimal Example > ------------------- > \documentclass[ngerman]{scrreprt} > \usepackage{graphicx} > \begin{document} > \begin{figure}[htbp!] > \centering\includegraphics[width=1.1\textwidth] > {ligaturen.pdf} > \end{figure} > \end{document} > > ligaturen.pdf can be downloaded from <https://dl.getdropbox.com/u/73200/ligaturen.pdf > > > > (c) Problem Analysis > -------------------- > This is what the the German tex usenet group de.comp.text.tex has > already figured out: > > - problem can be reproduced with MiKTeX 2.6 and TexLive 2008 (Windows) > - names of ligature glyphs in included pdf (f_i, f_l, f_f) differ from > names used by pdftex (fi, fl, ff) > - font from included pdf is replaced by pdftex -> glyphs f_i, ... > won't be found anymore > - behaviour can be suppressed by using \pdfmapfile{} > - behaviour can be suppressed by removing or renaming related fonts in > pdftex.map > - behaviour can be suppressed by typesetting the pdf with xe(la)tex > before including it in pdf(la)tex document. XeTeX redeclares the font > in ligaturen.pdf from JTSEMF+LMRoman10-Regular to ASKXQL+LMRoman10- > Regular-Identity-H. > > The related thread, in German language, can be found here: > > <http://groups.google.de/group/de.comp.text.tex/browse_frm/thread/4c0245d37c… > > > > Right now I use the workaround with XeTeX to get my documents right. > What do you think? > > Cheers, > > Jan > > ------------------------------------------------------------ > > p.s. Please see pdf(la)tex version information below: > (from TexLive 2007 shipped with MacTeX 2007 package on MacBook > C2D running OS X 10.5.5) > > $ pdflatex -v > pdfTeX 3.141592-1.40.3-2.2 (Web2C 7.5.6) > kpathsea version 3.5.6 > Copyright 2007 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). > Kpathsea is copyright 2007 Karl Berry and Olaf Weber. > There is NO warranty. Redistribution of this software is > covered by the terms of both the pdfTeX copyright and > the Lesser GNU General Public License. > For more information about these matters, see the file > named COPYING and the pdfTeX source. > Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh > (pdfTeX). > Kpathsea written by Karl Berry, Olaf Weber, and others. > > Compiled with libpng 1.2.15; using libpng 1.2.15 > Compiled with zlib 1.2.3; using zlib 1.2.3 > Compiled with xpdf version 3.01 > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

1 0

Possible Bug: Ligatures and special Character in included pdf disappear in typetted document
by Jan Michael 18 Sep '08

18 Sep '08

Dear Readers, as the subject already states, my documents created with pdflatex are loosing their ligatures and other special characters from included pdf documents which were typesetted by other applications (Word, Excel, Omnigraffle ...). (a) Situation ------------- This is how the behaviour can be reproduced and how it happens in my case: (1) Import Latin Modern fonts as otf into system wide font location (2) Create a document with Latin Modern Roman font and use ff, fi, fl ligatures (3) Save Document as PDF (in OS X it's just "Save as PDF ...") - the pdf still shows the ligatures (4) Include the created pdf into a *.tex document with \includegraphics (5) Typeset the document with pdflatex (6) Ligatures from included pdf document disappear while inline ligature are typeset as usual. (b) Minimal Example ------------------- \documentclass[ngerman]{scrreprt} \usepackage{graphicx} \begin{document} \begin{figure}[htbp!] \centering\includegraphics[width=1.1\textwidth] {ligaturen.pdf} \end{figure} \end{document} ligaturen.pdf can be downloaded from <https://dl.getdropbox.com/u/73200/ligaturen.pdf > (c) Problem Analysis -------------------- This is what the the German tex usenet group de.comp.text.tex has already figured out: - problem can be reproduced with MiKTeX 2.6 and TexLive 2008 (Windows) - names of ligature glyphs in included pdf (f_i, f_l, f_f) differ from names used by pdftex (fi, fl, ff) - font from included pdf is replaced by pdftex -> glyphs f_i, ... won't be found anymore - behaviour can be suppressed by using \pdfmapfile{} - behaviour can be suppressed by removing or renaming related fonts in pdftex.map - behaviour can be suppressed by typesetting the pdf with xe(la)tex before including it in pdf(la)tex document. XeTeX redeclares the font in ligaturen.pdf from JTSEMF+LMRoman10-Regular to ASKXQL+LMRoman10- Regular-Identity-H. The related thread, in German language, can be found here: <http://groups.google.de/group/de.comp.text.tex/browse_frm/thread/4c0245d37c… > Right now I use the workaround with XeTeX to get my documents right. What do you think? Cheers, Jan ------------------------------------------------------------ p.s. Please see pdf(la)tex version information below: (from TexLive 2007 shipped with MacTeX 2007 package on MacBook C2D running OS X 10.5.5) $ pdflatex -v pdfTeX 3.141592-1.40.3-2.2 (Web2C 7.5.6) kpathsea version 3.5.6 Copyright 2007 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Kpathsea is copyright 2007 Karl Berry and Olaf Weber. There is NO warranty. Redistribution of this software is covered by the terms of both the pdfTeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the pdfTeX source. Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Kpathsea written by Karl Berry, Olaf Weber, and others. Compiled with libpng 1.2.15; using libpng 1.2.15 Compiled with zlib 1.2.3; using zlib 1.2.3 Compiled with xpdf version 3.01

1 0

[pdftex-Bugs][2092] Ligatures and special characters in included pdf disappear in typesetted document
by pdftex-bugs＠sarovar.org 18 Sep '08

18 Sep '08

Bugs item #2092, was opened at 2008-09-18 12:36 Status: Open Priority: 3 Submitted By: Jan Michael (jan) Assigned to: Nobody (None) Summary: Ligatures and special characters in included pdf disappear in typesetted document Resolution: None Group: None Category: PDF inclusion Initial Comment: Dear Readers, as the subject already states, my documents created with pdflatex are loosing their ligatures and other special characters from included pdf documents which were typesetted by other applications (Word, Excel, Omnigraffle ...). (a) Situation ------------- This is how the behaviour can be reproduced and how it happens in my case: (1) Import Latin Modern fonts as otf into system wide font location (2) Create a document with Latin Modern Roman font and use ff, fi, fl ligatures (3) Save Document as PDF (in OS X it's just "Save as PDF ...") - the pdf still shows the ligatures (4) Include the created pdf into a *.tex document with \includegraphics (5) Typeset the document with pdflatex (6) Ligatures from included pdf document disappear while inline ligature are typeset as usual. (b) Minimal Example ------------------- \documentclass[ngerman]{scrreprt} \usepackage{graphicx} \begin{document} \begin{figure}[htbp!] \centering\includegraphics[width=1.1\textwidth]{ligaturen.pdf} \end{figure} \end{document} ligaturen.pdf can be downloaded from <https://dl.getdropbox.com/u/73200/ligaturen.pdf> (c) Problem Analysis -------------------- This is what the the German tex usenet group de.comp.text.tex has already figured out: - problem can be reproduced with MiKTeX 2.6 and TexLive 2008 (Windows) - names of ligature glyphs in included pdf (f_i, f_l, f_f) differ from names used by pdftex (fi, fl, ff) - font from included pdf is replaced by pdftex -> glyphs f_i, ... won't be found anymore - behaviour can be suppressed by using \pdfmapfile{} - behaviour can be suppressed by removing or renaming related fonts in pdftex.map - behaviour can be suppressed by typesetting the pdf with xe(la)tex before including it in pdf(la)tex document. XeTeX redeclares the font in ligaturen.pdf from JTSEMF+LMRoman10-Regular to ASKXQL+LMRoman10-Regular-Identity-H. The related thread, in German language, can be found here: <http://groups.google.de/group/de.comp.text.tex/browse_frm/thread/4c0245d37c…> Right now I use the workaround with XeTeX to get my documents right. What do you think? Cheers, Jan ------------------------------------------------------------ p.s. Please see pdf(la)tex version information below: (from TexLive 2007 shipped with MacTeX 2007 package on MacBook C2D running OS X 10.5.5) $ pdflatex -v pdfTeX 3.141592-1.40.3-2.2 (Web2C 7.5.6) kpathsea version 3.5.6 Copyright 2007 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Kpathsea is copyright 2007 Karl Berry and Olaf Weber. There is NO warranty. Redistribution of this software is covered by the terms of both the pdfTeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the pdfTeX source. Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Kpathsea written by Karl Berry, Olaf Weber, and others. Compiled with libpng 1.2.15; using libpng 1.2.15 Compiled with zlib 1.2.3; using zlib 1.2.3 Compiled with xpdf version 3.01 ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2092&group_id=106

1 0

[pdftex-Patches][2091] bugfix for #2090
by pdftex-patches＠sarovar.org 17 Sep '08

17 Sep '08

Patches item #2091, was opened at 2008-09-17 06:59 Status: Open Priority: 3 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: bugfix for #2090 Resolution: None Group: None Category: None Initial Comment: this patch is for 1.40.9 and the stable branch only. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2008-09-17 07:03 Message: update: don't forget to rerun autoconf after applying the patch. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=2091&group_id=106

1 0