ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "R. Ermers" <r.ermers@hccnet.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: docbook in context
Date: Mon, 04 Jun 2007 16:14:30 +0200	[thread overview]
Message-ID: <46641E46.9070503@hccnet.nl> (raw)
In-Reply-To: <4663F9B7.5010403@seznam.cz>

Dear All,

After having had a great deal of problems when submitting my context 
files to my publisher, I decided to write future projects in docbook 
(V4.4), rather than switching to Word or Open Office. From the docbook 
files I then can generate an rtf or wml file which is much more of use 
for the publisher, alas.

For me this has the extra advantage of viewing the text in an xml 
editor, such as Xmlmind.

My new docbook document processes well in Context and no errors are 
reported, thanks again Simon and others for this valuable application.

However two major problems have come up.

The first is a problem with Cals tables and figures:
1. After the section containing a table, all section headings in the 
following chapters, sections, subsections, even bridgeheads, until the 
end of the document are omitted, without due error message.

2. Figure titles create an extra section or subsection title. I solved 
this by using <informalfigure> instead and inserting a <caption>. For 
tables using caption is not an option.

A second problem is the language label. In the top level of the tree, I 
add the language label, e.g. <book lang="nl">. In general, and for fo 
processors this is, I believe the right place. Context gives the 
following error message:
\dodosetupsometextprefix ...malist [#3]\docommand
                                                  \else \def \docommand 
##1{...
l.53 \XMLDBheadtext[nl]{figuren}{Figuren}
           
This disappears when the label (lang="nl") is removed. Perhaps I am not 
right in putting the language label in this way, if so, please advise.

I am grateful for any help,

Robert





___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2007-06-04 14:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01  7:42 endlinechar redefinition Vit Zyka
2007-06-02 20:58 ` Hans Hagen
2007-06-04 11:38   ` Vit Zyka
2007-06-04 13:34     ` Hans Hagen
2007-06-04 14:24       ` Vit Zyka
2007-06-04 14:33         ` Hans Hagen
2007-06-04 15:50           ` Vit Zyka
2007-06-04 21:02             ` Hans Hagen
2007-06-04 14:14     ` R. Ermers [this message]
2007-06-04 14:42       ` docbook in context luigi scarso
2007-06-04 14:56         ` context file to publisher (was: docbook in context) R. Ermers
2007-06-04 16:44           ` luigi scarso
2007-06-05  8:18         ` docbook in context R. Ermers
2007-06-07  7:43         ` R. Ermers
2007-06-07  9:23           ` luigi scarso
2007-06-07 10:14             ` R. Ermers
2007-06-07 17:00               ` Aditya Mahajan
2007-06-07 23:29                 ` luigi scarso

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=46641E46.9070503@hccnet.nl \
    --to=r.ermers@hccnet.nl \
    --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).