ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: Re: Module documentation
Date: Fri, 31 Jan 2003 22:00:39 +0100	[thread overview]
Message-ID: <20030131210039.GA3313@scaprea> (raw)
In-Reply-To: <20030131201203.GA1992@scaprea>

I just installed the latest beta, and that solved the problem. I can
now run module documentation with an english interface. I did not yet
try the dutch interface.

Simon

On Fri, Jan 31, 2003 at 09:12:03PM +0100, Simon Pepping wrote:
> On Tue, Jan 21, 2003 at 10:21:58AM +0100, Hans Hagen wrote:
> > At 08:47 PM 1/20/2003 +0100, you wrote:
> > >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.
> > 
> > hm, english documentation should work ok,
> > 
> > doen't --interface=en do the trick?
> 
> Both in Dutch and in English I get an error about the other language:
> 
> 1. In Dutch:
> 
> >texexec --module xtag-docbook.tex
> 
> ...
> 
> . . . . . [6.4] . . [7.5] . . .
> ! Undefined control sequence.
> l.423 \subject
>               {Analysis of the high level structure of an article}
> ? x
> 
> 2. In English:
> 
> >texexec --interface=en --module xtag-docbook.tex
> 
> ...
> 
> systems        : begin file texexec at line 4
> (./xtag-docbook.ted
> ! Undefined control sequence.
> \moduletitel ...\insidefloattrue \steltabulatiein 
>                                                   [\c!voor =,\c!na =]\startt...
> l.11 ...ht={2002 Simon Pepping, Michael Wiedmann}]
>                                                   
> ? x
> 
> I have no idea why I seem to be the only one who has this problem.
> 
> Simon
> 
> -- 
> Simon Pepping
> email: spepping@scaprea.hobby.nl

-- 
Simon Pepping
email: spepping@scaprea.hobby.nl

      reply	other threads:[~2003-01-31 21:00 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 ` What DTD for a thesis 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
2003-01-21  9:21           ` Hans Hagen
2003-01-31 20:12             ` Re: Module documentation Simon Pepping
2003-01-31 21:00               ` Simon Pepping [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=20030131210039.GA3313@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).