Issue 91243 - Integrate Vietnamese spellchecker into application
Summary: Integrate Vietnamese spellchecker into application
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: spell checking (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@lingucomponent
URL: http://extensions.services.openoffice...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-01 09:22 UTC by clytie
Modified: 2013-02-24 20:43 UTC (History)
2 users (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description clytie 2008-07-01 09:22:57 UTC
The URL above is for Iván García's Hunspell Vietnamese spellchecker in .oxt form on the Extensions 
website. The licence etc. is built in to the extension.

Our spellcheck workaround page:
http://vi.openoffice.org/about-spellcheck.html
shows screenshots of the install process for this currently external dictionary.

Please integrate this dictionary into the application, since it is currently the best spellcheck dictionary 
for Vietnamese, and the only one available for OpenOffice.org. Users expect it to be built-in, and this 
3.0 release will be key in gaining our user-base, since it is the first release to feature a full Help 
translation. So please integrate it for 3.0 if at all possible.

Thankyou for your help. :)
Comment 1 Mathias_Bauer 2008-07-01 10:26:14 UTC
I'm afraid that we can't integrate the spell checker as it is because it uses
the GPLv3. We either need LGPLv3 or another suitable licence.

cc:ing Martin as he it the poor chap that usually is charged with stuff like
that :-)
Comment 2 clytie 2008-07-01 10:54:14 UTC
I have emailed Ivan (dictionary author) and asked him to join in this discussion.
Comment 3 capiscuas 2008-07-01 11:16:12 UTC
Which other license less restrictive than GPL but more "opensource" can I use
than LGPL ? 

I feel pitty that by opening the license too much, it will be profited even by
propietary softwares. I don't mind to just open it for "opensource" projects
like OpenOffice or Firefox that doesn't have a GPL license.
Comment 4 Mathias_Bauer 2008-07-01 11:31:27 UTC
Here's the licence of the German dictionary (that besides that also comes with
the GPL):

"Without any modifications this dictionary may be distributed with programs that
support the OASIS Open Document Format for Office Applications and whose
PRIMARY format for saving documents is the Open Document Format."

But please stay tuned, Martin is checking whether we can use GPLv3. We think
that at least GPLv2 would be OK for a fast integration but we are still talking
with lawyers about GPLv3 in general.
Comment 5 capiscuas 2008-07-01 13:11:14 UTC
For a fast integration, can I change it into GPLv2 ?
Comment 6 pavel 2008-07-02 09:08:12 UTC
Sorry, but right now, we are in the process of migrating already included dictionaries into extensions.

So the request to integrate an already existing extension into OOo sounds to me like coming from the 
other Planet.

We do not want e.g. Russian OOo to include Vietnamese spellchecker, and Czech and Chinese, Korean, ... 
We want the user to be able to download exactly these extensions he wants to...

Comment 7 clytie 2008-07-02 10:12:15 UTC
I thought builds for different languages were exactly that. Someone downloading a specifically 
Vietnamese build will expect it to include basic Vietnamese writing aids, at the very least a spellchecking  
dictionary.

Is it not possible to integrate a Vietnamese dictionary into a Vietnamese build?
Comment 8 capiscuas 2008-07-02 12:06:31 UTC
Hi  pjanik, 
of course including Chinese extensions in a Russian build as you mention won't
make sense.

but I agree with Clytie that specific builds should have integrated related
extensions, it makes a lot of sense to include vietnamese extensions into the
vietnamese build, like spellcheckers, encoding converters, etc.
Comment 9 Mathias_Bauer 2008-07-02 13:58:48 UTC
Pavel, we will first integrate the vi dictionary files into our "dictionaries"
module. Furthermore we have a list somewhere (scp2?) that defines which of the
many dictionary extensions we have will be packed into the installation set,
depending on the included languages.

So by default the vi dictionary will be packed only if a build containing "vi"
is done (or any other language where people think that having "vi" included
makes sense).
Comment 10 capiscuas 2008-07-02 16:05:46 UTC
In that case I suggest to get the most updated vi_VN.aff and vi_VN.dic
dictionaries from the SVN.

Here it is:

http://code.google.com/p/hunspell-spellcheck-vi/source/browse/trunk/dictionaries/
Comment 11 Mathias_Bauer 2008-07-02 16:38:41 UTC
OK, so if I get a licence for GPLv2 I can take the both files and the licence
file and pack it into an extension. Ingo then can update his list to assign the
"vi" extension to "vi" builds or language packs.
Comment 13 Mathias_Bauer 2008-07-21 09:42:07 UTC
fixed in cws dictionaryupdate
Comment 14 Mathias_Bauer 2008-07-21 11:15:07 UTC
We have added that the vi build by default bundles the dictionary extensions for
vi, en and fr. Please let us know if you think that others should be added (or
en or fr should be removed).
Comment 15 Mathias_Bauer 2008-07-21 11:16:20 UTC
fixed in cws dictionaryupdate
Comment 16 Mathias_Bauer 2008-07-23 13:04:19 UTC
please verify
Comment 17 stefan.baltzer 2008-07-28 10:37:38 UTC
SBA: Verified in CWS dictionaryupdate.
Comment 18 stefan.baltzer 2008-07-28 18:39:45 UTC
SBA: Verified in CWS dictionaryupdate.
Comment 19 thorsten.ziehm 2009-07-20 15:59:17 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues