Index of /gallery/po/

NameLast ModifiedSize
UpParent Directory
[TXT]change_version.sh2017-08-11 02:59 4k
[TXT]copyright-header.txt2017-08-11 02:59 4k
[TXT]create_po_template.sh2017-08-11 02:59 4k
FileCREDITS2017-08-11 02:59 4k
[TXT]edit_changelog.sh2017-08-11 02:59 4k
Filefilelist-common2017-08-11 02:59 4k
Filefilelist-config2017-08-11 02:59 4k
Filefilelist-core2017-08-11 02:59 4k
Filegallery-common.pot2017-08-11 02:59 40k
Filegallery-config.pot2017-08-11 02:59 100k
Filegallery-core.pot2017-08-11 02:59 112k
[TXT]make_mo_files.sh2017-08-11 02:59 8k
Fileremove_obsolete.pl2017-08-11 02:59 4k
Filetransform_fuzzy.pl2017-08-11 02:59 4k
[TXT]update_po_files.sh2017-08-11 02:59 4k
$Id: README 17459 2008-02-09 17:11:37Z JensT $ ************************************************* * * * If you are using the *nix scripts you need: * * * * GNU gettext Version 0.12.1 * * Recommended Version is 0.16 or higher * * * ************************************************* Here's how to create a new GALLERY translation (1.4.1 or newer) 1.) Choose which version of GALLERY you want to translate. (We suggest you choose the newest) 2.) Download or make fresh gallery-XXX.pot (po template) files according to your choosen version by * getting a full copy of the GALLERY source code from CVS or * just get the gallery-XXX.pot file from the po folder via WebCVS XXX is the component name. Note: If you are using Linux/Unix and have the full source code you can create a new gallery-XXX.pot file from the source code itself. Type: sh create_po_template.sh Normally you will not need to this, because the .pot that comes with the newest gallery should be up-to-date. Please consult with the translation team leaders before creating your own gallery.pot. 3.) copy gallery-XXX.pot (po template) to your own .po file. Your .po Translation-File has to be named <language>_<COUNTRY>-gallery_<component>.po For example: english, Great Britain -> en_GB-gallery_core.po or deutsch, Deutschland -> de_DE-gallery_config.po 4.) Edit header Information correctly (charset etc ..) Note: A good tool to edit .po files is poEdit poEdit works on Windows Systems, too. It is available from http://poedit.sourceforge.net/ 5.) Do your translation If you see something like: msgid "Upgrading item %d of %d . . . " or msgid "%s (%s), %s on %s" then leave the %d or %s in your translation. They are place holders for things like "time" or "times" or numbers. If you have problems with the order, because in your language its different then in english. You can use the $ to change order eg: msgid "Upgrading item %d of %d" msgstr "... %2$d ... %1$d ..." 6.) If all translations are done * With Shell Access run make_mo_files.sh sh make_mo_files.sh -po <language>_<COUNTRY> this works only on *nix System with bash * Without Shellaccess: o use poEdit and create a <language>_<COUNTRY>-gallery_<component>.mo file from your .po file o create a locale/<language>_<COUNTRY> folder o copy <language>_<COUNTRY>-gallery_<component>.po file into locale/<language>_<COUNTRY> o copy <language>_<COUNTRY>-gallery_<component>.mo into locale/<language_COUNTRY>/LC_MESSAGES/ 7.) Copy the nls.php file into locale/<language>_<COUNTRY> and edit it to your needs 8.) Test your gallery if the newlanguage works fine. 9.) Send your <language_COUNTRY>-gallery_XXX.po (ONLY THES FILES) to the GALLERY Language tracker If you dont have a sourceforge account, or have no clue about this tracker then send your .po files to me. <jens@peino.de> Note: Please tell us for which Version your translation is!
Proudly Served by LiteSpeed Web Server at roystpierre.com Port 80