Re: [dev-context] [NTG-context] modules on wiki
Hi Hans, (moved to dev-context) Hans Hagen wrote:
Thi sis what we have:
Archive: t-bib.zip
- this on is ok
Jay me! :)
Archive: t-lettrine.zip
- doc path
What do you mean by this? the files are in the 'doc' tree already? And i think those t-XXXX.pdf files tend to be the output of texexec --module t-XXXX (but they seem unnecessary).
- either we use t-name or name as subpath, but we need to be consistent and since only t-'s go there, we can omit the t- from the path
I vote for dropping the prefix. We are in 'third' already.
- only store runtime files in context/third/somename
- always provide an doc path
- put a file t-somename.xml in the tex path that looks like:
I already have t-bib.xml and t-lettrine.xml, those contain texshow/xml syntax information. Perhaps these should be moved elsewhere?
or whatever we can agree on, but at least let's cook up a format that can be parsed (the wiki already has something like that to generate the modules pages, i dunno the format)
How about the TPM format? It is an RDF syntax that should do all we need already. There even is a filled one for context (TL2005): http://www.tug.org/texlive/devsrc/Master/texmf-dist/tpm/context.tpm Taco
Taco Hoekwater wrote:
And i think those t-XXXX.pdf files tend to be the output of
texexec --module t-XXXX
(but they seem unnecessary).
indeed, let's not add those, otherwise the cont-ext.zip file will grow too large (btw, t-bib files will go in the main context zip since bibliographies are part of the core deal; we may even promite it to m-bib)
- either we use t-name or name as subpath, but we need to be consistent and since only t-'s go there, we can omit the t- from the path
I vote for dropping the prefix. We are in 'third' already.
ok, dropped
I already have t-bib.xml and t-lettrine.xml, those contain texshow/xml syntax information. Perhaps these should be moved elsewhere?
ah, good point, so maybe something r-lettrine.xml (with the r- for readme); i can even imagine then that d-* files are for the main documentation)
or whatever we can agree on, but at least let's cook up a format that can be parsed (the wiki already has something like that to generate the modules pages, i dunno the format)
How about the TPM format? It is an RDF syntax that should do all we need already. There even is a filled one for context (TL2005):
http://www.tug.org/texlive/devsrc/Master/texmf-dist/tpm/context.tpm
ok, can you make one for t-bib and t-lettrine that can serve as an example? i think that these go in atpm path in tds 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 -----------------------------------------------------------------
Hans Hagen wrote:
ok, can you make one for t-bib and t-lettrine that can serve as an example?
i think that these go in atpm path in tds
Sure (but not today any more, I need a break). They will be named "t-bib.tpm" etc., by the way. Shall we create tex/context/interface/third for the syntax definitions? Taco
Taco Hoekwater wrote:
Hans Hagen wrote:
ok, can you make one for t-bib and t-lettrine that can serve as an example?
i think that these go in atpm path in tds
Sure (but not today any more, I need a break). They will be named "t-bib.tpm" etc., by the way.
Shall we create tex/context/interface/third for the syntax definitions?
ok 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 -----------------------------------------------------------------
participants (2)
-
Hans Hagen -
Taco Hoekwater