[Fwd: Re: [NTG-context] Where is \typescriptthree documented?]
Patrick, Perhaps it is easiest if you start simple that 'api' subdivision in texshow-web first. Than i can start adding stuff at any time I have a minute or so to spare. Creating a big preprocessed cont-api.xml file is unlikely for (at least) the next month. Cheers, Taco Forwarded message from Hans:
David Arnold wrote:
All,
I don't understand \typescriptthree. Where is it documented? What does it mean?
I'm not sure that it is documented, but it is the value of the third argument of \starttypescript, and it valid until \stoptypescipt. If the actual argument was a list, then context will loop over each item in the list, each time with the next value in \typescriptthree.
Similar commands are available for \typescriptone and \typescripttwo.
taco: this is probably something for the api documentations, isn't it? (i forgot how we're goint to organize that -) Hans _______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Hi, (late answer)
Perhaps it is easiest if you start simple that 'api' subdivision in texshow-web first. Than i can start adding stuff at any time I have a minute or so to spare. Creating a big preprocessed cont-api.xml file is unlikely for (at least) the next month.
I'll try to get a texshow-web 2 running over christmas/new year with proper database backend and wiki markup in the texts. The api doc could serve as a test before I move all contents from texshow-web to texshow-web 2. OK? Patrick (full quote intended) [...]
I don't understand \typescriptthree. Where is it documented? What does it mean?
I'm not sure that it is documented, but it is the value of the third argument of \starttypescript, and it valid until \stoptypescipt. If the actual argument was a list, then context will loop over each item in the list, each time with the next value in \typescriptthree.
Similar commands are available for \typescriptone and \typescripttwo.
taco: this is probably something for the api documentations, isn't it?
(i forgot how we're goint to organize that -)
Patrick Gundlach wrote:
I'll try to get a texshow-web 2 running over christmas/new year with proper database backend and wiki markup in the texts. The api doc could serve as a test before I move all contents from texshow-web to texshow-web 2. OK?
Excellent! (I'll be too busy to do any documenting before the new year anyway). Taco
participants (2)
-
Patrick Gundlach -
Taco Hoekwater