Hi, 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. Hans ----------------------------------------------------------------- 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 -----------------------------------------------------------------
On 4/4/06, Hans Hagen
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. Thanks. nikolai
TDS is the Tex Directory Structure, designed so that the various tex distributions use the same file structure. See http://www.tug.org/tds/ -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
Nikolai Weibull wrote:
On 4/4/06, Hans Hagen
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. Taco
On 8/9/06, Taco Hoekwater
Nikolai Weibull wrote:
On 4/4/06, Hans Hagen
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? nikolai
Nikolai Weibull wrote:
On 8/9/06, Taco Hoekwater
wrote: Nikolai Weibull wrote:
On 4/4/06, Hans Hagen
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 -----------------------------------------------------------------
Nikolai Weibull wrote:
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?
No, you do have to do that yourself, it is not autogenerated. (because that would not be very reliable) Taco
On 8/9/06, Taco Hoekwater
Nikolai Weibull wrote:
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?
No, you do have to do that yourself, it is not autogenerated. (because that would not be very reliable)
OK, done. Now how do I get this package to the modules homepage? nikolai
Nikolai Weibull wrote:
No, you do have to do that yourself, it is not autogenerated. (because that would not be very reliable)
OK, done. Now how do I get this package to the modules homepage?
On modules.contextgarden.net, there is a "log in" link in the upper right corner. Do that (use your wiki login), and you get a new set of links for updating your modules. Cheers, Taco
On 8/9/06, Taco Hoekwater
Nikolai Weibull wrote:
Now how do I get this package to the modules homepage?
On modules.contextgarden.net, there is a "log in" link in the upper right corner. Do that (use your wiki login), and you get a new set of links for updating your modules.
I don't have a login, that I know about, so I created a new one. My username is "now", so if you could give the user "now" ownership of the BNF grammar module, that'd be great. Thanks! nikolai
Hello Nikolai,
I don't have a login, that I know about, so I created a new one. My username is "now", so if you could give the user "now" ownership of the BNF grammar module, that'd be great.
Done. If you have any more questions, just ask me. Sorry for the delay: I was offline for a few days. Patrick -- ConTeXt wiki and more: http://contextgarden.net
participants (5)
-
Hans Hagen
-
Nikolai Weibull
-
Patrick Gundlach
-
Sanjoy Mahajan
-
Taco Hoekwater