Translating ccHost - Revision history

Nathan Yergler: Redirecting to Translate

2007-10-04T16:59:50Z

Redirecting to Translate

Dbl2010: header levels fixed

2006-08-10T18:19:51Z

header levels fixed

Jon Phillips: /* Method 1 (preferred):Using GNU gettext tools */

2006-06-23T13:30:46Z

‎Method 1 (preferred):Using GNU gettext tools

Jon Phillips: /* Updating Translations */

2006-06-23T13:29:03Z

‎Updating Translations

Jon Phillips: /* Using poEdit */

2006-06-23T13:24:58Z

‎Using poEdit

Jon Phillips: /* Submitting a Translation */

2006-06-23T13:22:24Z

‎Submitting a Translation

Jon Phillips: /* Create a locale subdirectory for your new translation */

2006-06-23T13:20:24Z

‎Create a locale subdirectory for your new translation

Jon Phillips: /* Method 1: Creating A Translation on Commandline */

2006-06-23T13:15:31Z

‎Method 1: Creating A Translation on Commandline

Jon Phillips at 05:37, 23 June 2006

2006-06-23T05:37:48Z

Jon Phillips at 05:30, 23 June 2006

2006-06-23T05:30:20Z

← Older revision		Revision as of 16:59, 4 October 2007
Line 1:		Line 1:
−	~~[[Category:CcHost]]~~	+	#REDIRECT [[Translate]]
−	~~[[Category:Developer]]~~
−	~~[[Category:i18n]]~~
−
−	~~''Also see [[ccHost Localization]].''~~
−
−	This document describes the procedures used to create and maintain translations for ccHost, a web-based media sharing software (that powers ccMixter.org and other sites). If you are used to the standard translation system in Free and Open Source Software, translation work on ccHost is very similar (and uses the same tools). For those of you that are not familiar with translations, this document is really aimed at you.
−
−	~~== Supported Languages ==~~
−
−	The latest development versions of [[ccHost]] include support for multiple languagues. Depending on who from the community submits languages, the make-up of the project will be different. We need your help in adding more languages to ccHost!
−
−	~~Anyone wishing to assist should sign up on the [http://lists.sourceforge.net/mailman/listinfo/cctools-cchost ccHost] mailing list and poke around on these projects.~~
−
−	~~== Getting Started ==~~
−
−	Translations for ccHost are stored in gettext message catalogs. Message catalogs are text files which associate translated strings with identifiers used by the application. Each string to be translated is referred to as a "message". The [http://lists.sourceforge.net/mailman/listinfo/cctools-cchost cctools] mailing list is used for managing translations for ccHost. If you are translating ccHost into a new language, you are encouraged to join this list. The addition of new messages to be translated will be announced there, and you may ask questions on the list regarding internationalization. The availability of new message catalogs will also be announced on that list.
−
−	~~=== Method 1: Creating A Translation on Commandline (Unix/Linux/Mac OS X) ===~~
−
−	First, install [[ccHost]] onto your web server. When translating ccHost there is one file which must be generated, copied and edited. The translation files are located in the <code>locale/default</code> subdirectory inside of a ccHost installation. Use the following instructions to create a new translation for ccHost; these instructions are for translating ccHost to the fictional "ya" locale and assume a Linux development environment.
−
−	~~==== Generate and Create a locale subdirectory for your new translation ====~~
−	~~<pre>~~
−	~~$ make~~
−	~~$ cd locale/default~~
−	~~$ mkdir ya~~
−	~~$ mkdir ya/LC_MESSAGES~~
−	~~</pre>~~
−
−	~~==== Copy the template files into the new directory ====~~
−	~~<pre>~~
−	~~$ cp cchost.pot ya/LC_MESSAGES/cchost.po~~
−	~~</pre>~~
−	~~==== Edit the new files with the translated content. ====~~
−	~~Two areas need editing: 1.) the header information and 2.) the messages.~~
−
−	~~===== headers information =====~~
−	* The header information should be updated with the translator's contact information, email address and the character set used. The character set should usually be <code>utf-8</code>.
−
−	~~===== messages =====~~
−
−	* Each message is defined by two lines; the translated content goes between the quotes on the <code>msgstr</code> line. The <code>msgid</code> line '''must not be changed'''.
−	~~<pre>~~
−	~~...~~
−	~~msgid "OK"~~
−	~~msgstr ""~~
−	~~...~~
−	~~</pre>~~
−	* You may encounter strings such as <code>"The file %s can not be found."</code>; the <code>%s</code> should be left intact, as ccHost will substitute the actual piece of information at run time.
−
−	~~=== Method 2: Translating using Development Build POT file ===~~
−
−	~~''NOTE: This is the fastest way to get up and running with translating ccHost''~~
−
−	~~Download the latest build of the master POT file which contains all strings for ccHost:~~
−
−	~~<pre>~~
−	~~http://mirrors.creativecommons.org/cchost/cchost.pot~~
−	~~</pre>~~
−
−	~~From here, one can then pick up step 2 of method 1 above.~~
−
−	~~=== Method 3: Translating using poEdit ===~~
−
−	[http://www.poedit.org/ poEdit] is an Open Source cross-platform gettext catalog (.po files) editor. It is built with wxWidgets toolkit and can run on any platform supported by it. It aims to provide more convenient approach to editing catalogs than launching Notepad (or vi) and editing the file by hand. Official releases are available from the poEdit web site for Windows and Linux. An alpha for Mac OS X is available at http://www.poedit.org/files/poedit-1.3.4-alpha.dmg. The poEdit team reports it is an early alpha, but some translators have had success using it for [[ccPublisher]] (another Creative Commons project).
−
−	~~Just use poEdit's '''File''' -> '''New catalog from POT file...''' function will easily doing so. It even can compile .po into .mo file in the same time you pressing '''Save'''.~~
−
−	~~=== Method 4: Translating under Windows ===~~
−
−	~~''NOTE: The [[[Translating_ccPublisher~~#~~Translating_under_Windows\|following graphical windows]] use the excellent [[ccPublisher]]. The ideas though are easily remapped to [[ccHost]].''~~
−
−	To translate under Windows, download and install a ccHost 2.9 or greater release. In the installation directory you will find a the directory ''locale''' which contains the subdirectory '''default'''. Create a new subdirectory under '''locale/default''' with a name matching your new locale. For example, to translate ccHost into French, create a directory named <code>fr_FR</code>.
−
−	~~[[Image:Locale_folder_thumb.png\|frame\|The ccPublisher locale folder ([[:Image:Locale_folder.png\|full size]]).]]~~
−
−	~~Copy the template files from '''locale/default''' into your new directory; rename them from .pot to .po.~~
−
−	~~[[Image:Fr_FR_thumb.png\|frame\|The .po files for the new locale ([[:Image:Fr_FR.png\|full size]]).]]~~
−
−	~~Edit each .po file per the instructions above.~~
−
−	~~[[Image:Edit_thumb.png\|frame\|Editing the .po file ([[:Image:Edit.png\|full size]]).]]~~
−
−	~~If you are translating ccHost to your default locale, simply run ccHost to test your translation.~~
−
−	~~[[Image:Edit_shortcut_thumb.png\|frame\|Editting a shortcut to ccp.exe to specify a locale ([[:Image:Edit_shortcut.png\|full size]]).]]~~
−
−
−	~~[[Image:CcPublisher_fr_thumb.png\|frame\|ccPublisher running with the French locale specified; note the File menu reflects the change to Dossier ([[:Image:CcPublisher_fr.png\|full size]]).]]~~
−
−	~~== Submitting a Translation ==~~
−
−	Once you have completed or updated a translation and tested it, you can submit it to the ccHost developers using the ccTools [http://sourceforge.net/tracker/?group_id=80503&atid=559968 patch trackers]. Add the locale information for your new translation to the title and attach the .po file(s) you created (either individually or in a zip/tar file).
−
−	~~== Updating Translations ==~~
−
−	~~Strings are sometimes added or removed from the application during development cycles. At those times it is necessary to update the translation (.po) files with the new strings and translations.~~
−
−
−	~~=== Method 1: Using GNU gettext tools ===~~
−
−	Constructing an updated POT file, .po files, and .mo files (binary version of the .po files) is pretty simple on Unix-like systems (mac/linux/etc). Once you are in the main folder of where ccHost is installed. From commandline enter:
−
−	~~<pre>~~
−	~~$ make~~
−	~~</pre>~~
−
−	This automatically takes care of updating strings on languages, merging changes, etc. It also generates a new clean cchost.pot which can be used as a master file for creating future translations. And finally, it generates the binary .mo files which are per-language which ccHost uses for speedy delivery of different translations.
−
−	~~=== Method 2: Using poEdit ===~~
−
−	If you are using [http://poedit.org poEdit], you can use the '''Update from POT file...''' option. Go to the '''Catalog''' menu and select '''Update from POT file...'''. Select the .pot file which corresponds to the translation you have open (i.e. if you are updating cchost.po, select cchost.pot).
−
−	~~''NOTE: The graphical images depict this similar process using [[ccPublisher]]. The ideas are easily remapped to [[ccHost]].~~
−
−	~~[[Image:Poedit_select_catalog_template.png]]~~
−
−	~~poEdit will display the new strings it will add, as well as the obsolete strings it will remove.~~
−
−	[[~~Image:Poedit_approve_updates.png~~]]
−
−	~~== Known Issues ==~~
−
−	* XML pages need translation.
−	** Currently only strings php and inc files are correctly identified and set up for translation.
−	* Auto-detection
−	** There needs to be auto-detection of languages at installation and first session installation.

@@ Line 17: / Line 17: @@
 Translations for ccHost are stored in gettext message catalogs.  Message catalogs are text files which associate translated strings with identifiers used by the application.  Each string to be translated is referred to as a "message".  The [http://lists.sourceforge.net/mailman/listinfo/cctools-cchost cctools] mailing list is used for managing translations for ccHost.  If you are translating ccHost into a new language, you are encouraged to join this list.  The addition of new messages to be translated will be announced there, and you may ask questions on the list regarding internationalization.  The availability of new message catalogs will also be announced on that list.
-== Method 1: Creating A Translation on Commandline (Unix/Linux/Mac OS X) ==
+=== Method 1: Creating A Translation on Commandline (Unix/Linux/Mac OS X) ===
 First, install [[ccHost]] onto your web server. When translating ccHost there is one file which must be generated, copied and edited. The translation files are located in the <code>locale/default</code> subdirectory inside of a ccHost installation.  Use the following instructions to create a new translation for ccHost; these instructions are for translating ccHost to the fictional "ya" locale and assume a Linux development environment.
-=== Generate and Create a locale subdirectory for your new translation ===
+==== Generate and Create a locale subdirectory for your new translation ====
 <pre>
    $ make
@@ Line 29: / Line 29: @@
 </pre>
-=== Copy the template files into the new directory ===
+==== Copy the template files into the new directory ====
 <pre>
    $ cp cchost.pot ya/LC_MESSAGES/cchost.po
 </pre>
-=== Edit the new files with the translated content.  ===
+==== Edit the new files with the translated content.  ====
 Two areas need editing: 1.) the header information and 2.) the messages.
-==== headers information ====
+===== headers information =====
 * The header information should be updated with the translator's contact information, email address and the character set used.  The character set should usually be <code>utf-8</code>.
-==== messages ====
+===== messages =====
 * Each message is defined by two lines; the translated content goes between the quotes on the <code>msgstr</code> line.  The <code>msgid</code> line '''must not be changed'''.

@@ Line 100: / Line 100: @@
-=== Method 1 (preferred):Using GNU gettext tools ===
+=== Method 1: Using GNU gettext tools ===
 Constructing an updated POT file, .po files, and .mo files (binary version of the .po files) is pretty simple on Unix-like systems (mac/linux/etc). Once you are in the main folder of where ccHost is installed. From commandline enter:
@@ Line 109: / Line 109: @@
 This automatically takes care of updating strings on languages, merging changes, etc. It also generates a new clean cchost.pot which can be used as a master file for creating future translations. And finally, it generates the binary .mo files which are per-language which ccHost uses for speedy delivery of different translations.
 === Method 2: Using poEdit ===

@@ Line 99: / Line 99: @@
 Strings are sometimes added or removed from the application during development cycles.  At those times it is necessary to update the translation (.po) files with the new strings and translations.
 === Using poEdit ===
 If you are using [http://poedit.org poEdit], you can use the '''Update from POT file...''' option.  Go to the '''Catalog''' menu and select '''Update from POT file...'''.  Select the .pot file which corresponds to the translation you have open (i.e. if you are updating cchost.po, select cchost.pot).
@@ Line 110: / Line 122: @@
 [[Image:Poedit_approve_updates.png]]
 == Known Issues ==

@@ Line 101: / Line 101: @@
 === Using poEdit ===
-If you are using [http://poedit.org poEdit], you can use the '''Update from POT file...''' option.  Go to the '''Catalog''' menu and select '''Update from POT file...'''.  Select the .pot file which cooresponds to the translation you have open (i.e. if you are updating cchost.po, select cchost.pot).
+If you are using [http://poedit.org poEdit], you can use the '''Update from POT file...''' option.  Go to the '''Catalog''' menu and select '''Update from POT file...'''.  Select the .pot file which corresponds to the translation you have open (i.e. if you are updating cchost.po, select cchost.pot).
 [[Image:Poedit_select_catalog_template.png]]

@@ Line 93: / Line 93: @@
 == Submitting a Translation ==
-Once you have completed or updated a translation and tested it, you can submit it to the ccHost developers using the ccTools [http://sourceforge.net/tracker/?group_id=80503&atid=559968 patch trackers].  Add the locale information for your new translation to the title and attach the .po and .html files you created (either individually or in a zip/tar file).
+Once you have completed or updated a translation and tested it, you can submit it to the ccHost developers using the ccTools [http://sourceforge.net/tracker/?group_id=80503&atid=559968 patch trackers].  Add the locale information for your new translation to the title and attach the .po file(s) you created (either individually or in a zip/tar file).
 == Updating Translations ==

@@ Line 21: / Line 21: @@
 First, install [[ccHost]] onto your web server. When translating ccHost there is one file which must be generated, copied and edited. The translation files are located in the <code>locale/default</code> subdirectory inside of a ccHost installation.  Use the following instructions to create a new translation for ccHost; these instructions are for translating ccHost to the fictional "ya" locale and assume a Linux development environment.
-=== Create a locale subdirectory for your new translation ===
+=== Generate and Create a locale subdirectory for your new translation ===
 <pre>
    $ make
@@ Line 28: / Line 28: @@
    $ mkdir ya/LC_MESSAGES
 </pre>
 === Copy the template files into the new directory ===
 <pre>

@@ Line 17: / Line 17: @@
 Translations for ccHost are stored in gettext message catalogs.  Message catalogs are text files which associate translated strings with identifiers used by the application.  Each string to be translated is referred to as a "message".  The [http://lists.sourceforge.net/mailman/listinfo/cctools-cchost cctools] mailing list is used for managing translations for ccHost.  If you are translating ccHost into a new language, you are encouraged to join this list.  The addition of new messages to be translated will be announced there, and you may ask questions on the list regarding internationalization.  The availability of new message catalogs will also be announced on that list.
-== Method 1: Creating A Translation on Commandline ==
+== Method 1: Creating A Translation on Commandline (Unix/Linux/Mac OS X) ==
-First, install [[ccHost]] onto your web server. When translating ccHost there is one file which must be copied and edited. The translation resources are located in the <code>locale/default</code> subdirectory inside of a ccHost installation.  Use the following instructions to create a new translation for ccHost; these instructions are for translating ccHost to the fictional "ya" locale and assume a Linux development environment.
+First, install [[ccHost]] onto your web server. When translating ccHost there is one file which must be generated, copied and edited. The translation files are located in the <code>locale/default</code> subdirectory inside of a ccHost installation.  Use the following instructions to create a new translation for ccHost; these instructions are for translating ccHost to the fictional "ya" locale and assume a Linux development environment.
-* Create a locale subdirectory for your new translation
+=== Create a locale subdirectory for your new translation ===
    $ cd locale/default
    $ mkdir ya
    $ mkdir ya/LC_MESSAGES
-* Copy the template files into the new directory
+</pre>
    $ cp cchost.pot ya/LC_MESSAGES/cchost.po
-* Edit the new files with the translated content.  Two areas need editing: 1.) the header information and 2.) the messages.
+</pre>
-** The header information should be updated with the translator's contact information, email address and the character set used.  The character set should usually be <code>utf-8</code>.
+=== Edit the new files with the translated content.  ===
-** Each message is defined by two lines; the translated content goes between the quotes on the <code>msgstr</code> line.  The <code>msgid</code> line '''must not be changed'''.
+Two areas need editing: 1.) the header information and 2.) the messages.
    ...
    msgid "OK"
    msgstr ""
    ...
 * You may encounter strings such as <code>"The file %s can not be found."</code>; the <code>%s</code> should be left intact, as ccHost will substitute the actual piece of information at run time.
-=== Method 2: Translating using Experimental Build POT file ===
+=== Method 2: Translating using Development Build POT file ===
-''NOTE: This is a fast way to ge up and running with ccHost''
+Download the latest build of the master POT file which contains all strings for ccHost:
-Download the latest build of the master POT file which contains all strings for ccHost: http://mirrors.creativecommons.org/cchost/cchost.pot
+<pre>
 From here, one can then pick up step 2 of method 1 above.
@@ Line 46: / Line 63: @@
 === Method 3: Translating using poEdit ===
-[http://www.poedit.org/ poEdit] is an Open Source cross-platform gettext catalogs (.po files) editor. It is built with wxWidgets toolkit and can run on any platform supported by it.  It aims to provide more convenient approach to editing catalogs than launching Notepad (or vi) and editing the file by hand.  Official releases are available from the poEdit web site for Windows and Linux.  An alpha for Mac OS X is available at http://www.poedit.org/files/poedit-1.3.4-alpha.dmg.  The poEdit team reports it is an early alpha, but some translators have had success using it for [[ccPublisher]] (another Creative Commons project).
+[http://www.poedit.org/ poEdit] is an Open Source cross-platform gettext catalog (.po files) editor. It is built with wxWidgets toolkit and can run on any platform supported by it.  It aims to provide more convenient approach to editing catalogs than launching Notepad (or vi) and editing the file by hand.  Official releases are available from the poEdit web site for Windows and Linux.  An alpha for Mac OS X is available at http://www.poedit.org/files/poedit-1.3.4-alpha.dmg.  The poEdit team reports it is an early alpha, but some translators have had success using it for [[ccPublisher]] (another Creative Commons project).
 Just use poEdit's '''File''' -> '''New catalog from POT file...''' function will easily doing so. It even can compile .po into .mo file in the same time you pressing '''Save'''.
-=== Translating under Windows ===
+=== Method 4: Translating under Windows ===
-''NOTE: The following graphical windows use the excellent [[ccPublisher]]. The ideas though can be remapped to [[ccHost]] as well.''
+''NOTE: The [[[Translating_ccPublisher#Translating_under_Windows|following graphical windows]] use the excellent [[ccPublisher]]. The ideas though are easily remapped to [[ccHost]].''
 To translate under Windows, download and install a ccHost 2.9 or greater release.  In the installation directory you will find a the directory ''locale''' which contains the subdirectory '''default'''.  Create a new subdirectory under '''locale/default''' with a name matching your new locale.  For example, to translate ccHost into French, create a directory named <code>fr_FR</code>.

@@ Line 5: / Line 5: @@
 ''Also see [[ccHost Localization]].''
-This document describes the procedures used to create and maintain translations for ccHost, a web-based media sharing software (that powers ccMixter.org and other sites).
+This document describes the procedures used to create and maintain translations for ccHost, a web-based media sharing software (that powers ccMixter.org and other sites). If you are used to the standard translation system in Free and Open Source Software, translation work on ccHost is very similar (and uses the same tools). For those of you that are not familiar with translations, this document is really aimed at you.
 == Supported Languages ==
-The latest release of [[ccHost]] includes support for multiple languagues, depending on who from the community submits languages for localizing the project. We need your help in adding more languages to ccHost!
+The latest development versions of [[ccHost]] include support for multiple languagues. Depending on who from the community submits languages, the make-up of the project will be different. We need your help in adding more languages to ccHost!
-Anyone wishing to assist should sign up on the [http://lists.sourceforge.net/mailman/listinfo/cctools-cchost ccHost] mailing list.
+Anyone wishing to assist should sign up on the [http://lists.sourceforge.net/mailman/listinfo/cctools-cchost ccHost] mailing list and poke around on these projects.
 == Getting Started ==
@@ Line 44: / Line 37: @@
 === Method 2: Translating using Experimental Build POT file ===
 Download the latest build of the master POT file which contains all strings for ccHost: http://mirrors.creativecommons.org/cchost/cchost.pot
@@ Line 103: / Line 98: @@
 This automatically takes care of updating strings on languages, merging changes, etc. It also generates a new clean cchost.pot which can be used as a master file for creating future translations.