Hi, > By the way, we would like to change the default bundled French > dictionary for OOo 3.3. We have worked on a new one, called “Modern”, > which is less confusing, especially for non native French speakers. > Description here: > <http://extensions.services.openoffice.org/fr/project/french-dictionary-modern> > Is it possible? Shall I open an issue? >
It is easily possible. Just submit an issue with a link to the new extension and I will replace the current one. But if you have no specific needs to get it replaced right away I'll probably just keep the issue until right before the release of OOo 3.3. After you may already have new updates until that time. ^_- But if you want to get it included right away just say so in the issue and I will fix it in a current CWS. > > Also, in order to not miss on pointing this out, I'd like to > > specifically mention that I was told that for bundled extensions there > > will be no update notifications! That was already announced in the spec, > > but probably not everyone has read it. See > > http://wiki.services.openoffice.org/wiki/Setup_-_Bundled_Extensions > > I read: > "Bundled extensions, such as the dictionaries, can be configured if they > provide their own options pages in OOo's options dialog." > > What kind of options users could change in a dictionary extension? > Is there an example somewhere? > I think that is a misunderstanding on the side of the author who is probably not really familiar with dictionary extensions. I will check with the author. Of course dictionaries (as every other extension) could come along with there own UI. But it does not really make sense since everything need to get the dictionary run is already provided in the dictionary.xcu. If an extrension is to bring along UI for its configuration it needs to write code, e.g. a jar library, have a new set of configuration entries defined and implemented ia UNO API. And in the end all of that would still be useless if it does not provide its own spell check, thesaurus and hyphenation engine as well, since the engines in lingucomponent are not aware of anything configured locally to a extension. The only interface between lingucomponent and dictionary extensions is the dictionary.xcu. I think the author confused 'plain' dictionary extensions that do not come along with UI and code with extensions like the 'Duden Korrektor' that implements a complete linguistic engine, along with dictionaries, specific UI, help pages and a specialized option tab in 'Tools/Options'. Something like that can be done but it is probably far beyond what a regular dictionary provider likes to do. Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lingucomponent.openoffice.org For additional commands, e-mail: dev-h...@lingucomponent.openoffice.org
