Apache OpenOffice (AOO) Bugzilla – Issue 114603
lingucomponent: please update Dutch spell checking extension for version 3.3
Last modified: 2013-02-24 20:42:35 UTC
With reference to the "Call for OOo 3.3 dictionary updates" on lingu-dev, please update the Dutch spell checking extension using the one found on the extensions website. See http://extensions.services.openoffice.org/en/project/dict-nl
.
Thanks for the update! Fixed in CWS dict33a.
Verified in CWS dict33a. Funny note: Following the link mentioned in the extension manager, I had a look at opentaal.org in order to get some "random dutch text sample" from that page. Quote from tha page describing their stuff: "...ondersteuning voor talrijke woordsamenstellingen..." - and exactly the word "woordsamenstellingen" (beside some other compound words from there) is unknown to this version of the spell checker. Sometimes QA is real fun ;-D
sba -> simonbr: OK, Now I got it :-) I downloaded and tried the latest one "nl-dict-v2.00g.oxt" from opentaal.org and - as announced, the couple of compound words are recognized as being OK with that one. What about the idea of using THAT one for 3.3. We have the respective CWS in QA now, but TL and myself think it is better to deliver the latest that "leaving it to the user" to get a new one or to get an update notification once OOo 3.3 is released... Shall we reopen this one? Please comment ASAP, thx.
Sure, by all means, go ahead!
-> simonbr: Thanks for the quick response -> TL, go for it.
Updated to newest version "2.0.0".
Verified in CWS dict33a.
OK in OOO330_m13. Closed.
I installed OOo 3.3 RC6 (Dutch) for Windows and it still comes with "Dutch spelling and hyphenation dictionaries 2009.03.18" :(
If a have a look at the source code for OOO330_m16 it says it should be the 2.0.0 dictionary. See http://hg.services.openoffice.org/OOO330/file/f429027dae12/dictionaries/nl_NL/description.xml tl->sba: can you have a look? Thanks!
Maybe there is some confusion on my part. Is the bundled dictionary supposed to be shown in the extension manager? I'm starting to suspect the one listed in there is a dictionary I had installed as an extension quite some time ago, and which then must have remained on my system even though I had deinstalled OOo prior to installing the new version. If this is the case, it would be a problem if the older extension dictionary takes precedence over the newer bundled one. (I am not at home right now to check if it does)
tl->simonbr: Currently pre-bundled extensions are still listed in the extension manager but will show a lock symbol as well. In the long run it is planned to not show them anymore, but I don't know when this gets implemented.
Hi Simon, Installing OOo_3.3.0rc6_20101120_Linux_x86_install-deb_nl.tar.gz has as result that I see "Nederlandstalige spellingscontrole 2.00g ..."in Extra|Extensiebeheer. "Maybe there is some confusion on my part. Is the bundled dictionary supposed to be shown in the extension manager? " Yes "I'm starting to suspect the one listed in there is a dictionary I had installed as an extension quite some time ago, and which then must have remained on my system even though I had deinstalled OOo prior to installing the new version. " The extensions that you install, remain in the user-profile, which is used by the new installated version (stable, RC). "If this is the case, it would be a problem if the older extension dictionary takes precedence over the newer bundled one. (I am not at home right now to check if it does) " Usually user settings (user path), overrule the global settings (share path). So I guess there is a smart meganisme on the OOo extensions functions, that recognises the user installed and the disables the also installed global one (if present). When I start rc6 with the user profile from 3.2.1, I see the "Nederlandstalige spellingscontrole conform ... 1.1.1 " So this supports what you think: you see the extension that was installed by you earlier in an older version of OOo.
I just talked with our extension specialist. Provided that both extensions have the same identifier (that is are recognized as the same extension different but different versions) it should be like this: Lets assume in the user profile there is a older version 0.8 and a new office installation comes along with a 1.0 version of the very same extension. Then, since the extensions in the user profile have precedence over the one from the installation, the 0.8 version will win. However... Sooner or later the update mechanism will see that there is a newer version of the very same extension found in the installation itself (the pre-bundled 1.0 version) and will give a 'update available' notification. If the user chooses to allow that update then the pre-bundled version will be copied to the user preferences as well and replace the older version there. This will finally resulting in the 1.0 version being in the installation AND the user preferences and the one in the latter place will get normal update notifications as if the user had installed it manually.
I re-verified the correct version (2.00g) is in OOO330_m15/m16 on Windows, Linux and Mac OS. While doing so, I noted that we have a tiny encoding issue in the extension: In the Extension manager, the Dutch native description reads "...de offici#le standaard van de Taalunie...." - I saw different replacement characters, it should read "officiële" so the "E with two dots" gets lost. The "title" of the extension has the same letter, but it looks OK. That title comes from the \description.xml. Having a look at ..\description\desc_nl_NL.txt solves the riddle: The .xml is encoded and read in UTF-8 while the .txt is written in Western encoding. When viewing the file with standard encoding, all looks good, but when opening it with "forced UTF-8" encoding (with Writer, file-type "Text, encoded") or Firefox with the view options), the error shows. This seems to take place when extension descriptions are displayed. The fix is very easy (just tried it myself): Unzip the extension, open the .txt. file with Standard Western Europe encoding. Then re-save it in UTF-8, re-zip the extension and all looks fine. I understand that the version in the extension repository is only a copy from the one to download from opentaal.org. -> Simon/Cor: Can one of you please tell the responsible folks at opentaal.org to do what I described above? Thanks a lot.
Set issue to fixed.
Closing issue.
@sba, I'll take care of the encoding issue in the .txt file. I wonder though if I have to file another issue because I'm still stuck with the obsolete dictionary. In my extension manager it is shown with a lock next to it (which suggests it actually came as a bundled dictionary with a previously installed version of OOo) and I cannot remove it. Also, I tried to force the update to the newer bundled extension but if I select it and click "check for updates" it says there are no updates. How can I update it with the newer bundled dictionary or at least remove it?
I recognize, that I sometimes have extensions, installed by myself, with sort of error messages, not properly installed or so. Never paid enough attention to it, to find out what really is the problem. Hmm, this is different from your situation ;-) Possible dirty hack: - backup your user profile (docs&settings/app data/openoffice.org/3/user ) - go to the user/unopackages folder and find yourself the dictionary - remove it - start OOo No idea what will happen - in the same folders there is a database that registered the extensions, so it might crash? Wondering how it works out ... ;-)
@simonbr: Thanks for passing on the encoding thingie. A new issue to spotlight the handling of inherited extensions looks feasible. Discussions in closed issues are sort of a "private chat" among those on CC, thus not feasible.
You can remove bundled extension via the setup by deselecting the respective entries. For Windows this would be available under "Settings/Control Panel/Add or Remove Programs" where you need to look for the OOo entry. For that one there should be a "Modify" option.