|
Dear Freek, Freek Wiedijk wrote: The only exception that I know: the vocabulary 'ARYTM'. I do not know why it has such a name.
What is the relation between foo.miz and foo.voc? How it happened that they have the same name? When you submit a new article, you submit, sometimes, a new vocabulary. The Library Committee asks you to assign the same name to the vocabulary as to the article. To simplify book keeping. What is on foo.voc is often accidental. E.g. When attributes 'negative' and 'positive' were introduced in ASYMPT_0, 'positive' was placed on the vocabulary ASYMPT_0.VOC, but not 'negative', it already was on the vocabulary ZF_REFLE.VOC. After a revision the definitions of the attributes were moved to XXREAL_0. But symbols are still on old vocabularies. I like the first part. Why I should do the second?I don't see the problem, sorry. It is trivial to write a perl script that transforms a directory with separate .voc and .miz files into a directory in which the vocabularies are in included in the .miz files. So to "maintain" MML one then could run that script, do whatever is needed for maintenance, and then run the inverse script. Actually the vocabularies are kept in one file: MML.VCT. With the exception of private vocabularies, of course. My mistake, if I restore MML.VCT, it will be no problem Only I do not like to do unnecessary job.But I don't see why for maintenance the vocabularies couldn't stay in the .miz files. Can you explain? Without the preprocessing the problem is that an article may use a vocabulary that has the name of article that is processed later. What I have in mind that (without preprocessing) we should move symbols from one article to the other, any time we change the order of processing. Probably in such situation somebody would find that the vocabulary should be in a separate file. This would be a big discovery. And a big relief. :-) Regards, Andrzej |