ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: modules
Date: Wed, 09 Aug 2006 12:16:41 +0200	[thread overview]
Message-ID: <44D9B609.4000308@wxs.nl> (raw)
In-Reply-To: <dbfc82860608090138n61e242e8qc21ae90ccf7fdce3@mail.gmail.com>

Nikolai Weibull wrote:
> On 8/9/06, Taco Hoekwater <taco@elvenkind.com> wrote:
>   
>> Nikolai Weibull wrote:
>>     
>>> On 4/4/06, Hans Hagen <pragma@wxs.nl> wrote:
>>>
>>>
>>>       
>>>> In order to be able to generate new zips i'd like the modules in the
>>>> wiki to be tds compliant as soon as possible.
>>>>         
>>> I"ve kept this mail starred since I first saw it and haven't put any
>>> thought into what you're actually asking about here.  Now, however,
>>> I'd really like to know what /TDS compliant/ means and if there's
>>> something I should do with my BNF model to make it so.
>>>       
>> Have a look at the lettrines module for an example that should
>> be simple to apply to t-bnf.
>>     
>
> Thanks (and thanks Sanjoy).  I suppose the PDF documentation is
> auto-generated, so I don't need to include that, right?
>   
once you have a valid tpm file describing the package, you can use 

textools --tpmmake

to update such a file and create a zip 

saves time 

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

  reply	other threads:[~2006-08-09 10:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04  8:02 modules Hans Hagen
2006-08-08 23:33 ` modules Nikolai Weibull
2006-08-09  1:53   ` modules Sanjoy Mahajan
2006-08-09  7:08   ` modules Taco Hoekwater
2006-08-09  8:38     ` modules Nikolai Weibull
2006-08-09 10:16       ` Hans Hagen [this message]
2006-08-09 10:21       ` modules Taco Hoekwater
2006-08-09 11:57         ` modules Nikolai Weibull
2006-08-09 12:07           ` modules Taco Hoekwater
2006-08-09 12:28             ` modules Nikolai Weibull
2006-08-10 14:06               ` modules Patrick Gundlach
  -- strict thread matches above, loose matches on Subject: below --
2008-08-06  8:37 modules luigi scarso
2002-01-17 21:57 Modules Marco Kuhlmann
2002-01-18 18:30 ` Modules Giuseppe Bilotta
2002-01-19 23:20   ` Modules Hans Hagen
2002-01-21 10:13     ` Modules Taco Hoekwater
2002-01-21 14:47       ` Modules Hans Hagen
2002-01-22  9:10         ` Modules Taco Hoekwater
2002-01-22 11:03       ` Modules Eckhart Guthöhrlein
2002-01-19 18:07 ` Modules Berend de Boer
2002-01-19 18:17   ` Modules Marco Kuhlmann
2002-01-20 22:04     ` Modules Hans Hagen
2002-01-20 21:57   ` Modules Hans Hagen
2002-01-20 20:05 ` Modules 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=44D9B609.4000308@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).