From: Paul Tremblay <phthenry@iglou.com>
Subject: Re: Re: page on context and XML has moved
Date: Tue, 5 Apr 2005 11:45:43 -0400 [thread overview]
Message-ID: <20050405154543.GA23300@localhost.localdomain> (raw)
In-Reply-To: <20050405085144.GG9871@mnw.art.pl>
On Tue, Apr 05, 2005 at 10:51:44AM +0200, Piotr Kopszak wrote:
>
> That's very promising indeed. Right now I'm transforming my original
> xml using xslt to a simpler xml file which can be processed in
> document order to make the ConTeXt file containing xml formatting
> commands as simple as possible. It would be nice to end up with an xml
> file which would contain all the formatting information and make the
> ConTeXt file unnecessary. But I'm afraid of two things:
>
> 1. XSLT transformations will get so complex I will get lost in the
> stylesheet at some point.
>
> 2. How the final finetuning of the appearence of the typeset version
> should be done? Surely not by fiddling in the xml file which should
> be generated by xslt (or whatever) and I'm not sure making changes
> in the xslt stylesheet to make some pages one line shorter or
> longer is the way to go.
>
Hi Piotr,
First, if you use TeXML, make sure you download the latest version,
1.25-devel. This version is very stable and robust, and has the
texml_con script, which converts directly from XML to PDF or whatever
format you require:
texml_con <any option you can use with texexec> infile
It will create a ConTeX file along the way, as its first step. So if
your file is modern_photo.xml, a file called modern_photo.tex will be
created. You could open the modern_photo.tex file and make small changes
on that file. However, if you need to do this, you should instead type:
texml.py -e -c modern_photo.xml modern_photo.tex
That will create a ConTeXt file, which you can then alter.
Of course, having to alter the ConTeXt file defeats the purpose of XML.
You should be able to convert directly from XML to PDF. What alterations
do you think you will have to make?
I know XSLT stylesheets can get very complicated. This is often the
case, including when I convert XML to HTML. You could try converting in
steps, making a small manageble change on one document, and then making
a small manageable change and so on.
Let me know your results. Good luck!
Paul
--
************************
*Paul Tremblay *
*phthenry@iglou.com *
************************
next prev parent reply other threads:[~2005-04-05 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 2:24 Paul Tremblay
2005-04-03 8:13 ` Patrick Gundlach
2005-04-03 9:41 ` Paul Tremblay
2005-04-03 12:10 ` Maurice Diamantini
2005-04-03 19:36 ` h h extern
2005-04-04 7:26 ` Maurice Diamantini
2005-04-03 21:03 ` Patrick Gundlach
2005-04-03 22:05 ` Paul Tremblay
2005-04-04 12:31 ` Piotr Kopszak
2005-04-04 17:09 ` Paul Tremblay
2005-04-05 8:51 ` Piotr Kopszak
2005-04-05 15:45 ` Paul Tremblay [this message]
2005-04-06 9:50 ` Piotr Kopszak
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=20050405154543.GA23300@localhost.localdomain \
--to=phthenry@iglou.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).