Difference between revisions of "Project leads finalize licenses and arrange technical requirements"
(→Creating the XHTML files) |
(→Transform the licenses) |
||
| (14 intermediate revisions by 4 users not shown) | |||
| Line 5: | Line 5: | ||
=Transform the licenses= | =Transform the licenses= | ||
| − | Once | + | Once CC, the Legal Project Lead, and the jurisdiction's community have agreed upon the license draft, then the Legal Lead will be responsible for transforming the BY-NC-SA license into the other five CC licenses: |
| − | * BY-NC-ND | + | * BY-NC-ND |
| − | |||
* BY-NC | * BY-NC | ||
* BY-ND | * BY-ND | ||
| Line 14: | Line 13: | ||
* BY | * BY | ||
| − | All of these licenses can be derived from the clauses contained in BY-NC-SA. | + | All of these licenses can be derived from the clauses contained in BY-NC-SA. CC has a guide to help with this process. |
| − | =Translate informational material= | + | =Translate informational material (where necessary)= |
| − | The Project Leads will also be responsible for coordinating the literal translation of CC | + | The Project Leads will also be responsible for coordinating the literal translation of CC's informational material (if necessary). If these documents are already translated into your jurisdiction?s first language, then you may also like to consider offering translations in other common languages in your region. Furthermore, you should read through all documents to ensure that the specifics of your jurisdiction are reflected in the translations. These documents include, but are not limited to: |
* FAQs | * FAQs | ||
| Line 25: | Line 24: | ||
* Disclaimer | * Disclaimer | ||
* Legal Concepts | * Legal Concepts | ||
| − | * | + | * [http://creativecommons.org/choose/ License Chooser] |
| − | * CC | + | * [[Documentation]] |
| + | * [http://support.creativecommons.org/videos/ CC videos] on [http://dotsub.com/view/search/?q=creative%20commons dotSUB for easy subtitle translation] | ||
| − | + | To get started please see our wiki page on [http://wiki.creativecommons.org/Translate#creativecommons.org Translating]. | |
=Creating the XHTML files= | =Creating the XHTML files= | ||
| Line 34: | Line 34: | ||
Next your team will need to prepare all 6 ported licenses as XHTML files. | Next your team will need to prepare all 6 ported licenses as XHTML files. | ||
| − | To create these files, | + | To create these files, it is probably best to use the respective Unported licenses as templates for your own. You can download the HTML for each Unported license by going to ''File -> Save Page as…'' and then select “Webpage, HTML only”, or whatever equivalent there is for your browser. It is highly recommended that you work with one license at a time, i.e. BY, BY-NC, BY-NC-SA. This will ensure that the paragraph numbering for each license remains correct. Although, do keep in mind that your ported licenses may differ in terms of quantity of sections and section numbering. |
| − | |||
| − | |||
| − | |||
| − | |||
In a text editor or HTML editor such as Dreamweaver, FrontPage, or Nvu, open each file you have saved. Copy and paste your appropriate license text over the previous one. Read through the HTML code and make sure that all references to language, jurisdiction, country code, etc. are modified to reflect your jurisdiction. | In a text editor or HTML editor such as Dreamweaver, FrontPage, or Nvu, open each file you have saved. Copy and paste your appropriate license text over the previous one. Read through the HTML code and make sure that all references to language, jurisdiction, country code, etc. are modified to reflect your jurisdiction. | ||
| Line 54: | Line 50: | ||
*by_3.0_nl.html | *by_3.0_nl.html | ||
| − | If your jurisdiction has more than one official language, please also include the language code in the file name: | + | If your jurisdiction has more than one official language and you plan to translate the legalcode into multiple languages, please also include the language code in the file name: |
[license-code]_[version]_[country code]_[language code].html | [license-code]_[version]_[country code]_[language code].html | ||
| − | Please ensure that all files are saved | + | Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default in virtually any modern operating system. |
| + | |||
| + | Please validate the XHTML using the W3C validator: [http://validator.w3.org]. We cannot publish the XHTML until it is valid, so if the validator returns errors, then you will need to work through them one by one until it validates. | ||
| − | Once you have completed the above steps, please send the six XHTML files to | + | Once you have completed the above steps, please send the six XHTML files to Nathan Kinkade. |
=Please note that no further changes will be possible once they have been published= | =Please note that no further changes will be possible once they have been published= | ||
Latest revision as of 22:14, 20 October 2011
Back to Worldwide Overview >> Step VII. CCi reviews second draft
Suggested Timeframe: one-two months
Contents
Transform the licenses
Once CC, the Legal Project Lead, and the jurisdiction's community have agreed upon the license draft, then the Legal Lead will be responsible for transforming the BY-NC-SA license into the other five CC licenses:
- BY-NC-ND
- BY-NC
- BY-ND
- BY-SA
- BY
All of these licenses can be derived from the clauses contained in BY-NC-SA. CC has a guide to help with this process.
Translate informational material (where necessary)
The Project Leads will also be responsible for coordinating the literal translation of CC's informational material (if necessary). If these documents are already translated into your jurisdiction?s first language, then you may also like to consider offering translations in other common languages in your region. Furthermore, you should read through all documents to ensure that the specifics of your jurisdiction are reflected in the translations. These documents include, but are not limited to:
- FAQs
- Commons Deed
- Trademark policy (other policies)
- Disclaimer
- Legal Concepts
- License Chooser
- Documentation
- CC videos on dotSUB for easy subtitle translation
To get started please see our wiki page on Translating.
Creating the XHTML files
Next your team will need to prepare all 6 ported licenses as XHTML files.
To create these files, it is probably best to use the respective Unported licenses as templates for your own. You can download the HTML for each Unported license by going to File -> Save Page as… and then select “Webpage, HTML only”, or whatever equivalent there is for your browser. It is highly recommended that you work with one license at a time, i.e. BY, BY-NC, BY-NC-SA. This will ensure that the paragraph numbering for each license remains correct. Although, do keep in mind that your ported licenses may differ in terms of quantity of sections and section numbering.
In a text editor or HTML editor such as Dreamweaver, FrontPage, or Nvu, open each file you have saved. Copy and paste your appropriate license text over the previous one. Read through the HTML code and make sure that all references to language, jurisdiction, country code, etc. are modified to reflect your jurisdiction.
Within the HTML editor, replace the old jurisdiction flag with your flag. 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]_[version]_[country code].html
Example of all six licenses (Netherlands):
- by-nc-nd_3.0_nl.html
- by-nc-sa_3.0_nl.html
- by-nc _3.0_nl.html
- by-nd_3.0_nl.html
- by-sa_3.0_nl.html
- by_3.0_nl.html
If your jurisdiction has more than one official language and you plan to translate the legalcode into multiple languages, please also include the language code in the file name:
[license-code]_[version]_[country code]_[language code].html
Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default in virtually any modern operating system.
Please validate the XHTML using the W3C validator: [1]. We cannot publish the XHTML until it is valid, so if the validator returns errors, then you will need to work through them one by one until it validates.
Once you have completed the above steps, please send the six XHTML files to Nathan Kinkade.
Please note that no further changes will be possible once they have been published
Next: Step X. Launch of the national version of the licenses
