Your own domain or your e-mail address etc. If you are doing your dictionary just as a private person you can use Just break it down to a level where you think you can arrange everything Make you feel comfortable with being the only 'Grabinski', you could add you are employed by company 'linguprovider' in Russia that has theĭomain you could name your node If people outside the core developer cycle want to provide anĮxtensions, I recommend to use the reversed domain schema notation. %origin%/de_CH.aff %origin%/de_CH.dic DICT_SPELL de-CH %origin%/en_US.aff %origin%/en_US.dic DICT_SPELL en-US %origin%/hyph_en_US.dic DICT_HYPH en-US %origin%/hyph_de_CH.dic DICT_HYPH de-CH %origin%/th_de_CH_v2.dat %origin%/th_de_CH_v2.idx DICT_THES de-CH %origin%/th_en_US_v2.dat %origin%/th_en_US_v2.idx DICT_THES en-US Thus a set of dictionary entries in the Linguistic.xcu provided by a single extension may look like this: Also it is the implementations task to distinguish between those files and their potentially different use by their name only. Please note that there is no specified order to the list of files provided in the Locations property. a list of ISO-names for locales listing the languages the dictionary may be used for.a list of file locations (only the ones actually needed by the service implementation).a unique name (the node name in the configuration).The entries that are still missing and need to be provided are those for the dictionaries.Įach dictionary must have an entry of its own. This is done by looking at the format names of the configured dictionaries. When invoked the services are required to check in the configuration which dictionaries they can make use of and thus establishing their set of dictionaries to use. The only link between one of the above services and the dictionaries to be used by them is the name of the dictionary format.

How to install openoffice dictionary