From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: question for the xml-experts
Date: Sun, 15 Feb 2009 18:17:54 +0100 [thread overview]
Message-ID: <B9B2431E-BC4B-4633-9CDA-7DBD87E1D9C4@uni-bonn.de> (raw)
In-Reply-To: <fe8d59da0902150139r10075c3al39d3f0838e2b4c11@mail.gmail.com>
Luigi and Khaled,
thanks a lot for your replies! Luigi: I had a look at python lxml; it
looks very powerful and interesting, and I will try and see if can
make use of it. Why do you translate your xml sources into tex instead
of using the mkiv mechanism for processing xml, is it because of speed?
Khaled: I have to see if I can tweak the OpenOffice docbook converter
to keep more of the formatting; in its default state, it drops too
much important stuff...
Right now, I have followed Patrick's advice. I've installed saxon9 and
am writing a xslt stylesheet to translate the openoffice xml into a
cleaner and easier to handle format. I'm making progress... Maybe we
should put something like this on the wiki and make it a collaborative
effort - I can only write rules for stuff that occurs in my documents,
and that is of course only a subset of what OpenOffice has, so it
would be good to add rules as people find interesting features.
All best
Thomas
On Feb 15, 2009, at 10:39 AM, luigi scarso wrote:
> If you know python
> http://wiki.services.openoffice.org/wiki/PyUNO_bridge
> http://opendocumentfellowship.com/projects/odfpy
> For xml the choice is
> http://codespeak.net/lxml/
>
> A native xml db, with XQuery and python binding
> http://www.oracle.com/technology/products/berkeley-db/xml/index.html
>
>
>
> And this is my experience :
> I'm programming in TeX (with context) , lua / python (they are
> similar) and xslt .
> For every project if I can I use lxml to manage xml sources, because
> it includes xslt but not viceversa.
> The goal is to translate xml in tex in the quickest way, and let mkiv
> to do the hard word.
> I have not a good feeling with xslt, because is not so powerful as
> lxml, and clearly is not a competitor of TeX .
>
> If I need storage, dbxml is good, and XQuery+lxml is powerful
> enought .
>
> OO has also docbook exporter
> http://www.docbook.org/
> docbook
> is rich and with a good collection of xsl stylesheets to translate
> xml to html
> but maybe is ...too much .
>
> --
> luigi
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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 prev parent reply other threads:[~2009-02-15 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 17:40 Thomas A. Schmitz
2009-02-14 18:25 ` Wolfgang Schuster
2009-02-14 18:37 ` Thomas A. Schmitz
2009-02-15 9:39 ` luigi scarso
2009-02-15 17:17 ` Thomas A. Schmitz [this message]
2009-02-17 22:07 ` luigi scarso
2009-02-19 8:54 ` Thomas A. Schmitz
2009-02-19 9:24 ` luigi scarso
2009-02-19 10:39 ` luigi scarso
2009-02-19 11:53 ` Thomas A. Schmitz
2009-02-19 14:10 ` luigi scarso
2009-02-20 15:09 ` Thomas A. Schmitz
2009-02-20 15:35 ` luigi scarso
2009-02-19 17:02 ` luigi scarso
2009-02-14 18:31 ` Patrick Gundlach
2009-02-14 19:06 ` Thomas A. Schmitz
2009-02-15 10:14 ` Khaled Hosny
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=B9B2431E-BC4B-4633-9CDA-7DBD87E1D9C4@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).