-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xmlto pdf fails (Fedora) #40
Comments
that's odd your log shows
then I don't have the xmlto script, could you add the generated tex from the xml, and I'll debug... |
It doesn't seem like xmlto ever spits out the generated tex in a sane way. I've attached the log that it does generate when I run it with "--noclean". |
oh! xmltex:-)
OK so it never writes out normal tex syntax it gets tex to read the xml
directly (using a parser I wrote in my youth:(
I'd never recommend xmltex these days but I'll see if I can recreate the
issue.
if you can give me the xsl FO XML file that is generated and given to tex
that would help, as I could run passivetex on that but do't worry if not, I
can probably find a copy of xmlto to test...
…On 4 June 2018 at 16:02, Tom Callaway ***@***.***> wrote:
It doesn't seem like xmlto ever spits out the generated tex in a sane way.
I've attached the log that it does generate when I run it with "--noclean".
tmp.log <https://github.com/ho-tex/oberdiek/files/2068781/tmp.log>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#40 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABNcAtfvzYb5jw7mngohjp1YRIYha2mkks5t5UwCgaJpZM4UZKkA>
.
|
tmp.fo.txt |
This bug has been open in Fedora for several years (see: https://bugzilla.redhat.com/show_bug.cgi?id=949087). Here's how to reproduce it:
Run:
xmlto --skip-validation pdf mini.xml
Watch it fail:
Other data points:
xmlto --skip-validation --with-fop pdf mini.xml
works fine.In the Fedora bug report, it was noticed that commenting out lines 451-456 from epstopdf-base.sty works around this problem, but I am not sure that this fix is valid:
The text was updated successfully, but these errors were encountered: