[tex-hyphen] License of hyphenation patterns

[Xiangye Xiao (肖湘晔)]

Sascha, please chime in if I give wrong answers.

Thanks for your all interest and questions! I am growing knowledge on open
source licenses in the process of communicating with authors. I probably
didn't make clear communication at the beginning. Sorry for the confusion.
Let me try to clarify.

*First is about our use cases.* We want to use the data in Android. We
already shipped US English, Hungarian, Armenian, Norwegian etc, and we want
to support as many languages as possible. This is where the hyphenation
pattern data end up at:
https://android.googlesource.com/platform/external/hyphenation-patterns/+/master

We thought about committing the data in Unicode CLDR and then pull the data
from CLDR to AOSP. It may or may not work. We are not sure yet. We think it
is potentially good because Unicode has engagement with
contributors/developers of many language data. However, Unicode license is
not a requirement or a goal for us. Our goal is to use the data in Android
(may be other products in the future too)

*Second is about the licenses.* Our open source team told me
MIT/BSD/Apache/Unicode licenses are acceptable licenses for our use cases.
LGPL v2 is also okay since the patterns are loaded at run time (i.e.,
dynamic linked) and we refer to original sources for the hyphenation
patterns in AOSP. These licenses can be conflicting in some areas. Picking
whatever licenses among this group is okay for us.

I am still trying to arrange a *video conference or phone* meeting with the
open source license guy. It is close to holidays, so can be a bit hard.


On Sun, Dec 13, 2015 at 11:41 PM, Philip Taylor <P.Taylor at rhul.ac.uk> wrote:

> 你好, 肖湘晔 --
>
> > I found hyphenation patterns of many languages in tug.org
> > <http://tug.org> (link
> > <
> http://tug.org/svn/texhyphen/trunk/hyph-utf8/tex/generic/hyph-utf8/patterns/txt/
> >)
> > and are interested in using the data. However, licenses of many pattern
> > files do not work for us. [...] Unicode license also works for us but it
> requires to
> > make Unicode joint copyright owner.
>
> Could you please clarify who the "us" are in "licenses of many pattern
> files do not work for us" and "Unicode license also works for us" ?
> When you first wrote to Dominik Wujastyk regarding the British English
> patterns, you said :
>
> > I really like your hyphenation patterns for British English and would
> > like to put it in Unicode.org. However, the license doesn’t work.
> > Could you license it under Unicode license.
>
> but now you write that "Unicode license also works for us but it
> requires to make Unicode joint copyright owner" so it would seem that
> the primary motivation is /not/ to "put [the patterns] in Unicode.org".
>  If you could clarify exactly who the "us" in the two phrases above, and
> at the same time clarify exactly what you (or "us") are planning to do
> with the pattern files once the licence has been modified, we may all be
> better able to what is required and your motivation for the request.
>
> Philip Taylor
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tex-hyphen/attachments/20151214/c92689e2/attachment-0001.html>