Hi Robert, Are you still interested in working in the area of dictionaries?
It took us a while to come up with an idea related to dictionaries that we like to change and which might be interesting to you: We like to change our user-dictionary format to use the same as Hunspell dictionaries. This would roughly require the following: - Hunspell needs to have support for exception dictionaries with suggestions implemented - We need a language 'ALL' for Hunspell dictionaries since our user-dictionaries are capable of that - For the hyphenation information in the user-dictionaries we need a separate file to keep those. - the related code in OOo needs to be changed to make proper use of the new dictionary format and of the new hyphenation specific user-dictionaries The first two tasks will probably require that you get in touch with Lazlo Nemeth, the owner and maintainer of Hunspell (a OpenSource project itself) to see if and how exception dictionaries can be be implemented. If you are still interested please drop me a note and I will ask Lazlo if he has the time to get you introduced in the respective parts of Hunspell. Regards, Thomas Robert Black wrote: > Thomas, > > Totally agree with what you said about index out of bounds crashes in > regards to operating systems. Hiding these crashes is a terrible idea. I > didn't see any detail on the issue to know it was this kind of crash, > because the summary just says "Fix for stacktrace 9383", but I will take > your word on it. :) > > I am not really involved in making any dictionaries for OOo. I merely helped > out the author of the Australian dictionary recently with some technical > issues. As far as I know, Mathias is handling this, although I would be > happy to help if required. > > In fact, I am looking to contribute as a developer for OOo but am not sure > where I should begin. I am a moderately experienced C+ programmer. I have > worked on remotely distributed development environments commercially. As I > mentioned above, I have become reasonably familiar with the dictionaries > from the extension point of view, but not yet seen any of the code base. I > was hoping to just single out a few very simple bugs to get started. From a > user perspective I mainly use Writer and Calc. Could you give me any advice > on where to start? > > Thank you. > > Regards > Robert Black > > > 2008/12/12 Thomas Lange - Sun Germany - ham02 - Hamburg < > [email protected]> > >> >> 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] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
