From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: ConTeXt -> LaTeXt -> ODT?
Date: Tue, 19 Jul 2011 12:45:06 +0200 [thread overview]
Message-ID: <4E256032.40803@wxs.nl> (raw)
In-Reply-To: <CALBOmsajZkt9bS7UpCff-FSkgdjhqQZD+s=Jp-hwe3QapVU+bg@mail.gmail.com>
On 19-7-2011 12:15, Mojca Miklavec wrote:
> On Tue, Jul 19, 2011 at 11:41, Cecil Westerhof wrote:
>>
>> Okay, I'll discard this option then. (Or someone else must have a way to do
>> the ConTeXt -> LaTeXt part.)
>
> Keep in mind that ConTeXt -> ODT should in theory be doable as well,
> but the author of tex4ht died and it is very unlikely that the
> conversion would work without any problems and even more unlikely that
> anyone would know how to fix it.
>
> If you can throw away any formatting you did and if you didn't use too
> many ConTeXt specific tricks, you can "simply rewrite" your code to
> LaTeX with a few regular expressions etc. But in the same spirit it
> might be way easier to just "convert" the document straight to ODT
> using copy-paste and applying some formatting there.
It also depends on the requirement.
Of a document only has some sectioning, itemize, and tables (and the
majority of the document have) then some simple convertable input format
can do. For more complex documents you end up with either coding in tex
or when multiple output is needed xml is a good choice. When coding in
tex, the xml/xhtml can be of help (and it will evolve) as it provides a
pretty complete structure of the document.
Concerning OTD: if you need to be roundtrip, then you also need to be
able to convert back, which might be non trivial.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-07-19 10:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 8:47 Cecil Westerhof
2011-07-19 8:51 ` Martin Schröder
2011-07-19 9:00 ` Hans Hagen
2011-07-19 9:41 ` Cecil Westerhof
2011-07-19 10:15 ` Mojca Miklavec
2011-07-19 10:24 ` Martin Schröder
2011-07-19 10:35 ` Cecil Westerhof
2011-07-19 10:45 ` Hans Hagen [this message]
2011-07-19 10:50 ` Cecil Westerhof
2011-07-19 10:58 ` Mojca Miklavec
2011-07-19 11:14 ` Cecil Westerhof
2011-07-19 12:58 ` Khaled Hosny
2011-07-19 13:06 ` Hans Hagen
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=4E256032.40803@wxs.nl \
--to=pragma@wxs.nl \
--cc=mojca.miklavec.lists@gmail.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).