Re: [dev-context] setup-en.pdf and mkiv command list

On 5/17/2017 2:23 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:

On Wed, 17 May 2017 01:43:38 -0600, Hans Hagen wrote:

...

...

...

...

I wrote a python script to auto-generate keyword lists from the full xml file. All the "abstract" keywords (those with a cd:sequence tag) are simply ignored. The full list is in the KEYWORDS.txt file.

idris probably also wants the instances, so \startsubject and so; in due time we'll add cd:instances to the relevant commands (kind of experimental now)

Hmm, so we have an ambiguity. See setup-en.pdf, p. 302:

\startSECTION is typeset in slanted, but is an abstract command that can have an indefinite number of instances

\startchapter is typeset in slanted, but is a concrete command -- in this case a pre-supported instance of an abstract command.

Question 1: Why is \startchapter typeset in slanted?

to show that it's an instance

...

Question 2: Is there a hook in the i-*.xml files so that Jason's script can distinguish between abstract commands and pre-supported instances? We want a way to capture the latter while ignoring the former? Or are we stuck with the ambiguity until cd:instances is supported? In the latter case we'll have to do some manual work...

cd:instances

While we wait for support cd:instances: How about this heuristic to distinguish abstract commands from pre-supported instances:

======= If slanted and containing and containing *no* capital letters, treat as an instance. =======

(slanted is not part of the coding, instances is)

Wolfgang, Hans: Will this heuristic leave any residue, i.e., leave out any pre-supported instances?

well, you can easilly check that .. probably it's ok but not a complete list ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------