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: local policy)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <4EB796EC.70402@letturefantastiche.com>
References: 
 <CAP-ksogSR473pTTR_nuXj=y5=M4rzNc8ESHdTY0yV-x+2Y6J_Q@mail.gmail.com>
 <1320617924.37218.YahooMailClassic@web113504.mail.gq1.yahoo.com>
 <CAP-ksogoAT-SSu-aD2WjaOVmtJmgxGyu27qEOTaivtLURcYHyA@mail.gmail.com>
 <4EB796EC.70402@letturefantastiche.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-47-899565765
Message-Id: <13E976F9-05C4-4F19-93A3-A0B15E651AB1@free.fr>
From: eric b <eric.bachard@free.fr>
Subject: Re: GPL'd dictionaries (was Re: ftp.services.openoffice.org?)
Date: Mon, 7 Nov 2011 10:04:25 +0100
To: ooo-dev@incubator.apache.org

--Apple-Mail-47-899565765
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=UTF-8;
	delsp=yes;
	format=flowed

Hi Gianluca,

Le 7 nov. 11 =C3=A0 09:29, Gianluca Turconi a =C3=A9crit :

> Rob Weir ha scritto:
>> 1) The user can download the dictionaries onto their own machines, if
>> they agree to uphold the license.
>>
>> 2) We could have a UI in the product that helps the user download
>> dictionaries.  This could state the license and require the user to
>> click "agree".
> Like I've wrote to Pedro, it would be useful, at least to me, to =20
> know how the compiling and releasing structure of AOOo *binaries* =20
> will be organized.
>
> If the binaries will be *contributed* by external volunteers and =20
> structures, the inclusion of GPL'd parts would be consented anyway, =20=

> since the code repository would be untouched and only the binaries =20
> would be hypothetically ruled by GPL.
>


Well, a fast read in the sources (please other, correct me if I'm =20
wrong) leads me to that :


1) there is one module (say a directory in the main OOo tree) named  =20
"dictionaries"

2) inside, the tree is organized into

- one subdir per locale,
- inside every locale, you find

More precisely, main/dictionaries/  contains one subdir per locale + =20
util, containing the main makefile for the module "dictionary" :

af_ZA   da_DK   de_DE   es_ES   gl      hu_HU   lt_LT   no      =20
pt_BR   sk_SK   sv_SE   util
ca      de_AT   diclst  et_EE   he_IL   it_IT   ne_NP   pl_PL   =20
ro      sl_SI   sw_TZ   vi
cs_CZ   de_CH   en      fr_FR   hr_HR   ku_TR   nl_NL   prj     =20
ru_RU   sr      th_TH   zu_ZA

e.g. in main/dictionaries/it_IT, we got :

README_hyph_it_IT.txt   desc_en.txt             =20
hyph_it_IT.dic          makefile.mk
README_it_IT.txt        desc_it.txt             =20
ico.png                 manifest.xml
README_th_it_IT.txt     description.xml         =20
it_IT.aff               th_it_IT_v2.dat
delzip                  dictionaries.xcu        =20
it_IT.dic               th_it_IT_v2.idx

If I'm not wrong, the dictionary itself is the it_IT.dic file.


3) at buildtime, the content of every locale is zipped as an extension

At least this is what I read in dictionaries/util/makefile.mk


4) every zipped dictionary is delivered in the solver, and included =20
in the final package, depending on the goal as an extension

See main/setup_native/source/packinfo/package_names.txt  for the list =20=

of available dictionaries.


5) at packaging time :

when packaging an archive, on a given OS, a list of dictionary is =20
used, to add the one needed for a given locale.

See main/setup_native/source/packinfo/spellchecker_selection.txt to =20
check what dictionary will be installed, for a given locale.

I'm a bit unsure, but the pre-installed dictionaries (or maybe they =20
are at user install time) are installed as extensions.


My 2 cts

Eric Bachard


--=20
q=C9=94=E1=B4=89=C9=B9=C9=99
Projet OOo4Kids : http://wiki.ooo4kids.org/index.php/Main_Page
L'association EducOOo : http://www.educoo.org
Blog : http://eric.bachard.org/news


--Apple-Mail-47-899565765--