Issue 74320 - distribution of hyph_uk_UA.dic may violate the LPPL
Summary: distribution of hyph_uk_UA.dic may violate 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 19:29 UTC by doko
Modified: 2017-05-20 09:01 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description doko 2007-02-07 19:29:56 UTC
hyph_uk_UA.dic, as found in
http://ftp.services.openoffice.org/pub/OpenOffice.org/contrib/dictionaries/hyph_uk_UA.zip
may be derived from a file licensed under the LPPL; it would then violate at
least paragraph 6d of the LPPL.

Information is needed for the origin of this file (if it's built from the
TeX/LaTeX patterns).

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 22:03:07 UTC
Maksym Polyakov did write:
> The patterns in file hyph_uk_UA.dic are identical to the patterns in file:
> ftp://tug.ctan.org/pub/tex-archive/language/hyphenation/ukrhyph/ukrhypmt.tex
> 
> which is a part of Ukrhyph package for TeX/LaTeX.
> 
> I believe there is no problem with LPPL since I am an author of both.
> 
> -- 
> Maksym

I do not want to nickpick, although the LPPL doesn't make an exception.
Comment 2 Mechtilde 2009-12-20 11:10:48 UTC
sot in source code of OOO320_m8
Comment 3 Mechtilde 2010-01-23 12:47:49 UTC
set to NEw
Comment 4 Pedro Giffuni 2011-12-02 05:11:56 UTC
The dictionary component was removed as part of the IP clearance process.