Navigation

Changeset 47126

Timestamp:

07/17/06 15:20:34 (2 years ago)

Author:

madarche

Message:

- Fixed #1698: Missing instructions in howto-translate_cps.txt, when using

CPS >= 3.4 (Patch kindly provided by Santi Camps).

Files:

r45720	r47126
8	8	~~~~~~~~~~
9	9	- Added the needed doc to make the `make_pot` and `update_pos` scripts work.
	10	- Fixed #1698: Missing instructions in howto-translate_cps.txt, when using
	11	CPS >= 3.4 (Patch kindly provided by Santi Camps).
10	12	New internal features:
11	13	~~~~~~~~~~~~~~~~~~~~~~

r45720	r47126
83	83
84	84	Then add your language to the language vocabulary defined in
85		``CPSDocument/skins/cps_document/getDocumentVocabularies.py``.
	85	``CPSDocument/skins/cps_document/getDocumentVocabularies.py`` if
	86	you use CPS < 3.4. For CPS >= 3.4, do the same in
	87	''CPSDefault/profiles/default/vocabularies/language_voc.xml''.
86	88	There are three keys to add: the first one is the i18n label, the
87	89	same that you used to name your po file; the second one is how you
…	…
92	94
93	95	If you use CPS < 3.4, you will also need to modify the file
94		``CPSDefault/zmi/manage_addCPSSiteForm.dtml``. There's a Languages
	96	``CPSDefault/zmi/manage_addCPSSiteForm.dtml``. If you use CPS >= 3.4,
	97	then do the same in ``CPSDefault/factory.py``. There's a Languages
95	98	box which contains a list of two element tuples. Add a new tuple
96	99	for your language. The first element will be the i18n label and
…	…
109	112	Updating the translations from the translation files can be done through the
110	113	`portal_setup` tool (located at the root of your CPS instance in the `ZMI`) by
111		importing the needed steps from the `Import` tab.
	114	importing the needed steps from the `Import` tab, but before that you need to add
	115	your language code to the `available_languages` property of your CPS site
	116	(`Property` tab of your CPS instance in the `ZMI`).
112	117
113	118	If the translations you are doing only affect the CPSDefault, CPSSchemas,