Hello,

Mathias Bauer a écrit :

The main reason for the new mechanism was that the old one was broken by
design. And updating is quite easy for users now as extensions can be
updated at any time you want and users can get automatic notifications
about that. This will help distributing updated versions very quickly.

I agree that for developers it was easier to handle it the old way - but
I think first we want to make it easier for users (and less error-prone
BTW), not first for developers. :-)

And for development purposes there is a way to get back the old way.
When an extension is installed it is unpacked into a sub directory of
$(user)/uno_packages. Just search for it and replace the file in that
folder if you want to check your updated dictionary.

Perhaps we should publish this hint for developers somewhere. Any idea
what might be the best place?

Probably here:
http://wiki.services.openoffice.org/wiki/Dictionaries

There is already a note about tools for developers, and this wiki page contains a lot of external links towards dictionaries maintainers sites. They probably keep an eye on this wiki page, to edit it for updates.

I don't know how OOo developers usually communicate to native-lang leaders, but I wonder if each of them knows that the dictionary.lst system will disappear for OOo 3.0 and that no dictionaries will be bundled in the "vanilla OOo install set", and that it has been planned to include some dictionaries as extension in localized builds.

When I talked to the french team, they knew nothing about that, and I had to digg in the website to find back the information and prove what I said was true (It has been said on this mailing-list and somewhere in IssueZilla*, that's all, I believe). No extension was planned to be included in the french localization, so no dictionary by default. But maybe that will change now...?

Regards,
Olivier R.

* http://www.openoffice.org/issues/show_bug.cgi?id=81365

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to