Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Mathias_Bauer@gmx.net
 designates 213.165.64.23 as permitted sender)
Message-ID: <4ECF9F57.4080503@gmx.net>
Date: Fri, 25 Nov 2011 14:59:51 +0100
From: Mathias Bauer <Mathias_Bauer@gmx.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: GPL'd dictionaries (was Re: ftp.services.openoffice.org?)
References: <4ECE4FEF.8080704@letturefantastiche.com>
 <1322144982.68662.YahooMailClassic@web113507.mail.gq1.yahoo.com>
 <20111124145703.GA27416@localhost>
 <95388529-70C5-4C68-9857-42DBC45FA6B3@gmx.net> <4ECF6203.9080801@a-w-f.de>
In-Reply-To: <4ECF6203.9080801@a-w-f.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 25.11.2011 10:38, Andre Fischer wrote:
> 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?

Mainly because we package some content from our side together with the 
dic files. That must be done somewhere, and until now it was desired 
that this "somewhere" is inside the OOo build process.

Treating MPL dics as "source files" would require to do the packaging of 
the dictionary extensions elsewhere, in the same way as building the MPL 
binaries must be done elsewhere.

I'm not convinced that this effort is needed, it is possible that we 
don't need to create dic files as "sources" in the same way as e.g. c++ 
files. Again, it was just a suggestion, some room for thoughts.

Regards,
Mathias