ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christopher Creutzig <christopher@creutzig.de>
Subject: Re: ConTeXt to RTF Conversion
Date: Fri, 23 Sep 2005 22:13:45 +0200	[thread overview]
Message-ID: <433461F9.8030205@creutzig.de> (raw)
In-Reply-To: <opsxkkadw1u9mfh0@lamar.colostate.edu>

Idris Samawi Hamid wrote:
> Would it be possible to define an xml format for the journal so that I
> could more easily process both ConTeXt/LaTeX articles as well as the
> docs and rtfs I generally receive? Is this more work than it's worth?
> It's a humanities journal, so little-to-no math.

 Math is, in my experience, the worst part of it, so you an consider
yourself happy that you don't need it.

 The question is, what problems of the current process are you trying to
improve/solve with a possible move to xml?

 If your most pressing problem is the variety of data formats you
receive articles in, then no, xml won't help.  You'd still need some way
of transforming the articles to the format of your choice.  That being
said, XML may be a very good intermediate step from Word or rtf to
ConTeXt, if only because OpenOffice has pretty advanced import filters
and stores its data in a straightforward xml format that should be easy
to transform, assuming you start with a sufficiently rich set of
predefined formats and somehow get people to either use them (fat
chance, I know) or have them be sufficiently different that you can
automatically or at least semi-automatically classify the author's
formatting to your presets.  In really simple cases (e.g., pure prose)
you may get away with accepting HTML and converting that.

 If your most serious problem is a variety of output formats you want to
support (print/pdf, html, some eBook variants, ...), xml is a perfect
technique to develop a solution.

 If getting lots of different encodings is a problem of yours, xml
solves that nicely as well.  But just for that, there are simpler and
less intrusive ways.


 Other things xml may solve well:

- archivability (although your ConTeXt files are probably no worse)

- reusability: Almost everything in a file following a well-designed
  xml format is local and you can simply copy a (complete) block of
  text + markup and insert it into another file.

- consistency, enforcing rules: While it is possible to enforce things
  like “every article must start with an abstract containing one to
  three paragraphs” in TeX, it is way easier in xml.

- all sorts of conversions, including shuffling around or extracting
  data of interest


 Things xml won't do any magic for:

- layout.  You'd need to write a conversion to ConTeXt or whatever.
  Depending on your needs, this can be anything from trivial (say,
  two hours) to almost undoable (although this would mean the xml
  format is particularly badly designed for your journal).


 Both lists are certainly incomplete.  I hope you will get other answers
as well.


regards,
	Christopher

  reply	other threads:[~2005-09-23 20:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050922100002.E15A2127F0@ronja.ntg.nl>
2005-09-22 10:23 ` Duncan Hothersall
2005-09-22 16:51   ` Maurice Diamantini
2005-09-22 20:54     ` Christopher Creutzig
2005-09-23 18:57       ` Idris Samawi Hamid
2005-09-23 20:13         ` Christopher Creutzig [this message]
2005-09-21 16:12 Idris Samawi Hamid
  -- strict thread matches above, loose matches on Subject: below --
2005-09-21 15:12 Louis F.Springer
2005-09-21 15:31 ` andrea valle
2005-09-21 15:58   ` Pr. Erich Fickel
2005-09-21 21:23     ` andrea valle
2005-09-21 20:09 ` Mojca Miklavec
2005-09-21 20:19   ` Adam Lindsay

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=433461F9.8030205@creutzig.de \
    --to=christopher@creutzig.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).