To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=101716


User tl changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|''                        |'dwb,nemeth,tl'
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Thu Nov 19 08:45:37 +0000 
2009 -------
I also just noticed this issue because of the latest new comment...

tl->barry_carroll: There is a problem with the suggested fix. Of course it will
work with the dictionary extension distributed with the installation set. But
one needs to conteact the extension author as well in order to have him/her add
the locale for the next version as well. Otherwise if a newer version of the
extension will become available and gets installed the support for en-IE (that
is the added locale) will be missing in the new dictionary.xcu and thus en-IE
spell checking will not work anymore.

I'm adding the persons listed in the respective readme file file to CC.

tl->nemeth,dwb: Is it Ok for you to add 'en-IE' as additional locale to future
versions of the en-GB dictionary?
If so, then please assign this issue to me and I will do the same in the OOo
source code for the current dictionary. Then everything should be fine.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
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]

Reply via email to