CC0 translation guide - Revision history

Kat Walsh: #REDIRECT Legal tools translation guide

2014-06-13T17:03:19Z

← Older revision		Revision as of 17:03, 13 June 2014
Line 1:		Line 1:
	~~Here are some general issues and things to watch for as you are preparing translations of CC0.~~		#REDIRECT [[Legal tools translation guide]]

	~~==General Issues==~~
	~~As with all license translations: check that all substantive clauses are included, cross-references correct, headings correct and aligned with the source version, spelling and grammar correct.~~

	~~Heading: "CC0 1.0 Universal"~~

	~~Check the connecting words in the document: "and" and "or" in English should line up with words with corresponding meaning in the translation.~~

	All translation files must include the boxes indicating the availability of other languages. Those who began translating this tool before the boxes were present on the English version should find the current file on the Creative Commons website to use as a template. Please note that if you are translating from English, you should also include English on the "in other languages" box!

	~~In paragraphs 2 and 3, subsections i-iv should use the same wording in each place where the English text is also identical, unless there is a particular reason for them to be different.~~

	The English version states that CC0 is "associated with" or "applied to" the work. Translations should choose words that convey that this is being done by an Affirmer who has authority to apply CC0 to the work.

	~~If there is a Europeana translation for your language, please refer to it and note any important differences in your worksheet.~~

	~~==Key Words==~~
	These words are most important to determining the meaning of the document. Please let us know if you have any questions around how to translate these words (particularly if there is not an exact translation, if the English meaning is not clear to you, or if the difference between the key word and other similar terms is not clear to you).

	* "Copyright and Related Rights"
	** Note that this is a different phrase than the language in 4.0 for "Copyright and Similar Rights"--these are not identical in scope and should probably be different in most translations.
	* "Work"
	* "Affirmer"
	* "License"
	* "Waiver"

	"Statement of Purpose": this should be referred to as a proper name everywhere in the document, with the same wording that is used in the first section heading. It must be clear that references elsewhere in the text mean the "Statement of Purpose" section of the document, not simply any statement of purpose.

	~~==Creating the files==~~
	To create the HTML files, we recommend using the English legal code pages as templates for your own. You can download the HTML for each license by going to File -> Save Page as… and then select “Webpage, HTML only”, or whatever equivalent there is for your browser. In a text editor or HTML editor, open each file you have saved. Copy and paste your appropriate license text over the previous text, being careful not to copy over the existing HTML tags. Check and re-check the code to ensure that there are no mistakes. Then save each file separately according to the following convention:

	~~zero_1.0_[language code].html~~

	~~For example, "zero_1.0_fr.html" would be for the French translation.~~

	~~Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Once you have completed the above steps and relevant processes in the~~ [[~~legal code~~ translation ~~policy]], please send the XHTML file to legal@creativecommons.org along with your report of drafting issues you encountered.~~

	~~[[Category:CC0]]~~
	~~[[Category:Translation~~]]

Kat Walsh: note to include English in other languages box

2014-05-12T17:44:48Z

note to include English in other languages box

← Older revision		Revision as of 17:44, 12 May 2014
Line 8:		Line 8:
	Check the connecting words in the document: "and" and "or" in English should line up with words with corresponding meaning in the translation.		Check the connecting words in the document: "and" and "or" in English should line up with words with corresponding meaning in the translation.

	All translation files must include the boxes indicating the availability of other languages. Those who began translating this tool before the boxes were present on the English version should find the current file on the Creative Commons website to use as a template.		All translation files must include the boxes indicating the availability of other languages. Those who began translating this tool before the boxes were present on the English version should find the current file on the Creative Commons website to use as a template. Please note that if you are translating from English, you should also include English on the "in other languages" box!

	In paragraphs 2 and 3, subsections i-iv should use the same wording in each place where the English text is also identical, unless there is a particular reason for them to be different.		In paragraphs 2 and 3, subsections i-iv should use the same wording in each place where the English text is also identical, unless there is a particular reason for them to be different.

Kat Walsh: /* General Issues */ note Europeana

2014-04-03T00:42:32Z

General Issues: note Europeana

← Older revision		Revision as of 00:42, 3 April 2014
Line 13:		Line 13:

	The English version states that CC0 is "associated with" or "applied to" the work. Translations should choose words that convey that this is being done by an Affirmer who has authority to apply CC0 to the work.		The English version states that CC0 is "associated with" or "applied to" the work. Translations should choose words that convey that this is being done by an Affirmer who has authority to apply CC0 to the work.

			If there is a Europeana translation for your language, please refer to it and note any important differences in your worksheet.

	==Key Words==		==Key Words==

Kat Walsh: /* Key Words */ note on copyright and related rights

2014-03-25T20:36:05Z

Key Words: note on copyright and related rights

← Older revision		Revision as of 20:36, 25 March 2014
Line 18:		Line 18:

	* "Copyright and Related Rights"		* "Copyright and Related Rights"
			** Note that this is a different phrase than the language in 4.0 for "Copyright and Similar Rights"--these are not identical in scope and should probably be different in most translations.
	* "Work"		* "Work"
	* "Affirmer"		* "Affirmer"

Kat Walsh: /* General Issues */ change for translation boxes, not disclaimer

2014-03-25T20:29:19Z

General Issues: change for translation boxes, not disclaimer

← Older revision		Revision as of 20:29, 25 March 2014
Line 8:		Line 8:
	Check the connecting words in the document: "and" and "or" in English should line up with words with corresponding meaning in the translation.		Check the connecting words in the document: "and" and "or" in English should line up with words with corresponding meaning in the translation.

	All ~~translations~~ must include the ~~disclaimer as listed on~~ the ~~[[Legal Code Translation Policy\|translation policy page]]~~. ~~The disclaimer stating that~~ the ~~document is an official translation should be clear that it is an official language translation, not simply for a single jurisdiction. This may require additional words to clarify. (For example, if~~ English ~~were a translated~~ version~~, it would be~~ the ~~"Official English-language translation", rather than~~ the ~~"Official English translation", which might imply that it was specific~~ to ~~England~~.)		All translation files must include the boxes indicating the availability of other languages. Those who began translating this tool before the boxes were present on the English version should find the current file on the Creative Commons website to use as a template.

	In paragraphs 2 and 3, subsections i-iv should use the same wording in each place where the English text is also identical, unless there is a particular reason for them to be different.		In paragraphs 2 and 3, subsections i-iv should use the same wording in each place where the English text is also identical, unless there is a particular reason for them to be different.

Kat Walsh: /* Creating the files */ update file naming convention

2014-02-12T01:04:50Z

Creating the files: update file naming convention

← Older revision		Revision as of 01:04, 12 February 2014
Line 28:		Line 28:
	To create the HTML files, we recommend using the English legal code pages as templates for your own. You can download the HTML for each license by going to File -> Save Page as… and then select “Webpage, HTML only”, or whatever equivalent there is for your browser. In a text editor or HTML editor, open each file you have saved. Copy and paste your appropriate license text over the previous text, being careful not to copy over the existing HTML tags. Check and re-check the code to ensure that there are no mistakes. Then save each file separately according to the following convention:		To create the HTML files, we recommend using the English legal code pages as templates for your own. You can download the HTML for each license by going to File -> Save Page as… and then select “Webpage, HTML only”, or whatever equivalent there is for your browser. In a text editor or HTML editor, open each file you have saved. Copy and paste your appropriate license text over the previous text, being careful not to copy over the existing HTML tags. Check and re-check the code to ensure that there are no mistakes. Then save each file separately according to the following convention:

	~~[license-code]_~~[language code].html		zero_1.0_[language code].html

	For example, "~~cc0_nl~~.html" would be for the ~~Dutch~~ translation.		For example, "zero_1.0_fr.html" would be for the French translation.

	Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Once you have completed the above steps and relevant processes in the [[legal code translation policy]], please send the XHTML file to legal@creativecommons.org along with your report of drafting issues you encountered.		Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Once you have completed the above steps and relevant processes in the [[legal code translation policy]], please send the XHTML file to legal@creativecommons.org along with your report of drafting issues you encountered.

Kat Walsh: /* Creating the files */ formatting

2014-02-04T01:08:29Z

Creating the files: formatting

← Older revision		Revision as of 01:08, 4 February 2014
Line 30:		Line 30:
	[license-code]_[language code].html		[license-code]_[language code].html

	~~Example (Dutch):~~		For example, "cc0_nl.html" would be for the Dutch translation.

	cc0_nl.html

	Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Once you have completed the above steps and relevant processes in the [[legal code translation policy]], please send the XHTML file to legal@creativecommons.org along with your report of drafting issues you encountered.		Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Once you have completed the above steps and relevant processes in the [[legal code translation policy]], please send the XHTML file to legal@creativecommons.org along with your report of drafting issues you encountered.

Kat Walsh: add file creation section

2014-02-04T01:05:45Z

add file creation section

← Older revision		Revision as of 01:05, 4 February 2014
Line 25:		Line 25:
	"Statement of Purpose": this should be referred to as a proper name everywhere in the document, with the same wording that is used in the first section heading. It must be clear that references elsewhere in the text mean the "Statement of Purpose" section of the document, not simply any statement of purpose.		"Statement of Purpose": this should be referred to as a proper name everywhere in the document, with the same wording that is used in the first section heading. It must be clear that references elsewhere in the text mean the "Statement of Purpose" section of the document, not simply any statement of purpose.

			==Creating the files==
			To create the HTML files, we recommend using the English legal code pages as templates for your own. You can download the HTML for each license by going to File -> Save Page as… and then select “Webpage, HTML only”, or whatever equivalent there is for your browser. In a text editor or HTML editor, open each file you have saved. Copy and paste your appropriate license text over the previous text, being careful not to copy over the existing HTML tags. Check and re-check the code to ensure that there are no mistakes. Then save each file separately according to the following convention:

			[license-code]_[language code].html

			Example (Dutch):

			cc0_nl.html

			Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Once you have completed the above steps and relevant processes in the [[legal code translation policy]], please send the XHTML file to legal@creativecommons.org along with your report of drafting issues you encountered.

	[[Category:CC0]]		[[Category:CC0]]
	[[Category:Translation]]		[[Category:Translation]]

Kat Walsh: new page

2013-12-09T18:42:39Z

new page

New page

Here are some general issues and things to watch for as you are preparing translations of CC0.

==General Issues==
As with all license translations: check that all substantive clauses are included, cross-references correct, headings correct and aligned with the source version, spelling and grammar correct.

Heading: "CC0 1.0 Universal"

Check the connecting words in the document: "and" and "or" in English should line up with words with corresponding meaning in the translation.

All translations must include the disclaimer as listed on the [[Legal Code Translation Policy|translation policy page]]. The disclaimer stating that the document is an official translation should be clear that it is an official language translation, not simply for a single jurisdiction. This may require additional words to clarify. (For example, if English were a translated version, it would be the "Official English-language translation", rather than the "Official English translation", which might imply that it was specific to England.)

In paragraphs 2 and 3, subsections i-iv should use the same wording in each place where the English text is also identical, unless there is a particular reason for them to be different.

The English version states that CC0 is "associated with" or "applied to" the work. Translations should choose words that convey that this is being done by an Affirmer who has authority to apply CC0 to the work.

==Key Words==
These words are most important to determining the meaning of the document. Please let us know if you have any questions around how to translate these words (particularly if there is not an exact translation, if the English meaning is not clear to you, or if the difference between the key word and other similar terms is not clear to you).

* "Copyright and Related Rights"
* "Work"
* "Affirmer"
* "License"
* "Waiver"

"Statement of Purpose": this should be referred to as a proper name everywhere in the document, with the same wording that is used in the first section heading. It must be clear that references elsewhere in the text mean the "Statement of Purpose" section of the document, not simply any statement of purpose.

[[Category:CC0]]
[[Category:Translation]]