From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: Re: What DTD for a thesis
Date: Mon, 20 Jan 2003 20:47:07 +0100 [thread overview]
Message-ID: <20030120194707.GB1347@scaprea> (raw)
In-Reply-To: <871y37pzzf.fsf@gundla.ch>
On Mon, Jan 20, 2003 at 05:06:44PM +0100, Patrick Gundlach wrote:
> Hans Hagen <pragma@wxs.nl> writes:
>
> Hello,
>
> I tried to get the documentation out of this file but it failed (sorry
> about only posting things that fail and not about the 1000 things that
> are so nice about ConTeXt..)
>
>
> First of all the interface=en is confusing ConTeXt:
>
> [...]
>
>
> After changing this to nl (or removing it or --interface=nl on the
> commandline) I get:
>
>
> [...]
I have the same problem when I try to read my own Docbook In Context
documentation. As a result I have never been able to read it myself in
formatted form :-(. How should I solve the language problem? The
documentation uses the english interface, but both the english and the
dutch interface run into problems.
Simon
--
Simon Pepping
email: spepping@scaprea.hobby.nl
next prev parent reply other threads:[~2003-01-20 19:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0301201049220.908-100000@g31.physik.fu-berli n.de>
2003-01-20 10:10 ` Hans Hagen
2003-01-20 14:16 ` Bruce D'Arcus
2003-01-20 14:24 ` Hans Hagen
2003-01-20 16:06 ` Patrick Gundlach
2003-01-20 16:41 ` Hans Hagen
2003-01-20 17:01 ` Maarten Sneep
2003-01-20 17:25 ` Patrick Gundlach
2003-01-21 9:24 ` Hans Hagen
2003-01-28 11:59 ` Patrick Gundlach
2003-01-28 13:21 ` Hans Hagen
2003-01-28 18:05 ` Bruce D'Arcus
2003-01-28 18:16 ` Adam Lindsay
2003-01-29 11:13 ` Hans Hagen
2003-01-29 11:12 ` Hans Hagen
2003-03-12 0:00 ` Adam Lindsay
2003-03-12 10:36 ` Hans Hagen
2003-01-20 19:47 ` Simon Pepping [this message]
2003-01-21 9:21 ` Hans Hagen
2003-01-31 20:12 ` Re: Module documentation Simon Pepping
2003-01-31 21:00 ` Simon Pepping
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=20030120194707.GB1347@scaprea \
--to=spepping@scaprea.hobby.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).