From: John Culleton <john@wexfordpress.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: XML one more time.
Date: Tue, 14 Jul 2009 15:23:48 -0400 [thread overview]
Message-ID: <200907141523.48482.john@wexfordpress.com> (raw)
I have the xml sources for the Gimp manual. I can't seem to get them
to translate to a pdf. The top xml file just contains a series of
calls to subordinate files. When I run this through Context I get
just the text of the first file in no particular format and none of
the subfiles.
I have tried
texexec --environment=gimp gimp.xml
and
texexec --environment=xml gimp.xml
The Gimp advice is to use dblatex, but that seems to think it is on
a Windows system and generates errors containing code like c:\foo
Now I can hand convert each and every xml statement in each and
every subfile to a TeX equivalent but there should be a shorter
way. There are more than 600 subfiles. Or I can write a program to
do that to either the xml source or the html derivative. But I
hope Context will enable me to do it with less labor.
BTW the html generation works flawlessly following the approved Gimp
script.
--
John Culleton
Create Book Covers with Scribus/e-book $5.95
http://www.booklocker.com/books/4055.html
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@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
___________________________________________________________________________________
next reply other threads:[~2009-07-14 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 19:23 John Culleton [this message]
2009-07-14 20:37 ` Wolfgang Schuster
2009-07-14 21:36 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200907141523.48482.john@wexfordpress.com \
--to=john@wexfordpress.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).