Hello Robert, > I am glad you detailed that, as that is exactly how I thought it should > work. > > Out of interest, the current standard English dictionary extension > hyphenation dictionary currently uses multiple locales (and the same for the > associated thesaurus). So I am surprised to hear there is a bug associated > with this. From my own personal use I have never experienced any problem > with this. Although, I see from the Issue you mentioned that it involved the > Russian dictionary (which I never used). > > From the standard English dictionary extension: > > <node oor:name="HyphDic_en-GB" oor:op="fuse"> > <prop oor:name="Locations" oor:type="oor:string-list"> > <value>%origin%/hyph_en_GB.dic</value> > </prop> > <prop oor:name="Format" oor:type="xs:string"> > <value>DICT_HYPH</value> > </prop> > <prop oor:name="Locales" oor:type="oor:string-list"> > <value>en-GB en-US en-ZA</value> > </prop> > </node>
Well, as with any index out of bounds accesses the result may crash or work depending on the memory content. Also some operating systems are more accepting to that kind of error (which from my point of view is troublesome. A nice clean crash would be the best to find and address such issues). Also it might just be the case that without the fix in the end only the first hyphenation dictionary is available for use and that should then be fine without any crash potential. (I would need to look more closely into the old code to see about that one.) So if you write such dictionaries for multiple language to be used with OOo 3.0.1 you may want to actually cross check that all the languages are available and you get the results you are expecting for each language. Regards, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
