ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: typesetting modules
Date: Sat, 19 Apr 2008 17:23:57 +0200	[thread overview]
Message-ID: <480A0E8D.1020206@wxs.nl> (raw)
In-Reply-To: <4809ED80.5010003@elvenkind.com>

Taco Hoekwater wrote:
> Taco Hoekwater wrote:
>> Taco Hoekwater wrote:
>>> Hans van der Meer wrote:
>>>> For typesetting a context module I did the following, first making  a 
>>>> .ted file and then typesetting it:
>>>> texmfstart ctxtools --documentation --type=pdf char-utf.tex
>>>> texmfstart texexec --silent --pdf --autopdf
>>>>
>>>> However I got an unknown format cont-nl.fmt. Why is nl chosen?
>>>> What I am doing wrong here?
>>> Nothing, but ted files use dutch macro commands, so they need
>>> the dutch interface.
>> I was totally misinforming you, sorry. Let me start over... hangon.
> 
> Here we go: it uses the dutch interface because there is no explicit
> interface given in the file nor on the command line, and it so happens
> that line 3 of <whatever>.ted contains
> 
>    \startdocumentation

ah, i can remove that test because i don't think that nowadays anyone is 
using startdocument (old functionality to build styles for letters, 
stickers, etc)

> This matches the dutch heuristics for interface discovery because
> it is a superset of \startdocument. The second case in scantexcontent
> in tex.rb probably should have something like a \b at the end of the
> match.
> 
> I was confused because
> 
>     texexec --interface=en char-utf.ted
> 
> doesn't work either, but that is unrelated. You need to preload
> a module that texexec --module would load automatically:
> 
>    texexec --interface=en --use=mod-01 char-utf.ted
> 
> That should do it.

or

texexec --modu char-utf.tex

thinking of it ... i add this feature to one of the mtx-* files because:

(1) the whole conversion can be done in memory so no intermediate file 
is needed
(2) the xml interface loading when using luatex is less demanding (and 
can result in faster runs for bigger documents



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2008-04-19 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 12:30 Hans van der Meer
2008-04-19 12:39 ` Taco Hoekwater
2008-04-19 12:45   ` Taco Hoekwater
2008-04-19 13:02     ` Taco Hoekwater
2008-04-19 14:03       ` Hans van der Meer
2008-04-19 15:23       ` Hans Hagen [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=480A0E8D.1020206@wxs.nl \
    --to=pragma@wxs.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).