Translating with Pootle/Administration - Revision history

Nkinkade at 14:59, 30 April 2010

2010-04-30T14:59:19Z

2009-12-10T20:46:58Z

‎New string: (3) Make new string(s) available to Pootle

2009-12-10T20:21:25Z

‎New language: (2) in Pootle

2009-04-14T23:12:50Z

‎New string: (2) sync

2009-02-18T23:24:43Z

‎New language: (2) in Pootle

2009-02-18T23:24:30Z

‎New string: (3) Make new string(s) available to Pootle

2009-02-18T23:08:58Z

2009-02-17T22:10:41Z

‎New string: (3) Make new string(s) available to Pootle

2008-11-18T22:42:45Z

‎Change an English string

2008-11-18T22:29:59Z

‎Change an English string

← Older revision		Revision as of 14:59, 30 April 2010
Line 9:		Line 9:

	'''<span style='color: red'>Note: most of this is relative to the project creativecommons.org and may or may not apply to other projects.</span>'''		'''<span style='color: red'>Note: most of this is relative to the project creativecommons.org and may or may not apply to other projects.</span>'''
		+
		+	<h3>NOTE: to avoid '''conflicts''' when merging your changes into the pootle checkout it is recommended to do the following before anything else:</h3>
		+	<pre>
		+	$ ssh translate.creativecommons.org
		+	$ sudo su - pootle
		+	$ cd ~/checkouts/$project/cc-i18n-trunk
		+	$ svn ci -m "Committing any pending changes before making changes to the PO files."
		+	</pre>
		+	... then update your local checkout before doing any of the operations below.

	== Fully-prepared checkout ==		== Fully-prepared checkout ==

@@ Line 44: / Line 44: @@
 $ ssh translate.creativecommons.org
 $ sudo su - pootle
-$ cd ~pootle/pootle/Pootle/po/[project dir - usually cc_org]
+$ cd ~/checkouts/$project/cc-i18n-trunk
 $ svn up
 </pre>

@@ Line 77: / Line 77: @@
 $ ssh translate.creativecommons.org
 $ sudo su - pootle
-$ cd ~pootle/pootle/Pootle/po/cc_org/
+$ cd ~/checkouts/cc_org/cc-i18n-trunk
 $ svn up i18n/es_PR po/es_PR
 </pre>

@@ Line 35: / Line 35: @@
   $ ./bin/sync
-Once you have added your new string(s) you must run ./bin/sync with no arguments.  This will propagate the new string(s) to all of the English-key PO files. Commit the many changes which should be visible in the ./i18n/trunk/po/ directory.
+Once you have added your new string(s) you must run ./bin/sync with no arguments.  This will propagate the new string(s) to all of the English-key PO files. Running po2cc with those arguments will push those changes into the CC-style, short-name-key PO fies. Commit the many changes which should be visible in the '''po/''' and '''i18n/''' directories.
 === New string: (3) Make new string(s) available to Pootle ===

@@ Line 75: / Line 75: @@
 <pre>
 $ ssh translate.creativecommons.org
 $ cd ~pootle/pootle/Pootle/po/cc_org/
 $ svn up i18n/es_PR po/es_PR

@@ Line 42: / Line 42: @@
 <pre>
 $ ssh translate.creativecommons.org
-$ cd /var/www/translate.creativecommons.org/po/
+$ cd /var/www/translate.creativecommons.org/po/[project dir - usually cc_org]
 $ svn up
 </pre>

← Older revision		Revision as of 22:42, 18 November 2008
Line 91:		Line 91:

	Changing an English string is done precisely like '''Adding a new string''', with the exception that you modify an existing string in ./i18n/trunk/master/cc_org.po instead of adding a new one.		Changing an English string is done precisely like '''Adding a new string''', with the exception that you modify an existing string in ./i18n/trunk/master/cc_org.po instead of adding a new one.
		+
		+	=== Future dreaming ===
		+
		+	Having changed this English string, run ./bin/sync. This will go through the PO-style PO files and, if translations for a string with that as context exist, either:
		+	* Migrate the translation to the new English value, or
		+	* Move the translation out of the PO-style file into the suggestions file, and delete the translation from the PO-style file
		+
		+	I think the second is the better option.

	== Documentation ==		== Documentation ==

← Older revision		Revision as of 22:29, 18 November 2008
Line 91:		Line 91:

	Changing an English string is done precisely like '''Adding a new string''', with the exception that you modify an existing string in ./i18n/trunk/master/cc_org.po instead of adding a new one.		Changing an English string is done precisely like '''Adding a new string''', with the exception that you modify an existing string in ./i18n/trunk/master/cc_org.po instead of adding a new one.
		+
		+	== Documentation ==
		+
		+	=== Fallback ===
		+
		+	* ?!