Creative Commons - User contributions [en]

CCWiki:Users

2013-06-19T22:18:06Z

Base: Undo revision 55027 by MegaExplorer (talk)

See http://www.mediawiki.org/wiki/Project:Users for an explanation of this, although some details differ from what is described there.

User talk:Alex

2013-02-02T21:37:13Z

Base: /* Special:Contributions/Marasche40 */ new section

Thanks for restoring Monobook! [[User:Guaka|guaka]] 18:46, 4 October 2007 (EDT)

== [[Special:Contributions/Marasche40]] ==

and others. This wiki seems to be spam-rubbish bin. Could you clean it please? :) --[[User:Base|Base]] ([[User talk:Base|talk]]) 21:37, 2 February 2013 (UTC)

CCWiki talk:Translate

2013-02-02T21:12:00Z

Base: /* Extension:Translate */ new section

== Namespaces ==
In most instances [http://www.mediawiki.org/wiki/Help:Namespace namespaces] distinguish pages having different technical properties, handled differently by software, such as categories, images, or templates. Thus namespaces prefixes must more often than not be preserved in the translation process. That means, we should translate pages in the '''CC Wiki:''' namespace to ones in the same namespace, too. Thus I suggest to rename the pages already translated for this one.
--[[:USER:purodha|Purodha Blissenbach]] [[:USER TALK:purodha|(Discussion)]] 09:00, 19 October 2010 (UTC)
:I concur that the page Namespace should come before language prefixes. I moved existing translations of [[CC Wiki:Translate]] that do not conform to this, and updated the documentation to try and clarify that.--[[User:Nathan Yergler|Nathan]] 16:50, 19 October 2010 (UTC)

== Better Not Uppercasing the 1st Letters in Page Titles ==
The automatic uppercasing of the 1st letter in page titles can be switched off for a MediaWiki wiki or specific namespaces.[http://www.mediawiki.org/wiki/Manual:$wgCapitalLinks][http://www.mediawiki.org/wiki/Manual:$wgCapitalLinkOverrides]
Since uppercasing the 1st character in language code prefixes appears somewhat odd and inconvenient, I'd suggest to switch that off as soon as possible, and adjust documentation and translated pages accordingly.
--[[:USER:purodha|Purodha Blissenbach]] [[:USER TALK:purodha|(Discussion)]] 09:00, 19 October 2010 (UTC)
:If we stick to have initial capitals for original untranslated pages, a good side effect would be to have pages nicely sorted in [[Special:Allpages]], which we currently have not. --[[:USER:purodha|Purodha Blissenbach]] [[:USER TALK:purodha|(Discussion)]] 09:06, 19 October 2010 (UTC)

::I don't feel very strongly about this; don't understand the comment about sorting. --[[User:Nathan Yergler|Nathan]] 16:50, 19 October 2010 (UTC)

:::Well, pages of the same language are sorted together because the start with the same sequence of letters. Mediawiki sort puts uppercase letters together and lowercase letters together in two distinct blocks. If language prefixes are lower case as is the recommended standard, while original pages not having language prefixes have names starting with an uppercase character, also the untranslated pages are sorted together and not intermingled between the groups of translated pages. Now easier comprehensible? --[[:USER:purodha|Purodha Blissenbach]] [[:USER TALK:purodha|(Discussion)]] 01:45, 20 October 2010 (UTC)

== Translating Templates ==
Should we add an extra section on translating templates?
Several special precautions need to be taken, so as not to have <code>{<nowiki />{Translated From … }}</code> and similar stuff included in pages that use temples. The <code><noinclude></code> and/or <code><includeonly></code> and/or <code><onlyinclude></code> syntax and sematics need to be explained. I doubt, this would be suitable for general translators who are not programmers.
--[[:USER:purodha|Purodha Blissenbach]] [[:USER TALK:purodha|(Discussion)]] 09:00, 19 October 2010 (UTC)
:I'm not sure how to translate templates at all in a sane manner, especially since many of them are used for adding semantic mediawiki mark-up. This is an unfortunate downside to our use of prefixes for translations. I propose we add documentation advising against translation of templates. We're currently working on doing translation of [[Case Studies]]; it's possible that work will help us understand how translation of templates could work. --[[User:Nathan Yergler|Nathan]] 16:50, 19 October 2010 (UTC)

:: I do have ideas of translating templates. Best is to have as many templates as possible not requiring translation, however, since they do not contain displayed strings of translatable text.
:: It is a good idea to collect invariable strings in templates or subtemplates of their own. Such templates should usually not do much more than supplying a set of strings in one language as parameters to a stringless, and thus untranslated template. Then you only need to create more such very simple language specific templates when translating.
:: --[[:USER:purodha|Purodha Blissenbach]] [[:USER TALK:purodha|(Discussion)]] 02:03, 20 October 2010 (UTC)

== Extension:Translate ==

How about enabling [//www.mediawiki.org/wiki/Extension:Translate Extension:Translate] in this wiki? It is quite good for translating wikipages. But it require some volunteers to manage translatable pages. --[[User:Base|Base]] ([[User talk:Base|talk]]) 21:12, 2 February 2013 (UTC)

Translating CC Deeds

2013-02-02T20:25:36Z

Base: Undo revision 58557 by Nicolas23 (talk)

The license engine, deeds and legal code hosted at creativecommons.org are all translated directly by CC [http://creativecommons.org/international/ jurisdiction partner institutions]. While there are usually people at the partner institutions who handle these translations, you can request to become a member of the translation team for any given language using the directions below under '''For Translators'''.

Creative Commons uses [http://www.transifex.net Transifex.net] to manage translations for the web site and our open source software projects. Information on translating using [[Translating PO Files|gettext and poEdit]] is also available.

=== For CC Project Leads ===
To set up translations for your jurisdiction's language(s), please:
# Select one or more people to manage your translations
# Each translator should create an account as described below

=== For Translators ===
To translate to the language that interests you, please:
# Go to [http://www.transifex.net/accounts/register/ Transifex.net] and create an account. Once you have validated your email address, log in.
# Go to the [http://www.transifex.net/projects/p/CC/teams/ Translation Teams] tab for the Creative Commons project.
#* If a team already exists for the language that interestes you, then click on that language and then click the "Join this team" button, which will allow you to send a message to the coordinator for that language asking then to allow you to become a member of that team.
#* If a team doesn't yet exist for the language that interests you then simply click the "Request a new team" button at the bottom of the list of available teams. This will send an email to the administrator for the Creative Commons project requesting the new team.

=== General Notes About Translating ===

==== How to handle ${} or %() in strings ====

When you see "${license_name}" or "%(license_name)s" in a string, that indicates a substitution (for the real license name). These are placeholders that the translation machinery uses; if you modify this placeholder, the real license name will never be substituted into your string.

As a result, '''DO NOT''':

* Translate the text ("license_name") into your own language
* Remove the text
* Reverse the order of characters because you have a right-to-left language (ie, "{license_name}$")
* If the text uses the %(), do not remove the trailing character after the close of the parenthesis (i.e. the 's' in "%(license_name)s")

==== HTML links in strings (i.e., <a href="[someurl]">[sometext]</a>) ====

When you encounter an HTML link in a string, you must not translate anything inside of the angle brackets. In the example above, you would '''only''' translate ''[sometext]'', and the rest must be carried into the translation without any changes.

==== Whitespace Characters ====

Sometimes you'll see <code>\t</code> or <code>\n</code> in strings. These are left-over from the source files and can be safely omitted.

==== Wiki Links ====

Some text contains links to the CC Wiki for more information (ie, issues surrounding fair use, public domain, etc). If you would like to translate those pages in the CC Wiki, you may do so and substitute the link to the translated page in the translation. See [[CC Wiki:Translate]] for instructions on translating wiki pages.

[[Category:Translation Project]]

==== When Does The Server Get Updated? ====

'''<tt>staging.creativecommons.org</tt>''' is updated with the newest translations every 15 minutes.

The live site however is updated manually. Updates get pushed periodically with other software updates. If you would like to have your translations updated at any time, email <tt>webmaster AT creativecommons DOT org</tt>.

{{Translations
| articles = Pt:Traduzir os Resumos Para Leigos CC
}}