From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Cc: phthenry@iglou.com
Subject: DOC/RTF to ConTeXt via XML [was: Re: ConTeXt to RTF Conversion]
Date: Mon, 26 Sep 2005 15:31:39 -0600 [thread overview]
Message-ID: <436E5F8C@webmail.colostate.edu> (raw)
Thank you so much, Christopher, for your detailed answer!
>===== Original Message From Christopher Creutzig <christopher@creutzig.de>
=====
>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.
> 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)
fat chance, perhaps, but maybe...(see below)
>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.
Paul Tremblay's pages seem very useful in this regard:
http://getfo.sourceforge.net/context_xml/contents.html
Question: Is it possible to design a doc or rtf template that Open Office can
convert to a sane, consistent xml format? If the Tremblay approach is rich
enough, that would solve a lot of problems! Here is my idea:
1. Give each author a doc/rtf template for formatting their article;
2. Use OpenOffice to convert to xml;
3. Use the Tremblay method (have not tried it yet) to process this in Context.
Question: Does the entire journal have to be in programmed in xml or can
ConTeXt process xml locally? For example, I may have my own article done in
COnTeXt mixed with other articles done in rtf=>xml.
Any other advice (and/or pitfalls to watch for) would be appreciated. This
sounds very promising!
Best
Idris
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-09-26 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 21:31 Idris Samawi Hamid [this message]
2005-09-26 22:30 ` Hans Hagen
2005-09-26 23:10 ` How up-to-date is cont-enp.pdf Alexander Lazic
2005-09-27 7:39 ` Hans Hagen
2005-09-27 8:17 ` Alexander Lazic
2005-09-27 9:22 ` Adam Lindsay
2005-09-27 10:11 ` Alexander Lazic
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=436E5F8C@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--cc=ntg-context@ntg.nl \
--cc=phthenry@iglou.com \
/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).