From: Duncan Hothersall <dh@capdm.com>
Subject: Re: DOC/RTF to ConTeXt via XML
Date: Tue, 27 Sep 2005 11:24:15 +0100 [thread overview]
Message-ID: <43391DCF.1010805@capdm.com> (raw)
In-Reply-To: <20050927100004.7F435127E5@ronja.ntg.nl>
Slightly OT, sorry:
>>OpenOffice.org does allow you to attach an XSLT stylesheet to an export
>>process which therefore allows you to do a (limited) transformation from
>>the visual markup which is its native format to a more structured one
>
> Why „limited“?
Well, XSLT seems to have been designed, and certainly tends to be
implemented, as a tool for simple transformations of small XML chunks.
Obviously complex transformations can be constructed from a bunch of
simple transformations, but there comes a point when you should really
just use a better tool - though these tend to cost serious money (e.g.
OmniMark). Also, most XSLT implementations use the DOM model, which is
fine for a 50Kb file but will be incredibly resource-hungry if you're
processing files of 5Mb. At that point you want a streaming model, and
for a streaming model you want a better suited language than XSLT. As I
say, horses for courses. For article-length pieces and simple
transforms, XSLT might suffice.
> Also, don't limit your authors to Word. Offering Word is obviously a
> requirement, but if you go the way through OOo, there would be no point
> in not offering an OOo template file. If you are using a standard xml
> format, such as (a subset of) DocBook or TEI, you probably should accept
> articles in that format, too. And, of course, ConTeXt.
Absolutely; particularly if you can offer authors an incentive or direct
benefit from adopting OO.o, such as speed of turnaround of proofs, etc.
next parent reply other threads:[~2005-09-27 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050927100004.7F435127E5@ronja.ntg.nl>
2005-09-27 10:24 ` Duncan Hothersall [this message]
2005-09-27 13:42 ` Christopher Creutzig
[not found] <20050928080211.5A0EB127F8@ronja.ntg.nl>
2005-09-28 8:54 ` Duncan Hothersall
2005-09-28 11:45 ` Christopher Creutzig
2005-09-27 15:10 Idris Samawi Hamid
2005-09-27 15:19 ` Adam Lindsay
2005-09-28 7:08 ` Christopher Creutzig
-- strict thread matches above, loose matches on Subject: below --
2005-09-27 14:50 Idris Samawi Hamid
2005-09-28 8:02 ` Christopher Creutzig
[not found] <20050927074229.9EF85127E2@ronja.ntg.nl>
2005-09-27 8:05 ` Duncan Hothersall
2005-09-27 9:03 ` Christopher Creutzig
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=43391DCF.1010805@capdm.com \
--to=dh@capdm.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).