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: Re: DocBook in ConTeXt - any new ideas?
Date: Sat, 4 Jun 2011 11:57:55 +0200	[thread overview]
Message-ID: <B5B84DB4-944E-44C7-BD46-6BC33A7E1A2D@hccnet.nl> (raw)
In-Reply-To: <4DE9F5AB.2090500@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 3724 bytes --]


Op 4 jun 2011, om 11:06 heeft Hans Hagen het volgende geschreven:

> On 4-6-2011 10:21, R. Ermers wrote:
> 
>> Adding the prefix cals: to the tag names (thus making the file invalid, which is contrary to the docbook philosophy), using the cals table module and the directives is not enough, at least the cals tables in my valid xml docbook document were never typeset.
> 
> can be any prefix (namespace) ... the code that implements it uses a namespace in order to avoid a mixup
> 
>> With help from Aditya I managed to typeset a document which contains merely a cals table. I then thought this was going to be the first step to processing my xml file which contains a number of tables. But alas ....
>> 
>> The tables in my document were skipped like any other unknown xml tag. I must have done something wrong. But what? There were no replies to my postings. In the end I felt silly for daring to posing a problem other people apparently had no problems with whatsoever.
> 
> well, providing solutions for specific user cases depends on available time etc ... even making a simple example ...
> 
>> So, if you should embark on this track, be aware that typesetting xml is more complicated than a ConTeXt document, that the knowledge about it is not widespread yet, that you rely on the happy few who do know, and it may take a lot of time to find out things yourself.
> 
> sure, and eventually it will be covered by manuals (or test files in the test suite -- actually there are some xml ones in there) ... there's only so much you can expect for a free system so some patience is needed
> 
> ps. although a lot of help can be gotten from this list, the wiki etc, users who want to do complex things (or workflows) cannot expect all their problems to be solved here as we all have jobs to fulfill ... it might help to make wiki pages and let others fill in the gaps
> 

Of course, I agree that typesetting a xml docbook in itself is a complex matter. And yes, I read every single letter of the complex xml manuals.

I also agree that people no doubt have many other things to do, including myself. Anybody working with Context and TeX must bear in mind that his problems will not be solved immediately, that knowledgeable people will voluntarily look into questions and problems, depending on their time and their interest in specific problems.

However, on the other hand since docbook is a very well known and therefore attractive standard, and most problems in xml can be described quite straightforward. As a result the problem of typesetting cals tables cannot be depicted as a 'specific user case'. After all, there is a module cals tables, and it is expected to work.

The problem was: how can I typeset a cals table with a minimal installation? Comparable to: how do I typeset a header? What settings are needed apart from the module? This should not be a 'complex' problem.

My conclusion remains that the knowledge on xml is not widespread, that those who possess the knowledge do not always have time to help, and as a result my problem was not solved.

For the record: note that my problem was not of the type: how to discard the nth line of a cals table? How to color the header of a cals table? Or how to only typeset cals tables with id="abc".

Robert


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


[-- Attachment #1.2: Type: text/html, Size: 5110 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2011-06-04  9:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02  9:39 Piotr Kopszak
2011-06-02 10:20 ` Thomas Schmitz
2011-06-02 10:53   ` Piotr Kopszak
2011-06-02 12:03     ` Hans Hagen
2011-06-02 17:17       ` Bruce
2011-06-02 20:20         ` Hans Hagen
2011-06-03 15:43           ` R. Ermers
2011-06-03 16:28             ` Hans Hagen
2011-06-04  8:21               ` R. Ermers
2011-06-04  9:06                 ` Hans Hagen
2011-06-04  9:57                   ` R. Ermers [this message]
2011-06-04 12:24                   ` Aditya Mahajan
2011-06-04 13:25                     ` R. Ermers
2011-06-05 10:46                     ` Hans Hagen
2011-06-02 11:58 ` 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=B5B84DB4-944E-44C7-BD46-6BC33A7E1A2D@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).