ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Schmitz Thomas A." <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: E-books and XML.
Date: Wed, 27 Aug 2014 18:15:36 +0200	[thread overview]
Message-ID: <BA2FF76E-7833-4AFA-BC47-78D44116655A@uni-bonn.de> (raw)
In-Reply-To: <20140827103834.11575840@localb.wexfordpress.net>


On 27 Aug 2014, at 16:38, john Culleton <John@wexfordpress.com> wrote:

> Some questions:
> What tool do you recommend for entering text etc.
> in XML format? I have the Bluefish Editor but
> usually code html in a plain editor (Gvim).

“Recommend” is too strong, because everything depends on the type of document you’re working on. I mainly use emacs + nxml mode. It validates on the fly, if your document is well defined, you can make it validate against a relax-ng scheme. To me, this is sufficient. I know that many serious users of nxml swear by oxygen. And I wouldn’t be surprised if Hans used his beloved Scite. (As for Lukas’s question: sorry, I don’t do Windows, I have no clue)

> 
> I downloaded the manual "Dealing with XML in
> MKIV" but it presupposes that the user builds his
> own conversion system. And it is "still somewhat
> exerimental." Is there a conversion system already
> in place somewhere?

I have been using it for a number of years now and have found it as stable as the rest of ConTeXt. Every once in a while, a bug will come up, and it will be fixed by Hans.

Have you seen the wiki page about TEI xml and about processing xml with Lua? That should be a good start.

> 
> For the beginner (me) is the MKII method easier
> to implement?

No, I would say both are about equal in complexity, but the mkiv method is so much more powerful and consistent, I really wouldn’t bother with mkii anymore.

One reason for me to use xml: I generate presentations, manuscripts, handouts from the same source (all with context). When I’m not typesetting the book myself, editors usually want some sort of word or libreoffice document. When my input is xml, it is relatively trivial to transform it to valid html and load that into libreoffice. 

Again: much depends on the type of document you’re working on. If every document you write is its own piece of art with numerous font effects and special typesetting needs on every page, I would stay with context syntax. But if your documents have a pretty predictable structure and you don’t expect to be forced to tweak individual page breaks, I would have a very long look at xml. I have grown to like it. If you have ever looked at a tex source document and tried to figure out where the missing brace in your }}}}}}}}}} orgy came from, you will love the tags and their nice nesting.

Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2014-08-27 16:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 15:07 john Culleton
2014-08-26 15:10 ` Wolfgang Schuster
2014-08-26 17:08   ` Henning Hraban Ramm
2014-08-26 17:29     ` Hans Hagen
2014-08-27  7:02       ` Henning Hraban Ramm
2014-08-27  9:05         ` Hans Hagen
2014-08-27  9:25           ` Henning Hraban Ramm
2014-08-27  9:37             ` Hans Hagen
2014-08-27  9:46               ` Henning Hraban Ramm
2014-08-27 10:06                 ` Hans Hagen
2014-08-28  8:10                   ` Henning Hraban Ramm
2014-08-28  8:22                     ` Hans Hagen
2014-08-28 10:54                       ` Henning Hraban Ramm
2014-08-28 13:34                         ` Hans Hagen
2014-08-28 13:35                         ` Hans Hagen
2014-08-28 17:39                         ` Hans Hagen
2014-08-29  6:33                           ` Henning Hraban Ramm
2014-08-29 10:17                             ` Hans Hagen
2014-08-29 11:46                               ` Henning Hraban Ramm
2014-08-29 12:46                                 ` Hans Hagen
2014-08-30  7:56                                   ` Henning Hraban Ramm
     [not found]                                 ` <540AEA44.2080106@wxs.nl>
     [not found]                                   ` <540C26D3.1020101@wxs.nl>
2014-09-13  7:29                                     ` Henning Hraban Ramm
2014-08-27  9:03     ` Henning Hraban Ramm
2014-08-26 18:04 ` Hans Hagen
2014-08-26 18:12   ` Thomas A. Schmitz
2014-08-27 14:03     ` XML as source (was: E-books and XML) Procházka Lukáš Ing. - Pontex s. r. o.
2014-08-27 18:40       ` Jan Tosovsky
2014-08-28 17:02       ` Mica Semrick
2014-08-27 14:38     ` E-books and XML john Culleton
2014-08-27 16:15       ` Schmitz Thomas A. [this message]

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=BA2FF76E-7833-4AFA-BC47-78D44116655A@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).