- ntg-pdftex - NTG Mailing Lists

[pdftex-Feature Requests][662] avoid creating "fixed destination"
by pdftex-featurerequests＠sarovar.org 25 Mar '08

25 Mar '08

Feature Requests item #662, was opened at 2006-10-20 11:57 Status: Open Priority: 3 Submitted By: Ulrich Diez (ulrichdiez) Assigned to: The Thanh Han (hanthethanh) Summary: avoid creating "fixed destination" Resolution: None Group: v1.50 Category: Initial Comment: When referencing a non-existing destination, you get this warning: ! pdfTeX warning (dest): name{<something>} has been referenced but does not exist, replaced by a fixed one I always like the warning about non-existing destinations, but sometimes I'd prefer pdfTeX not to take action besides issuing a warning-message/I'd prefer pdfTeX not to create a "fixed" destination. E.g., when creating several separate pdf-files with pdfTeX (for later merging them together by means of external software like "pdftk" or "pdfcat") whereby the named destination is not known/available when compiling file A but is available/provided in file B so that in the result from merging these files, everything will be fine. Does it make sense/is it possible to implement some mechanism for forking if creation of fixed destination shall be avoided or not? (Either a new token/primitive similar to \globaldefs which can be used within TeX source or some command- line-option which can be specified at the command-line when running pdfTeX ?) Sincerely Ulrich ---------------------------------------------------------------------- Comment By: Ulrich Diez (ulrichdiez) Date: 2008-03-25 10:24 Message: This feature-request of mine is obsolete. By using \pdfliteral and \special you can easily create links to non-existing destinations which will not get replaced by "a fixed one" so that after pdf-concatenation links will work. I apologize for having send this feature-request. Sincerely Ulrich ---------------------------------------------------------------------- Comment By: Ulrich Diez (ulrichdiez) Date: 2008-03-25 10:23 Message: This feature-request of mine is obsolete. By using \pdfliteral and \special you can easily create links to non-existing destinations which will not get replaced by "a fixed one" so that after pdf-concatenation links will work. I apologize for having send this feature-request. Sincerely Ulrich ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=662&group_id=106

1 0

[pdftex-Feature Requests][662] avoid creating "fixed destination"
by pdftex-featurerequests＠sarovar.org 25 Mar '08

25 Mar '08

Feature Requests item #662, was opened at 2006-10-20 11:57 Status: Open Priority: 3 Submitted By: Ulrich Diez (ulrichdiez) Assigned to: The Thanh Han (hanthethanh) Summary: avoid creating "fixed destination" Resolution: None Group: v1.50 Category: Initial Comment: When referencing a non-existing destination, you get this warning: ! pdfTeX warning (dest): name{<something>} has been referenced but does not exist, replaced by a fixed one I always like the warning about non-existing destinations, but sometimes I'd prefer pdfTeX not to take action besides issuing a warning-message/I'd prefer pdfTeX not to create a "fixed" destination. E.g., when creating several separate pdf-files with pdfTeX (for later merging them together by means of external software like "pdftk" or "pdfcat") whereby the named destination is not known/available when compiling file A but is available/provided in file B so that in the result from merging these files, everything will be fine. Does it make sense/is it possible to implement some mechanism for forking if creation of fixed destination shall be avoided or not? (Either a new token/primitive similar to \globaldefs which can be used within TeX source or some command- line-option which can be specified at the command-line when running pdfTeX ?) Sincerely Ulrich ---------------------------------------------------------------------- Comment By: Ulrich Diez (ulrichdiez) Date: 2008-03-25 10:23 Message: This feature-request of mine is obsolete. By using \pdfliteral and \special you can easily create links to non-existing destinations which will not get replaced by "a fixed one" so that after pdf-concatenation links will work. I apologize for having send this feature-request. Sincerely Ulrich ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=662&group_id=106

1 0

[pdftex-Feature Requests][881] Integrate pool file
by pdftex-featurerequests＠sarovar.org 23 Mar '08

23 Mar '08

Feature Requests item #881, was opened at 2007-11-13 10:48 >Status: Closed Priority: 3 Submitted By: Taco Hoekwater (taco) Assigned to: Taco Hoekwater (taco) Summary: Integrate pool file >Resolution: Accepted Group: v1.50 Category: web2c Initial Comment: So we don't forget (XeTeX is also pool-free nowadays). ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-03-23 13:52 Message: Will be in 1.50 ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=881&group_id=106

1 0

[pdftex-Bugs][933] synchronization crashes
by pdftex-bugs＠sarovar.org 23 Mar '08

23 Mar '08

Bugs item #933, was opened at 2008-03-19 02:41 >Status: Closed Priority: 3 Submitted By: Robert (schlcht) Assigned to: Nobody (None) Summary: synchronization crashes >Resolution: Works For Me >Group: v1.50.0-alpha >Category: synctex Initial Comment: pdftex 1.50 crashes on either of the following here (cygwin): % pdflatex \synctex=1 \documentclass{minimal} \stop % pdftex \synctex=1 \font\x=cmr12 x \bye ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-03-23 13:49 Message: I can't reproduce this. Maybe it's a Cygwin issue? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=933&group_id=106

1 0

Fwd: [Sarovar.org] Downtime on 15 Mar 2008
by Martin Schröder 12 Mar '08

12 Mar '08

---------- Forwarded message ---------- From: Sarovar. org Admin <noreply(a)sarovar.org> Date: 12.03.2008 16:01 Subject: [Sarovar.org] Downtime on 15 Mar 2008 To: Martin Schröder <martin(a)oneiros.de> Hello, Sarovar.org will be down for maintenance on 15th March 2008 from 10 AM till 10 PM IST. We will be preforming a software as well as hardware upgrade during this time. While we do expect the migration to go smoothly and all data and settings to be migrated to the new server, please let us know if there are any problems after migration is complete. Thanks for using Sarovar.org and sorry for the inconvenience. Regards, Sarovar Team

1 0

Looking at a PDF/DVI while it is being produced
by David Kastrup 08 Mar '08

08 Mar '08

Hi, sometimes on a long run one would like to be able to take a look at the current state of a PDF being produced. I don't know whether there is something like a progressive PDF format: likely not. But if I could send a signal to my PDFTeX/LuaTeX process, and this would cause it (at least if it would not currently be in a \shipout) to flush the current buffers, create a copy of the current PDF/DVI file under a snapshot name, properly finish/close it (writing reference table/DVI trailers) and then resume regular work, this would be quite dandy. I often have the situation of starting a dead slow 1400 page compilation where I really need the full output, but can probably see after looking at a dozen pages whether or not the whole compilation will be rubbish, needs some minor change and restart. Being able to use a signal for "give me a viewable snapshot PDF/DVI for the current state of the document" would be rather invaluable. It would be conceivable to offer this as an option to the TeX interactive prompt, by typing >mysnap.pdf Then one could just interrupt PDFTeX using ^C as usual, and type this command for getting a snapshot. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum

4 4

Re: [NTG-pdftex] [pdftex] PDF Outlines in different versions of MiKTeX
by Heiko Oberdiek 08 Mar '08

08 Mar '08

On Fri, Mar 07, 2008 at 07:56:18AM -0600, Brad Burkman wrote: > I run pdfTeX 3.141592-1.20a (MiKTeX 2.4) on one computer, and pdfTeX > 3.141529-1.40.4 (MiKTeX 2.6) on another. When I compile the following > text: > > \pdfcatalog{/PageMode/UseOutlines} > > \pdfdest name{(-19,-17),(5,25),(17,19)} fit > > \pdfoutline goto > name{(-19,-17),(5,25),(17,19)}{(-19,-17),(5,25),(17,19)} > on the earlier version, everything works just fine. With the later > version, however, I get an outline pane but no bookmarks. Just a blank > pane. Has there been a syntax change? Perhaps different versions of > Acrobat? Windows XP v/s Vista? Error message of xpdf: Error (54): Dictionary key must be a name object And the PDF shows: 1 0 obj << /S /GoTo /D (-19,-17),(5,25),(17,19) >> endobj The surrounding parentheses are missing. pdftex.web, procedure pdf_print_str(s: str_number): ... if (str_pool[i] = '(') and (str_pool[j] = ')') then begin pdf_print(s); return; end; ... * First the test is insufficient, as the example shows. The test for a hex string is better. * Also it looks like a design error. I doubt, a user would suspect that \pdfdest name {abc} fit and \pdfdest name {(abc)} fit and \pdfdest name {<616263>} fit are using the same destination name. * Another BUG: \pdfdest name{a} fit \pdfdest name{(x)} fit \end The result is a wrong destination name tree: /Names [(x) 5 0 R (a) 4 0 R] /Limits [(x) (a)] `x' is sorted as destination name "(x)", but written as destination name "x". I think, pdfTeX shouldn't assume special meanings of the destination names. The byte string from the token list of keyword "name" should be the destination name without special meanings. And if pdfTeX writes the name, it takes care of the protection of special characters. Otherwise the user would have to use \pdfdest name{(\pdfescapestring{...})}... \pdfdest name{<\pdfescapehex{...}>}... to get control over the exact name. This isn't a good design, because implementation issues leaks into the user interface. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de>

1 0

[ pdftex-Bugs-741 ] wrong colors for included PDF-images (page groups)
by noreply＠sarovar.org 05 Mar '08

05 Mar '08

Bugs item #741, was opened at 2007-03-01 16:50 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=741&group_id=106 Category: PDF inclusion Group: v1.30.0 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Uwe Stöhr (stoehr) Assigned to: Martin Schröder (oneiros) Summary: wrong colors for included PDF-images (page groups) Initial Comment: Attached is a PDF 1.4 image. When you include this to a document the output generated by pdfetex 1.30.6 the images looks different: The colors are much darker, see attached PDF result. ---------------------------------------------------------------------- Comment By: Erich Hoover (compholio) Date: 2008-03-04 20:43 Message: Logged In: YES user_id=4885 If you are using a distribution that has not caught up with the new release then I have found a work-around that may help. You can "fix" a PDF you would like to embed by using the PDF Writer backend for cups to convert your PDF to CMYK. Simply open the PDF with acroread and then use the "PDF" printer, this will place the CMYK version of the file in the "~/PDF/" folder. In a somewhat related issue, I've found that embedding some PNG files causes the same conversion problem. However, I do not see why some PNG files would do this and others would not. If someone can point me in the right direction for solving this then I'd appreciate it. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-11-29 07:49 Message: Logged In: YES user_id=421 A fix for this will be included in the next release (1.40.6/1.50.0). ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-03 12:51 Message: Logged In: YES user_id=421 Fix is in the works. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-09-30 23:08 Message: Logged In: YES user_id=421 Adding /Group to the /Page is not an option for us (and probably wrong): What should we do when we have more than one included pdf on a page and they have different /CS entries? And why does transparency in an /XObject need an entry in the /Page? The entry in the /XObject should suffice. I wouldn't be surprised if AR is faulty here. ---------------------------------------------------------------------- Comment By: Adrian Johnson (ajohnson) Date: 2007-09-30 18:04 Message: Logged In: YES user_id=4699 After adding /Group << /CS /DeviceRGB /Type /Group /S /Transparency >> to the /Page object in newfile2-1.pdf it displays correctly in Acrobat. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-09-30 17:04 Message: Logged In: YES user_id=421 The attached file newfile2-1.pdf has a copied page group, which as I now know, should be correct. Still, AR8@Linux shows different colours for it and TestSkizze.pdf . ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-09-30 16:51 Message: Logged In: YES user_id=3168 > Why is this WONTFIX? Sorry, this bug was once closed when this additional info was not available. -> I reopened this bug. ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-09-30 16:46 Message: Logged In: YES user_id=3168 Why is this WONTFIX? I mean: > The file TestSkizze.pdf specifies the color blending space > with "/CS /DeviceRGB" in the transparency group. In > the PDF produced by pdftex this has been stripped out. So the bug is that pdftex strips out the color space. If you really think it's WONTFIX, then tell me what is the correct way of specifying the color space so that I can forward this to the Inkscape developers. ---------------------------------------------------------------------- Comment By: Adrian Johnson (ajohnson) Date: 2007-09-30 07:34 Message: Logged In: YES user_id=4699 The file TestSkizze.pdf specifies the color blending space with "/CS /DeviceRGB" in the transparency group. In the PDF produced by pdftex this has been stripped out. When the color space is not specified Acrobat defaults to CMYK. This results in RGB colors being converted to CMYK, blended in CMYK color space, then converted back to RGB. This will produce different results compared to blending the colors in RGB space. This problem was also reported to the cairo list: http://lists.cairographics.org/archives/cairo/2007-September/011471.html ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-03-03 11:41 Message: Logged In: YES user_id=3168 > To my eye the Harlequin results are the same for both > file, Yes and the result is correct. > while Jaws has to different results. In my eyes the Jaws results are identical but wrong. So it seems that pdftex is not the problem here, but it would be nice if pdftex could handle page groups in one of the next releases: >"PDF inclusion: Page Group detected which pdfTeX can't > handle. Ignoring it." So I'm not sure to close this bug or mark it as enhancement. Thanks for your help. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-03 07:48 Message: Logged In: YES user_id=421 I've attached the results of two professional RIPs: Global Graphics Jaws & Harlequin. To my eye the Harlequin results are the same for both file, while Jaws has to different results. :-{ ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-02 05:16 Message: Logged In: YES user_id=421 Your document is using Page Groups (see PDF Reference 7.3.6). Including pdfs that use this is a grey area; see the notes in NEWS and pdftoepdf.cc. It works most of the times and with most RIPs. I'll look into it again, but I don't have much hope. Btw: pdftex warns you: "PDF inclusion: Page Group detected which pdfTeX can't handle. Ignoring it." ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-03-02 05:05 Message: Logged In: YES user_id=3168 > problem in AR7 - but only there. But how could this be a bug in Acrobat when Adobe set the standards? Why is this correctly shown before the pdftex-run. The display is the same here in Acrobat 5 - 8 so I think they would have fixed it when it's a bug since Acrobat 5. Hmm but OK, when I open the result with GSview besides the GS bug, the color tones are correctly be displayed. So close this bug report again, when you are sure that pdftex follows here exactly the PDF-specification. ---------------------------------------------------------------------- Comment By: Uwe Stöhr (stoehr) Date: 2007-03-02 04:57 Message: Logged In: YES user_id=3168 > It's a bug in AR; No! Acrobat is correct: I created this image with Inkscape 0.45 and exported it the as PDF. I designed e.g. the green as light green. And Acrobat 7 and 8 shows this exactly as designed while the pdftex result has wrong color tones, see the attached screenshots. (Ghostscript is btw. not able to render the PDF-image correctly - I reported this to the GS people who confirmed it.) ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-03-01 17:05 Message: Logged In: YES user_id=421 You don't say it, but I see the same problem in AR7 - but only there. It's a bug in AR; try kpdf or ghostscript instead. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=741&group_id=106

1 0

BachoTeX 2008 -- Call for Papers -- reminder
by Jerzy B. Ludwichowski 04 Mar '08

04 Mar '08

Dear friends, The BachoTeX 2008 Program Committee dares to remind you of the quickly upcoming deadline for submitting paper proposals for the BachoTeX 2008 conference. The Call for Papers and TeX Pearls can be found http://www.gust.org.pl/BachoTeX/2008/cfp1en. We trust that the main theme of the conference, ,,TeX contra TeX'' should be of a great interest to the community at large and the various developers in particular. You may have noted that the supplementing theme "Aesthetic aspects of typesetting" is also addressed to those who use other typesetting software. If you know people active in this area please talk them into presenting a paper. Your children or very young TeXies in your vicinity are invited to contribute in the yet another conference supplementing theme "What is TeX to me?" Based on suggestions and experiences from previous years, one day of the conference will be devoted solely to working meetings of the various informal interest groups (no presentations): - fonts, - TeX engines, - distributions, - supporting software, - typesetting software in general, - propagating TeX, - history of TeX -- you name it. Talk your common interest buddies into coming and/or propose a paper. Do not forget submitting your "TeX Pearls" aka "TeX beauties and oddities"! And, finally -- registration is open at http://www.gust.org.pl/BachoTeX/2008/registration-en. Please note that early registration ending March 31 allows for a significant saving in the conference fee. Come and celebrate the XVIth, or $10000_{2}$ or $100_{4}$ or $20_{8}$ or $10_{16}$ BachoTeX! Jerzy Ludwichowski Organizing Committee

1 0

forwarded problem of 1.40.7 on powerpc
by Taco Hoekwater 28 Feb '08

28 Feb '08

Hi guys, See below for a bug in 1.40.7 as posted on the context list. As I wrote there, it looks like an endianness issue because 300000 >> 16 == 5 Either that, or some object has a different size on ppc, but that seems unlikely to me. I am hoping someone has a powerpc to try and sort this out. Best wishes, Taco -------- Original Message -------- Subject: Re: [NTG-context] bib module and pdftex 1.40.7: Virtual memory exhausted using MiKTeX-2.7 Date: Wed, 27 Feb 2008 10:26:46 +0100 From: Thomas A. Schmitz <thomas.schmitz(a)uni-bonn.de> Reply-To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> On Feb 20, 2008, at 10:05 AM, luigi scarso wrote: >> Just the other day, I encountered a mysterious error which may or may >> not be related. I upgraded to pdftex 1.40.7 on all my boxes. This was >> smooth on my intel-macs (OS X 10.5.2). On my powerpc-mac, I got a >> "TeX >> capacity exceeded!" error with 1.40.7 for a file that compiled fine >> with 1.40.5. I tried several times: all I did was dropping the pdftex >> binary and pdftex.pool in place, rebuilding th format and compiling >> the file. Compilation was smooth with 1.40.5 and consistently failed >> with 1.40.7 (which I compiled and recompiled without any special >> flags). I haven't pursued the matter for the moment and just went >> back >> to 1.40.5, but I'm wondering if these problems are related. > Do you have a test file ? > Sorry, it took me a while because this is the computer in my office, from which I;ve been away for a while. I think I nailed it down: if I try to include a pdf image into a ConTeXt document \starttext \externalfigure[Logo][width=56mm,height=20mm] \stoptext (with any pdf file) I get this error: <./Logo.pdf ! TeX capacity exceeded, sorry [PDF object stream buffer=5]. \dogetTPDfiguresize ...geBox {\@@DriverImageFile } \xdef \PDFimagereference {... \doanalyzefiguredimensionsinternal ...tfiguresize \setanalyzedfiguredimensio... <argument> ...}\doanalyzefiguredimensionsinternal \doanalyzefiguredimensions... \firstoftwoarguments #1#2->#1 \dododoanalyzeunknownfiguretype ...guredimensions \fi \next2 ...dododoanalyzeunknownfiguretype {pdf}{#1} \doprocesscommaitem ... l.4 ! ==> Fatal error occurred, no output PDF file produced! The pdf file is OK; this error only occurs with pdftex 1.40.7 on powerpc (OS X, 10.5.2). The same file compiles fine with luatex on powerpc and intel pdftex 1.40.5 on powerpc and intel pdftex 1.40.7 on OS X intel All best Thomas ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

3 5

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-14 00:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: v1.40.6 >Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-02-14 16:43 Message: Logged In: YES user_id=421 Then your compile was broken. We'll fix that in 1.50.0 :-) ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 16:32 Message: Logged In: YES user_id=4856 "Are you by chance trying to produce a pdf larger then 2GiB?" Ah, now we're getting somewhere! No, the test file I was using resulted in a pdf of only 4K, but... when I built pdftex I was using a version of build.sh that I had previously modified and saved, and it did not contain the configure flag "--disable-largefile", which I see is in the current build.sh. I added that flag, recompiled pdftex, and now it works fine. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 14:23 Message: Logged In: YES user_id=421 Are you by chance trying to produce a pdf larger then 2GiB? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 10:10 Message: Logged In: YES user_id=421 The error message probably comes from the kernel or libc; the string "Invalid argument" is only in ttf2afm.c allin, can you start a gdb, set a breakpoint in exit and get a backtrace? ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2008-02-14 09:10 Message: Logged In: YES user_id=1608 Works for me as well. The most likely candidate for creating this problem is the pfb file, not the map file. The actual error message probably comes from zlib, not the map file parser. Can you check that /usr/local/psfonts/bsr/cmr10.pfb is exactly 26882 bytes long? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 02:34 Message: Logged In: YES user_id=4856 I've now tried using a much simpler map file, but that didn't help. Here what strace says, at the end of reading the map file: read(7, "wncysc10.pfb\nwncyss10 <wncyss10."..., 4096) = 783 read(7, "", 4096) = 0 close(7) = 0 munmap(0xb7fdc000, 4096) = 0 write(1, "}", 1}) = 1 brk(0x835e000) = 0x835e000 brk(0x838e000) = 0x838e000 write(6, "%PDF-1.4\n%\320\324\305\330\n3 0 obj <<\n/Lengt"..., 156) = 156 write(2, "pdflatex: ", 10pdflatex: ) = 10 write(2, "Invalid argument\n", 17Invalid argument ) = 17 write(5, "\relax \n", 8) = 8 write(4, "This is pdfTeX, Version 3.141592"..., 1511) = 1511 exit_group(1) = ? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 01:40 Message: Logged In: YES user_id=4856 Minimal test file and log from pdftex 1.40.5 are added below. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 01:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-13 18:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: v1.40.6 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- >Comment By: Allin Cottrell (allin) Date: 2008-02-14 10:32 Message: Logged In: YES user_id=4856 "Are you by chance trying to produce a pdf larger then 2GiB?" Ah, now we're getting somewhere! No, the test file I was using resulted in a pdf of only 4K, but... when I built pdftex I was using a version of build.sh that I had previously modified and saved, and it did not contain the configure flag "--disable-largefile", which I see is in the current build.sh. I added that flag, recompiled pdftex, and now it works fine. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 08:23 Message: Logged In: YES user_id=421 Are you by chance trying to produce a pdf larger then 2GiB? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 04:10 Message: Logged In: YES user_id=421 The error message probably comes from the kernel or libc; the string "Invalid argument" is only in ttf2afm.c allin, can you start a gdb, set a breakpoint in exit and get a backtrace? ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2008-02-14 03:10 Message: Logged In: YES user_id=1608 Works for me as well. The most likely candidate for creating this problem is the pfb file, not the map file. The actual error message probably comes from zlib, not the map file parser. Can you check that /usr/local/psfonts/bsr/cmr10.pfb is exactly 26882 bytes long? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-13 20:34 Message: Logged In: YES user_id=4856 I've now tried using a much simpler map file, but that didn't help. Here what strace says, at the end of reading the map file: read(7, "wncysc10.pfb\nwncyss10 <wncyss10."..., 4096) = 783 read(7, "", 4096) = 0 close(7) = 0 munmap(0xb7fdc000, 4096) = 0 write(1, "}", 1}) = 1 brk(0x835e000) = 0x835e000 brk(0x838e000) = 0x838e000 write(6, "%PDF-1.4\n%\320\324\305\330\n3 0 obj <<\n/Lengt"..., 156) = 156 write(2, "pdflatex: ", 10pdflatex: ) = 10 write(2, "Invalid argument\n", 17Invalid argument ) = 17 write(5, "\relax \n", 8) = 8 write(4, "This is pdfTeX, Version 3.141592"..., 1511) = 1511 exit_group(1) = ? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-13 19:40 Message: Logged In: YES user_id=4856 Minimal test file and log from pdftex 1.40.5 are added below. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-13 19:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-14 00:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: v1.40.6 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-02-14 14:23 Message: Logged In: YES user_id=421 Are you by chance trying to produce a pdf larger then 2GiB? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 10:10 Message: Logged In: YES user_id=421 The error message probably comes from the kernel or libc; the string "Invalid argument" is only in ttf2afm.c allin, can you start a gdb, set a breakpoint in exit and get a backtrace? ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2008-02-14 09:10 Message: Logged In: YES user_id=1608 Works for me as well. The most likely candidate for creating this problem is the pfb file, not the map file. The actual error message probably comes from zlib, not the map file parser. Can you check that /usr/local/psfonts/bsr/cmr10.pfb is exactly 26882 bytes long? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 02:34 Message: Logged In: YES user_id=4856 I've now tried using a much simpler map file, but that didn't help. Here what strace says, at the end of reading the map file: read(7, "wncysc10.pfb\nwncyss10 <wncyss10."..., 4096) = 783 read(7, "", 4096) = 0 close(7) = 0 munmap(0xb7fdc000, 4096) = 0 write(1, "}", 1}) = 1 brk(0x835e000) = 0x835e000 brk(0x838e000) = 0x838e000 write(6, "%PDF-1.4\n%\320\324\305\330\n3 0 obj <<\n/Lengt"..., 156) = 156 write(2, "pdflatex: ", 10pdflatex: ) = 10 write(2, "Invalid argument\n", 17Invalid argument ) = 17 write(5, "\relax \n", 8) = 8 write(4, "This is pdfTeX, Version 3.141592"..., 1511) = 1511 exit_group(1) = ? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 01:40 Message: Logged In: YES user_id=4856 Minimal test file and log from pdftex 1.40.5 are added below. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 01:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-14 00:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: v1.40.6 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-02-14 10:10 Message: Logged In: YES user_id=421 The error message probably comes from the kernel or libc; the string "Invalid argument" is only in ttf2afm.c allin, can you start a gdb, set a breakpoint in exit and get a backtrace? ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2008-02-14 09:10 Message: Logged In: YES user_id=1608 Works for me as well. The most likely candidate for creating this problem is the pfb file, not the map file. The actual error message probably comes from zlib, not the map file parser. Can you check that /usr/local/psfonts/bsr/cmr10.pfb is exactly 26882 bytes long? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 02:34 Message: Logged In: YES user_id=4856 I've now tried using a much simpler map file, but that didn't help. Here what strace says, at the end of reading the map file: read(7, "wncysc10.pfb\nwncyss10 <wncyss10."..., 4096) = 783 read(7, "", 4096) = 0 close(7) = 0 munmap(0xb7fdc000, 4096) = 0 write(1, "}", 1}) = 1 brk(0x835e000) = 0x835e000 brk(0x838e000) = 0x838e000 write(6, "%PDF-1.4\n%\320\324\305\330\n3 0 obj <<\n/Lengt"..., 156) = 156 write(2, "pdflatex: ", 10pdflatex: ) = 10 write(2, "Invalid argument\n", 17Invalid argument ) = 17 write(5, "\relax \n", 8) = 8 write(4, "This is pdfTeX, Version 3.141592"..., 1511) = 1511 exit_group(1) = ? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 01:40 Message: Logged In: YES user_id=4856 Minimal test file and log from pdftex 1.40.5 are added below. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 01:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-14 00:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: v1.40.6 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2008-02-14 09:10 Message: Logged In: YES user_id=1608 Works for me as well. The most likely candidate for creating this problem is the pfb file, not the map file. The actual error message probably comes from zlib, not the map file parser. Can you check that /usr/local/psfonts/bsr/cmr10.pfb is exactly 26882 bytes long? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 02:34 Message: Logged In: YES user_id=4856 I've now tried using a much simpler map file, but that didn't help. Here what strace says, at the end of reading the map file: read(7, "wncysc10.pfb\nwncyss10 <wncyss10."..., 4096) = 783 read(7, "", 4096) = 0 close(7) = 0 munmap(0xb7fdc000, 4096) = 0 write(1, "}", 1}) = 1 brk(0x835e000) = 0x835e000 brk(0x838e000) = 0x838e000 write(6, "%PDF-1.4\n%\320\324\305\330\n3 0 obj <<\n/Lengt"..., 156) = 156 write(2, "pdflatex: ", 10pdflatex: ) = 10 write(2, "Invalid argument\n", 17Invalid argument ) = 17 write(5, "\relax \n", 8) = 8 write(4, "This is pdfTeX, Version 3.141592"..., 1511) = 1511 exit_group(1) = ? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-14 01:40 Message: Logged In: YES user_id=4856 Minimal test file and log from pdftex 1.40.5 are added below. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-14 01:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-13 18:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: v1.40.6 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- >Comment By: Allin Cottrell (allin) Date: 2008-02-13 20:34 Message: Logged In: YES user_id=4856 I've now tried using a much simpler map file, but that didn't help. Here what strace says, at the end of reading the map file: read(7, "wncysc10.pfb\nwncyss10 <wncyss10."..., 4096) = 783 read(7, "", 4096) = 0 close(7) = 0 munmap(0xb7fdc000, 4096) = 0 write(1, "}", 1}) = 1 brk(0x835e000) = 0x835e000 brk(0x838e000) = 0x838e000 write(6, "%PDF-1.4\n%\320\324\305\330\n3 0 obj <<\n/Lengt"..., 156) = 156 write(2, "pdflatex: ", 10pdflatex: ) = 10 write(2, "Invalid argument\n", 17Invalid argument ) = 17 write(5, "\relax \n", 8) = 8 write(4, "This is pdfTeX, Version 3.141592"..., 1511) = 1511 exit_group(1) = ? ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-13 19:40 Message: Logged In: YES user_id=4856 Minimal test file and log from pdftex 1.40.5 are added below. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-13 19:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-13 18:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: v1.40.6 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- Comment By: Allin Cottrell (allin) Date: 2008-02-13 19:40 Message: Logged In: YES user_id=4856 Minimal test file and log from pdftex 1.40.5 are added below. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-13 19:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-13 18:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: v1.40.6 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- >Comment By: Allin Cottrell (allin) Date: 2008-02-13 19:40 Message: Logged In: YES user_id=4856 Minimal test file and log from pdftex 1.40.5 are added below. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-02-13 19:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-14 00:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None >Group: v1.40.6 Status: Open >Resolution: Works For Me Priority: 5 Submitted By: Allin Cottrell (allin) >Assigned to: Martin Schröder (oneiros) >Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-02-14 01:13 Message: Logged In: YES user_id=421 I can't reproduce this; I can compile sample2e.tex with this map file. Please attach a (minimal) test file. Also the log of 1.40.5 for this file would be helpful. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

[ pdftex-Bugs-917 ] pdftex 1.40.6: "invalid argument" on parsing pdftex.map
by noreply＠sarovar.org 14 Feb '08

14 Feb '08

Bugs item #917, was opened at 2008-02-13 18:55 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Allin Cottrell (allin) Assigned to: Nobody (None) Summary: pdftex 1.40.6: "invalid argument" on parsing pdftex.map Initial Comment: Using an admittedly quite old pdftex.map, pdftex 1.40.5 would product correct output but pdftex 1.40.6 fails to parse the map file. pdftex.map is attached; here is interactive output: waverley:~/mytex/misc$ cat bug.tex \documentclass{article} \begin{document} Hello. \end{document} waverley:~/mytex/misc$ pdflatex bug This is pdfTeX, Version 3.141592-1.40.6 (Web2C 7.5.6) \write18 enabled. (./bug.tex LaTeX2e <2003/12/01> Babel <v3.7h> and hyphenation patterns for american, russian, spanish, italian, polish, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (./bug.aux) [1{/usr/share/texmf/f onts/map/pdftex.map}pdflatex: Invalid argument ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=917&group_id=106

1 0

Synchronization
by LAURENS Jérôme 12 Feb '08

12 Feb '08

Hi, I'd like to know the opinion of the developer team about synchronization and the patch I sent. Now that xpdf allows both forwards and backwords synchronization, it might be time to raise the question. JL

6 28

[ pdftex-Patches-871 ] Synchronization: pdfsync.sty embedded (1)
by noreply＠sarovar.org 09 Feb '08

09 Feb '08

Patches item #871, was opened at 2007-09-30 10:56 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=871&group_id=106 Category: User interaction >Group: v1.50.0 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Jerome LAURENS (jlaurens) Assigned to: Martin Schröder (oneiros) Summary: Synchronization: pdfsync.sty embedded (1) Initial Comment: To the administrator, please remove the preceding patch submission The purpose is to implement some extensions very useful for synchronization, both forwards and backwards. Synchronization is the ability for a text editor and a pdf viewer to work together, displaying the same thing at the same time. For example, a text editor can ask a pdf viewer to display and outline the character in the output corresponding to the character under the cursor. Attached is a zip file containing diff against version 1.40.4, explanations and demonstrations in synchronize.readme/synchronize+frames.pdf PS: I have problems with my connection ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2008-01-29 10:40 Message: Logged In: NO The pdfsync package is a tremendous boost in the productivity for everyone that learns about it, specially when working with pdf files of more than a couple of pages. The synchronization between pdf viewer and tex editor is essential for keeping track of the changes you are doing without having to search over lots of .tex files or having to scroll over the entire pdf to find the relevant section. My work on latex is mainly done on Mac OS X using eclipse+texlipse+pdftex and the Skim PDF reader and with my discovery of pdfsync, the whole experience of writting latex documents have improved to the point i would not use anything else. So i would love to have this feature included as soon as possible so it can become a standard and avoid any package incompatibilities. Also, it is well known that the syncrhonization feature has been present a very long time for latex output to .dvi files and i think it is the time to bring this essential feature to the pdftex world to achieve the same level of functionality. Regards, Juan Ramón González, Granada, Spain ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2008-01-28 10:50 Message: Logged In: NO I understand the issue correctly, Laurens' suggested modification of pdftex would make synchronization a (potential) standard in all TeX installations and formats, without package incompatibilities. This should be regarded as an improvement over present implementations of this essential feature, at least essential for those who, like Schremmer, spend hours each day going back and forth between TeX source and pdf output. Please add it soon, Josep Maria Font Barcelona ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2008-01-26 06:23 Message: Logged In: NO As someone who spends hours everyday going back and forth between source and pdf with TeXShop under OSX 10.4.11, any improvement in the synchronization would be invaluable and so would Laurens's improvement. Regards --Schremmer ---------------------------------------------------------------------- Comment By: Jerome LAURENS (jlaurens) Date: 2008-01-24 19:31 Message: Logged In: YES user_id=4698 Ok, I found some time to make the necessary corrections and improvements. The attached file contains explanations and examples about synchronization. The patch.diff file is the result of the "svn diff" command against the latest trunk (as of 01/24/08) Compared to the previous versions, the command line switch now works properly and there is now a mean to take into account the x and y offset that may be used by a postprocessor like dvipdf. Well, it is very difficult to find any kind of information/help about pdftex development, so please don't be too crude with me. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-12-19 17:21 Message: Logged In: YES user_id=2217 Also, the command line switch seems to be broken. It only works with \synchronize=1 in the source here. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-12-18 15:50 Message: Logged In: YES user_id=421 Please update the patch against trunk and please use svn diff. I refuse to look at this patch more closely since the diff includes all the .svn files. ---------------------------------------------------------------------- Comment By: Jerome LAURENS (jlaurens) Date: 2007-10-15 09:21 Message: Logged In: YES user_id=4698 Synchronize3.zip is available. It just adds a flag in the .sync file to indicate whether dvi or pdf mode was used. So far I have found only one problem, using dvips or dvipdf with a concrete offset (-x and -y options) will break the synchronization. If such a filter is gentle enough to indicate that it used a custom offset, then viewers can take this into account and the synchronization is not broken. Viewers will check the above mentionned flag to look for customized offset. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-01 00:00 Message: Logged In: YES user_id=421 You didn't attach Synchronize 2.zip yet... ---------------------------------------------------------------------- Comment By: Jerome LAURENS (jlaurens) Date: 2007-09-30 23:10 Message: Logged In: YES user_id=4698 Synchronize 2.zip is a version extending the previous one. Now synchronization works the same for both dvi and pdf output modes. ---------------------------------------------------------------------- Comment By: Jerome LAURENS (jlaurens) Date: 2007-09-30 23:09 Message: Logged In: YES user_id=4698 Synchronize 2.zip is a version extending the previous one. Now synchronization works the same for both dvi and pdf output modes. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=871&group_id=106

1 0

[ pdftex-Bugs-909 ] pdflatex does not respond, probably hitting an endless loop condition
by noreply＠sarovar.org 04 Feb '08

04 Feb '08

Bugs item #909, was opened at 2008-01-26 13:27 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=909&group_id=106 Category: None Group: v1.40.3 >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Jorgen Moth (unijm) Assigned to: Nobody (None) Summary: pdflatex does not respond, probably hitting an endless loop condition Initial Comment: A number of students at the Danish Technical University has experienced pdflatex being captured in an internal endless, cpu-consuming loop. Typically the students utilize texmaker (who submits pdflatex jobs with default option -interaction=nonstopmode) to generate their reports. Due to errors in the input latex files not being corrected immediately by the students, this way of working stresses the pdflatex engine, and a number of looping conditions have occured. Enclosed please find an example of a setup which is able to reproduce the looping error. The error will appear by running "pdflatex report" and answer with an empty line (CR) when a figure can't be located and otherwise with "R" when an error appears, thus emulating the -interaction=nonstopmode used by texmaker. You quickly reach the no-response, but very cpu-time consuming condition. It is our hope that you will easily with your knowledge of the internals of pdflatex locate and fix this very annoying problem. Best regards Jorgen Moth jorgen.moth(a)uni-c.dk (www.uni-c.dk) ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-01-26 17:37 Message: Logged In: YES user_id=421 Please provide a minimal self contained test case proving that this is indeed a problem of pdftex. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=909&group_id=106

1 0

[ pdftex-Bugs-908 ] corrupted SMask
by noreply＠sarovar.org 04 Feb '08

04 Feb '08

Bugs item #908, was opened at 2008-01-26 11:04 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=908&group_id=106 Category: Image inclusion Group: v1.40.6 >Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Robert (schlcht) Assigned to: Martin Schröder (oneiros) Summary: corrupted SMask Initial Comment: if an image with transparency is included, its SMask will contain funny stuff. with the attached image, for example, parts of the map file will be written to the pdf file (don't open it in a viewer but an editor!). \pdfcompresslevel0 \pdfximage{transp.png} \pdfrefximage\pdflastximage \bye ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-01-28 13:47 Message: Logged In: YES user_id=421 Iff you are using Cygwin, then of course Cygwin ist the problem. :-) ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2008-01-28 13:34 Message: Logged In: YES user_id=2217 Here's the PDF I get (with 1.40.6 as well as 1.50). The SMask object looks like this: ----------------------- 8 0 obj << /Type /XObject /Subtype /Image /Width 100 /Height 100 /BitsPerComponent 8 /ColorSpace /DeviceGray /Length 20000 >> stream [10,000 chars]orunska-Regular " encantt-texnansi ReEncodeFont " <antt-texnansi.enc <anttr.pfb texnansi-anttrcap AntykwaTorunska-Regular " encanttcap-texnansi ReEncodeFont " <anttcap-texnansi.enc <anttr.pfb texnansi-anttri AntykwaTorunska-Italic " encantt-texnansi ReEncodeFont " <antt-texnansi.enc <anttri.pfb texnansi-anttricap AntykwaTorunska-Italic " encanttcap-texnansi ReEncodeFont " <anttcap-texnansi.enc <anttri.pfb [etc., until length of 20,000 is reached] ----------------------- cygwin, again? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-01-26 17:35 Message: Logged In: YES user_id=421 I can't reproduce this with either 1.40.5, 1.40.6-rc1, trunk or stable. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=908&group_id=106

1 0

[ pdftex-Patches-871 ] Synchronization: pdfsync.sty embedded (1)
by noreply＠sarovar.org 29 Jan '08

29 Jan '08

Patches item #871, was opened at 2007-09-30 14:26 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=871&group_id=106 Category: User interaction Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Jerome LAURENS (jlaurens) Assigned to: Martin Schröder (oneiros) Summary: Synchronization: pdfsync.sty embedded (1) Initial Comment: To the administrator, please remove the preceding patch submission The purpose is to implement some extensions very useful for synchronization, both forwards and backwards. Synchronization is the ability for a text editor and a pdf viewer to work together, displaying the same thing at the same time. For example, a text editor can ask a pdf viewer to display and outline the character in the output corresponding to the character under the cursor. Attached is a zip file containing diff against version 1.40.4, explanations and demonstrations in synchronize.readme/synchronize+frames.pdf PS: I have problems with my connection ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2008-01-29 15:10 Message: Logged In: NO The pdfsync package is a tremendous boost in the productivity for everyone that learns about it, specially when working with pdf files of more than a couple of pages. The synchronization between pdf viewer and tex editor is essential for keeping track of the changes you are doing without having to search over lots of .tex files or having to scroll over the entire pdf to find the relevant section. My work on latex is mainly done on Mac OS X using eclipse+texlipse+pdftex and the Skim PDF reader and with my discovery of pdfsync, the whole experience of writting latex documents have improved to the point i would not use anything else. So i would love to have this feature included as soon as possible so it can become a standard and avoid any package incompatibilities. Also, it is well known that the syncrhonization feature has been present a very long time for latex output to .dvi files and i think it is the time to bring this essential feature to the pdftex world to achieve the same level of functionality. Regards, Juan Ramón González, Granada, Spain ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2008-01-28 15:20 Message: Logged In: NO I understand the issue correctly, Laurens' suggested modification of pdftex would make synchronization a (potential) standard in all TeX installations and formats, without package incompatibilities. This should be regarded as an improvement over present implementations of this essential feature, at least essential for those who, like Schremmer, spend hours each day going back and forth between TeX source and pdf output. Please add it soon, Josep Maria Font Barcelona ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2008-01-26 10:53 Message: Logged In: NO As someone who spends hours everyday going back and forth between source and pdf with TeXShop under OSX 10.4.11, any improvement in the synchronization would be invaluable and so would Laurens's improvement. Regards --Schremmer ---------------------------------------------------------------------- Comment By: Jerome LAURENS (jlaurens) Date: 2008-01-25 00:01 Message: Logged In: YES user_id=4698 Ok, I found some time to make the necessary corrections and improvements. The attached file contains explanations and examples about synchronization. The patch.diff file is the result of the "svn diff" command against the latest trunk (as of 01/24/08) Compared to the previous versions, the command line switch now works properly and there is now a mean to take into account the x and y offset that may be used by a postprocessor like dvipdf. Well, it is very difficult to find any kind of information/help about pdftex development, so please don't be too crude with me. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-12-19 21:51 Message: Logged In: YES user_id=2217 Also, the command line switch seems to be broken. It only works with \synchronize=1 in the source here. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-12-18 20:20 Message: Logged In: YES user_id=421 Please update the patch against trunk and please use svn diff. I refuse to look at this patch more closely since the diff includes all the .svn files. ---------------------------------------------------------------------- Comment By: Jerome LAURENS (jlaurens) Date: 2007-10-15 12:51 Message: Logged In: YES user_id=4698 Synchronize3.zip is available. It just adds a flag in the .sync file to indicate whether dvi or pdf mode was used. So far I have found only one problem, using dvips or dvipdf with a concrete offset (-x and -y options) will break the synchronization. If such a filter is gentle enough to indicate that it used a custom offset, then viewers can take this into account and the synchronization is not broken. Viewers will check the above mentionned flag to look for customized offset. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-10-01 03:30 Message: Logged In: YES user_id=421 You didn't attach Synchronize 2.zip yet... ---------------------------------------------------------------------- Comment By: Jerome LAURENS (jlaurens) Date: 2007-10-01 02:40 Message: Logged In: YES user_id=4698 Synchronize 2.zip is a version extending the previous one. Now synchronization works the same for both dvi and pdf output modes. ---------------------------------------------------------------------- Comment By: Jerome LAURENS (jlaurens) Date: 2007-10-01 02:39 Message: Logged In: YES user_id=4698 Synchronize 2.zip is a version extending the previous one. Now synchronization works the same for both dvi and pdf output modes. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=871&group_id=106

1 0