On Feb 19, 2009, at 3:10 PM, luigi scarso wrote:
see
http://codespeak.net/lxml/tutorial.html#namespaces
Luigi,
thanks so much for your patient replies. I have now begun to play with
python's lxml. It offers a lot, maybe too much for a beginner. One
advantage for my immediate needs that
On Fri, Feb 20, 2009 at 4:09 PM, Thomas A. Schmitz
thomas.schm...@uni-bonn.de wrote:
On Feb 19, 2009, at 3:10 PM, luigi scarso wrote:
see
http://codespeak.net/lxml/tutorial.html#namespaces
Luigi,
thanks so much for your patient replies. I have now begun to play with
python's lxml. It
Yes, you're right of course.
I have a similar situation here: the xml
produced by ooo is too messy, so I want to preprocess it to something that
is easier to maintain and modify (e.g., I will, at some point, add index
entries and a TOC); that's why I use xslt here. But I still produce xml
On Thu, Feb 19, 2009 at 9:54 AM, Thomas A. Schmitz
thomas.schm...@uni-bonn.de wrote:
On Feb 17, 2009, at 11:07 PM, luigi scarso wrote:
(sorry x my laziness)
If I have a good xml , then mkiv is a good choice. As far I know, mkiv
~ xslt by lpeg, so
traditional
xml--( xslt )--tex--( mkiv
On Feb 19, 2009, at 11:39 AM, luigi scarso wrote:
FOO = etree.Element(FOO)
emph = etree.Element(emph)
[child.tag for child in foo.iterdescendants(tag = '{urn:oasis:names:tc:opendocument:xmlns:text:1.0
}span' ) ]
['{urn:oasis:names:tc:opendocument:xmlns:text:1.0}span']
span = [child for
Yes, you're right of course. I have a similar situation here: the xml
produced by ooo is too messy, so I want to preprocess it to something that
is easier to maintain and modify (e.g., I will, at some point, add index
entries and a TOC); that's why I use xslt here. But I still produce xml
On Sun, Feb 15, 2009 at 6:17 PM, Thomas A. Schmitz
thomas.schm...@uni-bonn.de wrote:
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
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
You may consider giving dbcontext a look, it is written in python and
seems to use xsl to translate DocBook's xml into TeX files to be typeset
by ConTeXt. http://dblatex.sourceforge.net/doc/pt02.html
Regards,
Khaled
On Sat, Feb 14, 2009 at 06:40:51PM +0100, Thomas A. Schmitz wrote:
Hi all,
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
Hi all,
this is not a question about direct technical details, but more of a
conceptual problem, and I would love to have your input and ideas on
this. I will be editing several edited volumes in my field
(humanities, classics). From experience, I know that it's impossible
to make
Hi Thomas,
why don't you take a look at the OpenOffice export function, I saw it's
possible to convert a document to xhtml and this could be a start for
you.
Wolfgang
Am 14.02.2009 um 18:40 schrieb Thomas A. Schmitz:
Hi all,
this is not a question about direct technical details, but more
Hi Thomas,
process the odt directly; instead, I want to transform the xml via
xslt to a simplified format and then process that with ConTeXt. I have
just discovered the tool xalan (
http://xml.apache.org/xalan-c/index.html ) which allows me to use an
xslt style sheet and direct the output
On Feb 14, 2009, at 7:25 PM, Wolfgang Schuster wrote:
Hi Thomas,
why don't you take a look at the OpenOffice export function, I saw
it's
possible to convert a document to xhtml and this could be a start
for you.
Wolfgang
Hi Wolfgang,
thanks for the suggestion! I had, in fact, tried
On Feb 14, 2009, at 7:31 PM, Patrick Gundlach wrote:
Yes, it does. At my company we clean up (and reorganize) XML data with
XSLT all the time. We are happy users of saxon 9
(http://saxon.sourceforge.net/) which is an xslt 2.0 engine. Learning
XSLT is not trivial (but not too hard either), but
15 matches
Mail list logo
