To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113873
------- Additional comments from t...@openoffice.org Sat Aug 14 04:24:39 +0000 2010 ------- Having us merge the extension you listed (lets call it B) with parts of the other one from our source code (lets call it A) is not a really good idea. The reason for this is that: By merging B with parts of A we will technically create a new extension (lets call it C to which we also have to assign an identifier. Thus later on one of the following will happen: 1) I we use the a new identifier for C, then there will be no update notifications for that one even if A or B will get updated in the repository. In that case the only way to get a new version of the extension will be to install a newer Office with a newer version of that extension. 2) If we use the identifier of either A or B, then upon update of those the installed extension C will be removed and replaced by A or B. Thus the user will either loose the spell check dictionary from B or the thesaurus and hyphenation file from A. Also A and C can not be installed together since then we will have conflicting spell check dictionaries and thus at best will get mangled results from the spell checker. tl->fyva: Thus correct solutions would be - decide on a single extension (A or B) - have the author of A split up his extension in two (A1: spell check dictionary and A2: thesaurus and hyphenation). The we can include both of the extensions B and A2 for Ukrainian (and A1 and A2 for Russian), and then everything should be fine - you need to get permission of the author of A to break his extension, extract thesaurus and hyphenation and the create a new extension C2 (with new identifier) from those on your own. We could then integrate that and if you or anyone else later on provide updates for that extension, then the user will get a proper update as well. - have me implement 1) from above and go with the implied drawbacks Please make your choice. tl->mh: What is your opinion to solution 1). Would that be acceptable, or should we refrain from doing this? --------------------------------------------------------------------- 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: issues-unsubscr...@lingucomponent.openoffice.org For additional commands, e-mail: issues-h...@lingucomponent.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
