Martin,
> Slowly though, but I'm able to figure out what is the difference between
> ported and unported licenses. But I wonder how we should make "language
> specific" versions of our manual, not "only" translating it.
>
>
I'm not sure I understand your question. My feedback was that we should u
Seems you will have to modify compiling script accordingly.
No mean to push you Kevin. ;-)
rhetorical question:
Slowly though, but I'm able to figure out what is the difference between
ported and unported licenses. But I wonder how we should make "language
specific" versions of our manual, not "o
>
> >> Regarding bugs in the manual -- it's CC's policy that the published
> >> version is not changed (even for punctuation or factual errors). So the
> 1(f)
> >> reference that is clearly meant to be 1(h) will stay in the manual. They
> >> have a wiki where bugs are tracked -- if I get a link to
>
> Are these the licenses we should be using (if there isn't a
> translation offered on the main license page)?
>
> http://creativecommons.org/international/
>
> --Kevin
>
No, we should be using the unported (i.e. generic), English language
license: http://creativecommons.org/licenses/by-sa/3.0/
Hey, Martin.
>> Regarding bugs in the manual -- it's CC's policy that the published
>> version is not changed (even for punctuation or factual errors). So the 1(f)
>> reference that is clearly meant to be 1(h) will stay in the manual. They
>> have a wiki where bugs are tracked -- if I get a link t
Yes, great job!
But I still don't understand few things.
One that mentioned Kevin.
And when you wrote:
> Regarding bugs in the manual -- it's CC's policy that *the published
> version is not changed* (even for punctuation or factual errors). So the
> 1(f) reference that is clearly meant to be 1(
Excellent job, Ilya! Thanks for your help sorting this out.
Are these the licenses we should be using (if there isn't a
translation offered on the main license page)?
http://creativecommons.org/international/
--Kevin
___
Mailing list: https://launc
All,
An update on my conversation with Diane about license translations. The
Creative Commons acknowledges the lack of linguistically translated versions
of the manual -- their process for porting to specific jurisdictions is
actually to first linguistically translate, and then adapt to the
jurisd
I have a call scheduled for this coming Friday with Diane Peters -- the
General Counsel of Creative Commons -- to speak about their license
translation strategy. If someone else would like to join me for the call,
send me an email.
Since the license isn't a rapidly-changing entity (like the rest o
Do we already know anything about licenses?
---
Regards
Martin Lukeš
P.S.: Please keep the communication history
On Thu, Mar 4, 2010 at 10:47 PM, Ilya Haykinson wrote:
> Well, as a simple example, the German language is also spoken in Austria,
> Switzerland, a number of smaller countries, and
Well, as a simple example, the German language is also spoken in Austria,
Switzerland, a number of smaller countries, and hundreds of thousands of
others around the world who live in places that do not follow laws of
Germany. Just like the English edition is really an "international" edition,
so ar
Seems reasonable to me too. But lets wait for CC guys what they say. Just to
be sure.
---
Regards
Martin Lukeš
P.S.: Please keep the communication history
On Thu, Mar 4, 2010 at 9:44 PM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Should we? I'm not an expert in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Should we? I'm not an expert in this thing, but why not for example use
the german port for germany? Parts of this license quote german laws,
not american, which seems quite reasonable for me?
- ---
Mit freundlichen Grüßen
Daniel S
The versions that you get from the international page are the ported
licenses for particular jurisdictions
We should be using the unported license most likely
I will get on a call later this week or next week with the CC folks and
figure this out
-ilya
2010/3/4 Martin Lukeš
> As you can see fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yap, me myself used the translated version from creativecommons.org and
just formatted it as the original license.tex
- ---
Mit freundlichen Grüßen
Daniel Schury
Am 04.03.2010 17:04, schrieb Martin Lukeš:
> As you can see from my
As you can see from my previous post I used translation directly from
Creative Commons. Other translators should do the same I think.
In case there isn't translated license the original English will be used.
And since we won't translate license text by ourself I see no reason why we
should inform t
CC has a concept of an "unported" license, which is generically applicable,
and a "ported" license -- i.e. one specific to a country's legal system.
We should be using an unported license, since we're not targeting any
particular country with any edition. Some ported licenses may already be
transl
On Wed, Mar 3, 2010 at 10:23 PM, Ilya Haykinson wrote:
> 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 ap
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
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
> 2010/3
2010/3/3 Martin Lukeš :
> 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 tran
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alright, I uploaded a german license with refs. Is there any way, I can
test, if everythin works?
- ---
Mit freundlichen Grüßen
Daniel Schury
Am 03.03.2010 18:25, schrieb Kevin Godby:
> On Wed, Mar 3, 2010 at 11:16 AM, Daniel Schu
On Wed, Mar 3, 2010 at 11:16 AM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Do you see that something is labeled? Or: If I want to set a ref to 2.b,
> but not 2.a, would there be an optical difference between the both, so
> that I would have to label every enumerati
I did the LaTeX conversion of the license... Feel free to change it, but
note that we should not change the way sections are numbered since the text
of the license often refers to sections by number, and we should not be
changing these.
-ilya
On Wed, Mar 3, 2010 at 8:28 AM, Kevin Godby wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Do you see that something is labeled? Or: If I want to set a ref to 2.b,
but not 2.a, would there be an optical difference between the both, so
that I would have to label every enumeration?
- ---
Mit freundlichen Grüßen
Daniel Schu
On Wed, Mar 3, 2010 at 10:17 AM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Alright. Little LaTex-Question: the license uses enumeration this way:
> 1.a.i But the manual uses only \begin{enumeration} for the first and
> second layer, not the third. Wouldn't it be ea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alright. Little LaTex-Question: the license uses enumeration this way:
1.a.i But the manual uses only \begin{enumeration} for the first and
second layer, not the third. Wouldn't it be easier, to do so for the
third too?
- ---
Mit f
On Wed, Mar 3, 2010 at 9:50 AM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>> So if the language you're translating into already has an
>> appropriately translated license on the CC site, then you don't have
>> to worry about translating the license.
>>
>> If you do n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> So if the language you're translating into already has an
> appropriately translated license on the CC site, then you don't have
> to worry about translating the license.
>
> If you do need to translate the license, create a new
> license-LANGCODE.t
Hello, Daniel.
On Wed, Mar 3, 2010 at 9:32 AM, Daniel Schury wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hey everybody,
>
> would it be possible, to use a local copy of the license in the branch
> instead of using launchpad for translation? Because the license already
> _is_ tran
31 matches
Mail list logo
