Update the Localisation Files - Revision history

Alnaucler at 18:07, 18 August 2021

2021-08-18T18:07:23Z

← Older revision		Revision as of 20:07, 18 August 2021
Line 1:		Line 1:
	{{Warning \| The two original files IMessage.properties and ITerms.properties should '''not''' be edited. If you would like to change the English terms and messages then you have to create an English copy of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the '''<nowiki>=</nowiki>''' sign) should '''not''' be replaced.}}		{{Warning \| The two original files IMessage.properties and ITerms.properties should '''not''' be edited. If you would like to '''change the English''' terms and messages then you have to create an '''English copy''' of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the '''<nowiki>=</nowiki>''' sign) should '''not''' be replaced.}}

	{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}		{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}
Line 18:		Line 18:
	==ITerms.properties==__NOEDITSECTION__		==ITerms.properties==__NOEDITSECTION__
	The ITerms.Properties file contains terms used in menus, tooltips and field names in {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.		The ITerms.Properties file contains terms used in menus, tooltips and field names in {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.
	# Copy the existing ITerms.properties to e.g. ~~ITerms~~.properties or ~~ITerms~~.properties for English.		# Copy the existing ITerms.properties to e.g. ITerms_km.properties or ITerms_en.properties for English.
	# Edit the ITerms.properties copy with Rosetta-J.		# Edit the ITerms.properties copy with Rosetta-J.

Alnaucler at 16:14, 15 June 2017

2017-06-15T16:14:01Z

← Older revision		Revision as of 18:14, 15 June 2017
Line 5:		Line 5:
	The three files that are used for localisation need to be created for each new language. Each language has a unique language code. IMSMA is using the Window's codes. See which code should be used in the Data Inventory Manager.		The three files that are used for localisation need to be created for each new language. Each language has a unique language code. IMSMA is using the Window's codes. See which code should be used in the Data Inventory Manager.

	# ~~From~~ the '''Customisation''' menu~~, select~~ '''Data Inventory Manager'''.		# In the '''Customisation''' menu → '''Data Inventory Manager'''.
	# Click on the Translate button in the Data Category pane of the Data Inventory Manager window.		# Click on the Translate button in the Data Category pane of the Data Inventory Manager window.
	# Find the desired language in the Language list and note the code e.g. km for Khmer.		# Find the desired language in the Language list and note the code e.g. km for Khmer.

Alnaucler at 18:13, 9 May 2017

2017-05-09T18:13:19Z

← Older revision		Revision as of 20:13, 9 May 2017
Line 1:		Line 1:
	{{Warning \| The two original files IMessage.properties and ITerms.properties should '''not''' be ~~edit~~. If you would like to change the English terms and messages then you have to create an English copy of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the '''<nowiki>=</nowiki>''' sign) should '''not''' be replaced.}}		{{Warning \| The two original files IMessage.properties and ITerms.properties should '''not''' be edited. If you would like to change the English terms and messages then you have to create an English copy of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the '''<nowiki>=</nowiki>''' sign) should '''not''' be replaced.}}

	{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}		{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}

Alnaucler at 07:52, 17 August 2016

2016-08-17T07:52:37Z

← Older revision		Revision as of 09:52, 17 August 2016
Line 25:		Line 25:
	==trans.properties==__NOEDITSECTION__		==trans.properties==__NOEDITSECTION__
	The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.		The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.
	# '''[[Export ~~and Translate~~ the ~~Terms~~\|export]]''' the English translations		# '''[[Export the Translations\|export]]''' the English translations
	# rename the file (e.g. trans_km)		# rename the file (e.g. trans_km)
	# '''update''' the first row in the file to the new language code		# '''update''' the first row in the file to the new language code
	# create translations with Rosetta-J		# create translations with Rosetta-J
	# '''[[Import the ~~Translated Terms~~\|import]]''' the file into the database.		# '''[[Import the Translations\|import]]''' the file into the database.

	{{NavBox HowTo Languages and Translations}}		{{NavBox HowTo Languages and Translations}}

	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 20:08, 16 August 2016

2016-08-16T20:08:58Z

← Older revision		Revision as of 22:08, 16 August 2016
Line 1:		Line 1:
	{{Warning \| The two original files IMessage.properties and ITerms.properties should '''not''' be edit. If you would like to change the English terms and messages then you have to create an English copy of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the sign) should '''not''' be replaced.}}		{{Warning \| The two original files IMessage.properties and ITerms.properties should '''not''' be edit. If you would like to change the English terms and messages then you have to create an English copy of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the '''<nowiki>=</nowiki>''' sign) should '''not''' be replaced.}}

	{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}		{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}
Line 25:		Line 25:
	==trans.properties==__NOEDITSECTION__		==trans.properties==__NOEDITSECTION__
	The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.		The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.
	# [[Export and Translate the Terms\|export]] the English translations		# '''[[Export and Translate the Terms\|export]]''' the English translations
	# rename the file (e.g. trans_km)		# rename the file (e.g. trans_km)
	# '''update''' the first row in the file to the new language code		# '''update''' the first row in the file to the new language code
	# create translations with Rosetta-J		# create translations with Rosetta-J
	# [[Import the Translated Terms\|import]] the file into the database.		# '''[[Import the Translated Terms\|import]]''' the file into the database.

	{{NavBox HowTo Languages and Translations}}		{{NavBox HowTo Languages and Translations}}

	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 20:00, 16 August 2016

2016-08-16T20:00:52Z

← Older revision		Revision as of 22:00, 16 August 2016
Line 1:		Line 1:
			{{Warning \| The two original files IMessage.properties and ITerms.properties should '''not''' be edit. If you would like to change the English terms and messages then you have to create an English copy of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the sign) should '''not''' be replaced.}}

	{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}		{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}

Line 7:		Line 9:
	# Find the desired language in the Language list and note the code e.g. km for Khmer.		# Find the desired language in the Language list and note the code e.g. km for Khmer.

	{{Note\| If you are running {{IMSMANG}} in a client/server installation and modify the properties files, you will need to copy ~~this file~~ to the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder of each client computer. }}		{{Note\| If you are running {{IMSMANG}} in a client/server installation and modify the properties files, you will need to copy of IMessage and ITerms files to the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder of each client computer. }}

	==IMessages.properties==__NOEDITSECTION__		==IMessages.properties==__NOEDITSECTION__
	The IMessage.properties file contains the error messages and warning messages used by {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.		The IMessage.properties file contains the error messages and warning messages used by {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.
			# Copy the existing IMessage.properties to e.g. IMessage_km.properties or IMessage_en.properties for English.
			# Edit the IMessage.properties copy with Rosetta-J.

	==ITerms.properties==__NOEDITSECTION__		==ITerms.properties==__NOEDITSECTION__
	The ITerms.Properties file contains terms used in menus, tooltips and field names in {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.		The ITerms.Properties file contains terms used in menus, tooltips and field names in {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.
			# Copy the existing ITerms.properties to e.g. ITerms.properties or ITerms.properties for English.
			# Edit the ITerms.properties copy with Rosetta-J.

	{{Warning \| There are two terms that should '''not''' be translated and affects how dates are written in {{IMSMANG}}, see [[Two Terms Not to be Translated \| '''more details here''']].}}		{{Warning \| There are two terms that should '''not''' be translated and affects how dates are written in {{IMSMANG}}, see [[Two Terms Not to be Translated \| '''more details here''']].}}

	==trans.properties==__NOEDITSECTION__		==trans.properties==__NOEDITSECTION__
	The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.		The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.
	~~# check in Data Inventory Manager which is the code of the local language/variation (e.g. sv for Swedish)~~
	# [[Export and Translate the Terms\|export]] the English translations		# [[Export and Translate the Terms\|export]] the English translations
	# rename the file (e.g. ~~trans_sv~~)		# rename the file (e.g. trans_km)
	# '''update''' the first row in the file to the new language code		# '''update''' the first row in the file to the new language code
	# create translations with Rosetta-J		# create translations with Rosetta-J

Alnaucler at 08:08, 1 August 2016

2016-08-01T08:08:52Z

← Older revision		Revision as of 10:08, 1 August 2016
Line 17:		Line 17:

	==trans.properties==__NOEDITSECTION__		==trans.properties==__NOEDITSECTION__
	The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. ~~The file is ] from File menu → Export → Translations.~~		The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc.
	# check in Data Inventory Manager which is the code of the local language/variation (e.g. sv for Swedish)		# check in Data Inventory Manager which is the code of the local language/variation (e.g. sv for Swedish)
	# [[Export and Translate the Terms\|export]] the English translations		# [[Export and Translate the Terms\|export]] the English translations

Alnaucler at 08:08, 1 August 2016

2016-08-01T08:08:15Z

← Older revision		Revision as of 10:08, 1 August 2016
Line 19:		Line 19:
	The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. The file is ] from File menu → Export → Translations.		The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. The file is ] from File menu → Export → Translations.
	# check in Data Inventory Manager which is the code of the local language/variation (e.g. sv for Swedish)		# check in Data Inventory Manager which is the code of the local language/variation (e.g. sv for Swedish)
	# [[Export and Translate the Terms\|export] the English translations		# [[Export and Translate the Terms\|export]] the English translations
	# rename the file (e.g. trans_sv)		# rename the file (e.g. trans_sv)
	# '''update''' the first row in the file to the new language code		# '''update''' the first row in the file to the new language code

Alnaucler at 08:07, 1 August 2016

2016-08-01T08:07:48Z

← Older revision		Revision as of 10:07, 1 August 2016
Line 17:		Line 17:

	==trans.properties==__NOEDITSECTION__		==trans.properties==__NOEDITSECTION__
	The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. The file is ~~[[Export and Translate the Terms\|exported]~~] from File menu → Export → Translations. ~~When~~ the ~~translation to desired~~ language ~~is finished,~~ the file is [[Import the Translated Terms\|~~imported~~]] into the database.		The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. The file is ] from File menu → Export → Translations.
			# check in Data Inventory Manager which is the code of the local language/variation (e.g. sv for Swedish)
			# [[Export and Translate the Terms\|export] the English translations
			# rename the file (e.g. trans_sv)
			# '''update''' the first row in the file to the new language code
			# create translations with Rosetta-J
			# [[Import the Translated Terms\|import]] the file into the database.

	{{NavBox HowTo Languages and Translations}}		{{NavBox HowTo Languages and Translations}}

	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 07:22, 1 August 2016

2016-08-01T07:22:14Z

← Older revision		Revision as of 09:22, 1 August 2016
Line 1:		Line 1:
	{{Note \| To modify the localisation files, you '''should''' use Rosetta-J.}}		{{Note \| To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team \| GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}

	The three files that are used for localisation need to be created for each new language. Each language has a unique language code. IMSMA is using the Window's codes. See which code should be used in the Data Inventory Manager.		The three files that are used for localisation need to be created for each new language. Each language has a unique language code. IMSMA is using the Window's codes. See which code should be used in the Data Inventory Manager.
Line 6:		Line 6:
	# Click on the Translate button in the Data Category pane of the Data Inventory Manager window.		# Click on the Translate button in the Data Category pane of the Data Inventory Manager window.
	# Find the desired language in the Language list and note the code e.g. km for Khmer.		# Find the desired language in the Language list and note the code e.g. km for Khmer.
	~~# Contact your [[Information Management Team \| GICHD IM advisor]] for guidance on how to get started.~~

	{{Note\| If you are running {{IMSMANG}} in a client/server installation and modify the properties files, you will need to copy this file to the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder of each client computer. }}		{{Note\| If you are running {{IMSMANG}} in a client/server installation and modify the properties files, you will need to copy this file to the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder of each client computer. }}