Re: [tex-hyphen] License of hyphenation patterns

Hi Xiangye, On Wed, Dec 16, 2015 at 08:19:32PM -0800, Xiangye Xiao (肖湘晔) wrote: > Let me know if there are still confusions and you want a meeting with our > open source expert and engineer. A conference call of some sort will be most welcome when people are back from holiday. Please

Re: [tex-hyphen] License of hyphenation patterns

Just a note: please don't CC mojca at tug.org. That email was probably a blind guess by the poster based on the fact that there is a SVN user with that name on tug.org. That email doesn't exist. Mojca

Re: [tex-hyphen] License of hyphenation patterns

你好, 肖湘晔 -- Xiangye Xiao (肖湘晔) wrote: > *First is about our use cases.* We want to use the data in Android. OK, but I am still not clear who "we" are. I had initially thought that you were writing on behalf of the Unicode consortium, but I now know that that is not the case. Are you writing

Re: [tex-hyphen] License of hyphenation patterns

[Sorry if you get a duplication, I mistakenly deleted a comma in the cc list.] to take on any other obligations besides giving authors credit. That's basically the point of MIT, BSD or Apache. This is off the subject of hyphenation, but FYI, the Apache 2.0 license has patent and

Re: [tex-hyphen] License of hyphenation patterns

Who will attend the meeting from TUG side Speaking as a member of the TUG board of directors, I can say that the whole hyphenation stuff has nothing in particular to do with TUG, organizationally/administratively. TUG per se has no technical staff and no substantive budget. All TeX work in

Re: [tex-hyphen] License of hyphenation patterns

On 13 December 2015 at 21:09, Karl Berry wrote: > Who will attend the meeting from TUG side > > Speaking as a member of the TUG board of directors, I can say that the > whole hyphenation stuff has nothing in particular to do with TUG, > organizationally/administratively. TUG per se has no

Re: [tex-hyphen] License of hyphenation patterns

On 11/12/2015 13:23, Joseph Wright wrote: > On 10/12/2015 19:18, Xiangye Xiao (肖湘晔) wrote: >> After reminded by Author and Claudio (cc'ed here), I realize reaching out >> tug hyphenation mailing list can be more efficient to get connected with >> authors. Could you/TUG help coordinate with authors

Re: [tex-hyphen] License of hyphenation patterns

> Just to add that I assume the issue is not the LPPL (or GPL or ...) per > se but that your use case requires a very 'permissive' license: correct? I'll let Xiangye reply to that part since I don't know anything about the project, but I'm curious about your interpretation of the LPPL: do you

[tex-hyphen] License of hyphenation patterns

Dear Xiangye (and everyone else), I didn't see your initial email, but Arthur forwarded your message. (Thank you, Arthur.) And sorry for top-posting. Actually, I saw a number of email messages on the tex-hyphen mailing list, but I wanted to take more time and this email came faster and with a

Re: [tex-hyphen] License of hyphenation patterns

> Not all files are covered by LPPL. Having co-authored the full list on http://www.tug.org/tex-hyphen/#languages I'm very much aware of that. This is a situation to be expected and authors should choose whatever licence they think is best for their contribution; but that wasn't my question.

Re: [tex-hyphen] License of hyphenation patterns

On 11 December 2015 at 15:19, Arthur Reutenauer wrote: > Since the LPPL is a very > popular choice in the TeX world, for obvious reasons, it would be good > to get a clear idea of how compatible it is with other licences. I'm not a licence expert, but I would say "very bad". Both Mozilla and

[tex-hyphen] License of hyphenation patterns

Dear Miss Mojca and other active contributors to tug hyphenation data, I found hyphenation patterns of many languages in tug.org (link ) and are interested in using the data. However, licenses of many pattern files

Re: [tex-hyphen] License of hyphenation patterns

Not all files are covered by LPPL. Most have LPPL and/or GPL and/or some public-domain-like license, some have more restrictive licenses. met vriendelijke groet/kind regards, ing. Martijn van der Lee Advanced CRMMail Technology BV Amstellandlaan 84 1382CH Weesp (Greater Amsterdam) Phone:

Re: [tex-hyphen] License of hyphenation patterns

Hi Xiangye, Am 10.12.2015 um 20:18 schrieb Xiangye Xiao (肖湘晔): > Dear Miss Mojca and other active contributors to tug hyphenation data, > > I found hyphenation patterns of many languages in tug.org (link > ) > and

Re: [tex-hyphen] License of hyphenation patterns

> I'm not a licence expert, but I would say "very bad". I've found this Wikipedia article very useful: https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses Javier

Re: [tex-hyphen] License of hyphenation patterns

More to write about licenses, but for right now: ar> with, obviously, the addition of the "renamed if modified" clause. No such "renaming" clause exists in LPPL 1.3. That was the major change in 1.3 (see Frank's long long article about it in TUGboat if you want). What does exist is the