You are not logged in.
Pages: 1
Hi guys!
I'm having a slight problem with Texmacs's (from the extra repo) PDF output.
When I'm trying to export PDF, everything seems to be fine, Texmacs says nothing with debug enabled, but :
- I get a 1.2 MB file, even for 3 lines of text, which seems a little big
- Evince complains about some kind of missing "Xref table" before opening the file, which I understand to be a PDF content table
- Neither GMail nor Acrobat Reader (which some folks at my college use) are able to open the file
- I recently switched from Ubuntu, and the previous PDFs outputs from there are fine. I even tested with an old texmacs file. Ubuntu version : 34KB and fine; Arch version : 1.2MB and Xref missing.
I tried Lyx, but it doesn't work as well for my purposes, so I'd like to stick to Texmacs.
Does someone know a way to fix this?
Thanks a million!
Evince output :
$ evince Fichier.pdf
Error: May not be a PDF file (continuing anyway)
Error: PDF file is damaged - attempting to reconstruct xref table...
Error: Couldn't find trailer dictionary
Error: Couldn't read xref tableTexMacs version :
$ texmacs -v
TeXmacs version 1.0.7.7
(c) 1999-2006 by Joris van der HoevenOffline
I have the exact same problem in Ubuntu. I know this is an ArchLinux forum, but I figured idenfifying that the problem is not distro-dependent could be useful.
As with the OP, the PDF files I've been creating with TeXmacs can't be displayed, neither by the Acrobat Reader nor by Google Docs (it marks them as corrupt). Evince *can* display as well, but with the same errors.
Whatever Evince is doing, it manages to display the file correctly. So the workaround I've been using is to open the file in Evince, then open up the Print dialog and use the "Print to file" option. This produces a valid PDF file. I suppose one could use a terminal pdf converter to do this in batch if needed. But it's still a very annoying problem.
May I add that this problem started relatively recently (~1 year ago), though I can't really pinpoint the exact date. It used to work just fine before (I've been using Ubuntu all along). I don't know if it was due to a TeXmacs update, or an update of some of its dependencies (gs or whatever is used to produce the PDF file?).
Anyway, I'm not sure this is the correct place to post this (the TeXmacs dev mailing list seems a better option) but I thought confirming this "bug" here could be of some help.
I'm running Ubuntu 10.04 LTS, Kernel is 2.6.32, TeXmacs is 1.0.7.3, gs is 8.71.
Last edited by Meithan (2011-05-31 20:37:03)
Offline
Thanks for the reply, at least I'm not alone
I totally forgot about this post since I've posted it, though.
Since then, I discovered that, as it turns out, TeXmacs actually produces PostScript files, even while labelling them as PDF.
I'm not willing to dive into TeXmacs code at the moment, as I'm not using it frequently enough for it to be worth my time. The workaround I'm currently using is to only output to PostScript, and then run the ps2pdf command (found in the ghostscript package on Arch) on the generated .ps file.
Last edited by frix (2011-05-31 21:24:38)
Offline
Well,I'm having a new problem with TeXmacs and evince. After I produce a pdf file directly from TeXmacs, GV and xpdf do well with it. But when evince opens the pdf file, it doesn't show anything. If I produce a ps file, GV and evince works fine (xpdf does not support ps), but after I convert it to pdf with ps2pdf, GV and xpdf are ok, evince doesn't show anything. However, evince's preview is not blank.
Offline
Uh, sounds weird but I recently heard about another similar case on the TeXmacs mailing list (see http://comments.gmane.org/gmane.editors … user/8899).
Can you run TeXmacs on the command line with the -debug switch and see what happens?
Last edited by frix (2012-10-21 09:08:16)
Offline
Pages: 1