ubuntu-manual team mailing list archive
-
ubuntu-manual team
-
Mailing list archive
-
Message #00874
Re: License
I recommend that we _never_ translate this license, since it's a binding
legal document and it is very easy to make a mistake in translation that
alters the entire meaning. If need be, I can email Lawrence Lessig and ask
for help in approving a translation, but instead I would prefer that we do
the following:
- if a localized license is available, use it
- otherwise, use the US English version
This should yield the most legally sound approach for now, and does not bind
us to any legal approval cycle in CC, or expose us to unnecessary risk of
creating a license that's too restrictive, too liberal, contradictory, or
just plain unenforceable.
-ilya
On Wed, Mar 3, 2010 at 8:13 PM, Elan Kugelmass <epkugelmass@xxxxxxxxx>wrote:
> Can we look into sending this upstream to CC? They might want to have their
> lawyers look at our translations. This is legalese, after all.
> Though, given the absence of translated licenses in the first place, they
> might not have the staff in place to check our work.
>
>
> 2010/3/3 Kevin Godby <godbyk@xxxxxxxxx>
>
> 2010/3/3 Martin Lukeš <martin.meridius@xxxxxxxxx>:
>> > Hi Kevin
>> > I pushed Czech translation from
>> > http://creativecommons.org/licenses/by-sa/3.0/cz/legalcode and I put it
>> to
>> > backmatter/ directory under name license-cs.tex
>> > I also tried to do a bit of a LaTeX formating on it and as far as I
>> could
>> > see (thanks to "Make translated PDF" - great button) it looks fine.
>>
>> Great -- thanks!
>>
>> > If I may have a question...
>> > Do you plan to edit "Make translated PDF" button so it will
>> automatically
>> > select appropriate license file? If not present, then it would use
>> original
>> > (English) file.
>>
>> Yes. As soon as Launchpad lets me push this code, it'll use the proper
>> license file and fall back on English if it doesn't have a particular
>> translation.
>>
>> > And second, but I don't know if it isn't more question for Josh. As if
>> there
>> > will be an extra .tex file for translated license then Roseta probably
>> > shouldn't ask for its translation again. If this is doable of course. ;)
>>
>> I *think* that the way I've done it may hide the license text from the
>> translation software so it won't know anything about it. I'm going to
>> add a note to translators in the license.tex file. We'll see how it
>> works soon. :-)
>>
>> --Kevin
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~ubuntu-manual<https://launchpad.net/%7Eubuntu-manual>
>> Post to : ubuntu-manual@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ubuntu-manual<https://launchpad.net/%7Eubuntu-manual>
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ubuntu-manual<https://launchpad.net/%7Eubuntu-manual>
> Post to : ubuntu-manual@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-manual<https://launchpad.net/%7Eubuntu-manual>
> More help : https://help.launchpad.net/ListHelp
>
>
Follow ups
References