Issue 74291 - distribution of hyph_el_GR.dic violates the LPPL
Summary: distribution of hyph_el_GR.dic violates the LPPL
Status: CLOSED FIXED
Alias: None
Product: lingucomponent
Classification: Code
Component: other (show other issues)
Version: OOo 2.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: issues@lingucomponent
QA Contact: issues@lingucomponent
URL:
Keywords: oooqa
Depends on:
Blocks: 74283
  Show dependency tree
 
Reported: 2007-02-07 17:08 UTC by doko
Modified: 2017-05-20 09:01 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description doko 2007-02-07 17:08:36 UTC 
hyph_el_GR.dic, as found in
http://ftp.services.openoffice.org/pub/OpenOffice.org/contrib/dictionaries/hyph_el_GR.zip

is derived from a file licensed under the LPPL, but it violates at least
paragraph 6d of the LPPL.

Needed information: Either distribute the original file as well, or (better)
name the file and the version of the file which the derived work is based on.
The LPPL requests "Information that is sufficient to obtain a complete,
unmodified copy of the Work."

The LPPL can be found at http://www.latex-project.org/lppl.txt
Comment 1 doko 2007-02-07 21:41:39 UTC 
Got the following reply by the person who converted the file:

Since there are questions about it's legal status, please remove that
file, and replace it by the one at
http://www.ellak.gr/pub/oo_hyphenation/hyph_el_GR.zip
It is written by the same person that wrote the Latex one (which is not
under LPPL), so there should be no problems with that.

It would be a good idea to remove it from the el.openoffice.org site as
well.

Anyhow, I believe it is an original work but I have no idea how can one
prove that there is only one way to define greek hyphenation using the
specific method, and I do not want to get involved in any legal issues.
Comment 2 stefan.baltzer 2008-10-30 11:38:22 UTC 
SBA: Confirming 21 sub-issues of issue 74283 at once.
I believe that doko did the right thing and could/should have set the issues to
NEW right after submitting (Just like all "CanConfirm rights owners" do when
submitting issues)

Thus I beieve that taking a second look at EACH of these files is not worth the
effort. The state "Unconfirmed" is irritating queries used in daily QA work.
Comment 3 Mechtilde 2009-12-19 20:58:15 UTC 
not in the source of OOO320_m8
Comment 4 Pedro Giffuni 2011-12-02 04:57:39 UTC 
The dictionary component was removed as part of the IP clearance process.