Hi Mathias,
On 24.11.2011 18:04, Mathias Bauer wrote:
Just a dumb question: why do we think that the dicts are source code? At least
those without patches are distributed without any treatment. We just package
them. So where is the difference between an MPL library and an MPL .dic file?
Just the extension and the encoding of its content.
When we are just packaging them, then why not just provide the ready
made extensions and either bundle them or place them on the extension
repository. Which, by the way, already contains more spell-checking
extensions than the dictionaries module?
-Andre
Regards
Mathias
Am 24.11.2011 um 15:57 schrieb Ariel Constenla-Haile<[email protected]>:
On Thu, Nov 24, 2011 at 06:29:42AM -0800, Pedro Giffuni wrote:
Hunspell is still the main spellchecker in AOO but we
cannot ship the italian dictionary and even the MPL
dictionaries have to be removed from the repository.
Exactly, what do you mean by saying "You can go ahead and
kill hunspell from the tree"?
We are not allowed to ship copyleft (strong or weak) in
source releases so the same rules about not download+patching
copyleft apply to hunspell.
Unless I misunderstood something?
https://cwiki.apache.org/OOOUSERS/ipclearance.html
Task 1: Clarify legal usage of Category B (eg MPL) libraries
Binary builds of libraries can be shipped with binary release of AOO.
Source code of libraries can remain on an Apache server but (like
ext_sources of old OOo.)
BUT
* source code of libraries is not shipped in a source release of AOO
* instead it can be downloaded and built during bootstrap, but only when
developer uses a configure option that is off by default
[end of quote]
that's why rev. 1204995
http://svn.apache.org/viewvc?view=revision&revision=1204995
introduces:
--enable-hunspell - off by default
--enable-hyphen - off by default
* Category B sources are not included
* Using system/building Category B libraries is off by default
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
