My impression is also that an "all in one" English dictionaries approach is a good way to handle this issue. One extension in the extension manager is much cleaner and less confusing for users.
However, I thought that there is nothing to stop there being two different Hyphenation dictionaries in there: one for US only, one for other locales of English. I thought it is just a matter of making an extra entry in the dictionaries.xcu file for this? I am looking at the OOov3.0.0 version to make this conclusion, so maybe something has changed. Robert 2008/12/11 Mathias Bauer <[EMAIL PROTECTED]> > Németh László wrote: > > > Hi Mathias, > > > > 2008/12/8 Mathias Bauer <[EMAIL PROTECTED]> > > > >> Hi László, > >> > >> Németh László wrote: > >> > >> > It seems, within a few days I will finish the morphological extension > of > >> the > >> > en_US dictionary (converting the morphological data of Wordlist > project). > >> > >> Great! > > > > > > I will send it next day. (I had to fix some problems in the CWS, too.) > > > > > >>> I'm still waiting for a plan how to upload all pre-bundled dictionaries > >>> to our repository. But that's the second step. > >> > >> I think, it's possible to upload all official (accepted and preferred by > > NLP > >> projects) extensions from > >> http://extensions.services.openoffice.org/automatically with the > >> required database and updating mechanism/script in > >> the repository. > > > >> Sorry, I was talking about how we can bring all dictionaries that are > >> committed to svn and are bundled with the different localized builds to > >> the extension repository. This needs some work to do. > > > > > > It seems, some bundled dictionary extensions are attached to the relevant > > issues for verification, so they are already stored in an open > repository. > > They need an updated link or registration on extensions.services site > yet. > > > >> > >> > >> > Unfortunately, English (variants) have no NLP projects yet > >> > (this was a topic of the last OOo conference). For American English, I > >> will > >> > make an official en_US extension maintained by Wordlist project > >> (members). > >> > >> The OOo bundled dictionary does intentionally have only an "en" > >> dictionary, not a "en-US", "en-GB" etc. because they share hyphenation > >> and thesaurus. I would like to keep it that way and so I would like to > >> update the bundled dictionary with your new files. And of course in case > >> of updates I would also like to provide "en" dictionaries, not "en-US". > >> Does that make sense? > > > > > > No, it doesn't. But using common (i. e. British) hyphenation patterns is > a > > mistake, because American and British English have different hyphenation > > rules, see http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddhyphen. > There > > is an improved en_US pattern file in the last hyphen distribution: > > http://downloads.sourceforge.net/hunspell/hyphen-2.4.tar.gz, (also > attached > > here: http://www.openoffice.org/issues/show_bug.cgi?id=90028). > > Well, there are also canadian, australian and south african english that > we are serving with our extension. We have spelling dictionaries for > them, but no hyphenation dictionaries and no thesaurus. So my take on > that was: better use the en-US thesaurus and the en-GB hyphenation than > nothing! > > So how can be serve the users best? We don't offer any other english > builds than en-US, so we have to bundle the other english dictionaries > with the en-US build also. Having 4 extensions except one would clutter > the extension manager UI and - as I said - wastes space. So for me > staying with one "english-all" dictionary extension is the best option. > > Ciao, > Mathias > > -- > Mathias Bauer (mba) - Project Lead OpenOffice.org Writer > OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS > Please don't reply to "[EMAIL PROTECTED]". > I use it for the OOo lists and only rarely read other mails sent to it. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
