To Do list

An informal and messy list of things to do. May be used for quick notes before they are ripe enough to be entered into the project issue page.

To-Dos proper

introduce changes for OLAC
restrict the ODD further (hmm, create a higher level ODD, that is... enumerate @type for cit ("dicteg", "trans"?), types of notes(?), etc.)
think of setting up an ontology for grammatical stuff, either GOLD or (perhaps easier?) ISOCat (see a proposal)
consider the switch to XSLT 2.0 for the style sheets
- 2016: no full and free open-source implementation available
implement symlinks to schemas and such at last (?) -- but some software (oXygen) doesn't understand symlinks (post in oXygen forums); this is important, because otherwise we'll have to update stuff by hand from shared/
post at least some of this list to the issue tracker...

introduce the header plug-in to the ontology interface
Ergane dictionaries:
- some multi-word entry words are trimmed -- make sure to fix that, too
some English pronunciation info is suboptimal or just wrong; stress marks are missing, too; possibly, use the English-Polish dictionary as the template, or go for something else that is standard.
the distribution of equivalents across senses or just cits within a single sense may sometimes be odd (this is a general lexicographic issue)
possible task: sensible reversal of an existing monodirectional dictionary
possible task: concatenation of existing dictionaries; it would be good to have a system that may allow for the product of such concatenation to be updated
necessary task: go over the FreeDict build system, making it absolutely transparent and as modular as possible
sensible task: use a good dictionary for the basis of pronunciation information (e.g. the English-Polish dictionary is a good beginning for English pronunciation) and project that to all other dictionaries with the same source language
another sensible task: use the info on equivalent grammatical properties (e.g. gender in *-deu or *-fra dictionaries) and project that to all the others

style sheets do not split multiple orth's into multiple dict entries (and hence users can't search for them)

These came up in the process of introducing references to externally defined data categories.

redundancy between <pos>n</pos> and @ana="\#n" -- should we address it somehow?
- it doesn't seem like it can be addressed at tagUsage level
how to ensure equivalence between <pos>vt</pos> and <pos>v</pos><subc>trans</subc> (neither repository has "transitivity" as a general category (GOLD's transitivity is different))
which of the three "masculine"s (etc.) to choose from ISOCat? (weird)
ensure that the masc gender in entry/gramGrp (and rel/gramGrp) need not be the same masc as that used in cit/gramGrp -- because they may very well realise different networks of oppositions.