################################################################################
# Readme to work with translations.                                            #
################################################################################

Introduction
------------
Try to keep the default order. If there aren't any new strings in the GUI php
files you can jump to point 3.


System Requirements
-------------------
Be sure that you have installed gettext. If not install gettext.


Default order
-------------

1. makemsgs
	Use the shell script "makemsgs" to get all strings from GUI php files within
	the ispcp.pot file. But be aware that this will remove all existing
	strings in ispCP.pot that aren't hardcoded in the GUI PHP files.

2. updateToPot
	Use the shell script "updateToPot" to merge automatically the new ispcp.pot
	file (see point 1) with the language specific *.po files.

3. modify *.po files
	Add translations for empty strings or fix wrong translations in the language
	specific *.po files.

4. check all *.po files
	Check the syntax of all *.po files with the check_po script. If the script
	return one or more error, correct them and rerun the script.

	Note : If one or more localization files have been added, add it in the
	localization list of the check_po script before run.

5. create language text files
	Create/export language specific (.ini-like) text files with a language tool
	out of language specific *.po files. These text files can be used to upload
	them to the ispCP GUI panel.

	See http://atomo64.puffinhost.com/ispcp/poconverter.php for the online
	generator.
