User:Kebap/translation infrastructure - Revision history

Kebap: How to exclude text from translation

2019-04-05T08:32:23Z

How to exclude text from translation

Kebap: /* Review progress on each language */

2019-04-04T19:02:09Z

Review progress on each language

Kebap: layout

2018-08-19T01:06:56Z

layout

Kebap: /* Updating input strings */ section added

2018-08-19T01:06:30Z

Updating input strings: section added

Kebap: +Instructions from other project's translations

2018-08-17T04:43:30Z

+Instructions from other project's translations

Kebap at 01:29, 12 July 2018

2018-07-12T01:29:00Z

Kebap at 22:13, 11 June 2018

2018-06-11T22:13:33Z

Kebap at 19:19, 4 June 2018

2018-06-04T19:19:31Z

Kebap at 01:27, 4 June 2018

2018-06-04T01:27:53Z

Kebap at 18:18, 3 June 2018

2018-06-03T18:18:33Z

← Older revision		Revision as of 08:32, 5 April 2019
Line 88:		Line 88:
	en_US 11 0 11 0 11 100		en_US 11 0 11 0 11 100
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	== How to exclude text from translation ==
		+
		+	* In .cpp files, do not use tr() function. Easy.
		+	* In .ui files, change the opening <code><string></code> tags of the elements to <code><string notr="true"></code>
		+	** Or click in QtDesigner like this: https://github.com/Mudlet/Mudlet/pull/2481#pullrequestreview-221930644

← Older revision		Revision as of 19:02, 4 April 2019
Line 60:		Line 60:
	* command is: lupdate.exe -recursive .\src\ -ts .\translations\mudlet.ts		* command is: lupdate.exe -recursive .\src\ -ts .\translations\mudlet.ts
	* lupdate is available during [[Compiling_Mudlet#Compiling_on_Windows_7.2B\|Windows compilation]] in this folder: C:\Qt\5.11.0\mingw53_32\bin\		* lupdate is available during [[Compiling_Mudlet#Compiling_on_Windows_7.2B\|Windows compilation]] in this folder: C:\Qt\5.11.0\mingw53_32\bin\
		+
		+
		+	== Review progress on each language ==
		+	* Crowdin offers statistics in settings, counting translation percentage of ''words''
		+	* Whereas Mudlet counts percentage of ''strings'' and languages >95% receive a gold star
		+	* How to review the progress of current Crowdin translations:
		+	** Open PR "new Crowdin translation" created automagically by integration robots ([https://github.com/Mudlet/Mudlet/pull/2429 Example])
		+	** Open information from automatic Travis CI build, for example Linux gcc qmake ([https://travis-ci.org/Mudlet/Mudlet/jobs/515693306 Example])
		+	** Find lines starting like "Project MESSAGE: Building translations" and see statistics following ([https://travis-ci.org/Mudlet/Mudlet/jobs/515693306#L1380 Example])
		+
		+	Example progress snapshot from 2019-04:
		+	<syntaxhighlight lang="lua">
		+	Project MESSAGE: Building translations
		+	lang trnsl utrnsl finish unfin total percentage
		+	de_DE 1863 28 1863 0 1891 98
		+	el_GR 0 1891 0 0 1891 0
		+	en_GB 403 1488 403 0 1891 21
		+	es_ES 735 1156 735 0 1891 38
		+	fr_FR 150 1741 150 0 1891 7
		+	it_IT 809 1082 809 0 1891 42
		+	nl_NL 45 1846 45 0 1891 2
		+	pl_PL 514 1377 514 0 1891 27
		+	pt_PT 260 1631 260 0 1891 13
		+	ru_RU 1686 205 1684 2 1891 89
		+	zh_CN 961 930 961 0 1891 50
		+	zh_TW 0 1891 0 0 1891 0
		+	en_US 11 0 11 0 11 100
		+	</syntaxhighlight>

← Older revision		Revision as of 01:06, 19 August 2018
Line 1:		Line 1:
−	{{~~Toc~~ right}}	+	{{TOC right}}

	== History ==		== History ==

@@ Line 1: / Line 1: @@
-History:
+{{Toc right}}
 * https://github.com/Mudlet/Mudlet/issues/856 - Setup a web-based translation service for Mudlet
 * https://github.com/Mudlet/Mudlet/issues/1664 - Translation infrastructure of Mudlet web-presences
-Main sources of text:
+== Main sources of text ==
 * Mudlet client itself
@@ Line 12: / Line 14: @@
-Processes for each:
+== Processes for each ==
 # Find out a way to tell outdated texts from relevant current texts which need translation.
@@ Line 26: / Line 28: @@
-References:
+== References ==
 * Another great in-depth look at several alternatives and the process in general in this master study thesis about “Translations in libre software”: https://larjona.wordpress.com/translations-in-libre-software/
@@ Line 44: / Line 46: @@
-Decisions:
+== Decisions ==
 * We want to use US English in the source. Sometimes it is still en/GB - e.g. "licence/license", "color/colour", etc. SlySven will provide a dedicated en/GB translation, but origin will be en/US
@@ Line 50: / Line 52: @@
 * Some texts can't be translated easily in Crowdin, as they are surrounded by < and > for example. This needs to be adjusted in source. See [https://github.com/Mudlet/Mudlet/pull/1804 PR #1804] for example and possible solution.
 ** Some IRC texts start with ! or alike symbols which must not be translated. Compare above solution.

← Older revision		Revision as of 04:43, 17 August 2018
Line 40:		Line 40:
	** https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example		** https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example
	** https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle		** https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle
		+	* Instructions from other project's translations:
		+	** https://manual.cgeo.org/en/translation

@@ Line 44: / Line 44: @@
 Decisions:
-* we should be using US English in the source. Sometimes it is still en/GB - e.g. "licence/license", "color/colour", etc.
+* We want to use US English in the source. Sometimes it is still en/GB - e.g. "licence/license", "color/colour", etc. SlySven will provide a dedicated en/GB translation, but origin will be en/US
-* when a language offers multiple choices on how to address the reader, we will choose the less formal, more friendly way
+* When a language offers multiple choices on how to address the reader, we will choose the less formal, more friendly way

← Older revision		Revision as of 22:13, 11 June 2018
Line 36:		Line 36:
	** Mediawiki		** Mediawiki
	** Github		** Github
		+	* Notes from other translation efforts
		+	** https://www.mediawiki.org/wiki/Localisation
		+	** https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example
		+	** https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle

← Older revision		Revision as of 19:19, 4 June 2018
Line 41:		Line 41:

	* we should be using US English in the source. Sometimes it is still en/GB - e.g. "licence/license", "color/colour", etc.		* we should be using US English in the source. Sometimes it is still en/GB - e.g. "licence/license", "color/colour", etc.
		+	* when a language offers multiple choices on how to address the reader, we will choose the less formal, more friendly way

← Older revision		Revision as of 01:27, 4 June 2018
Line 36:		Line 36:
	** Mediawiki		** Mediawiki
	** Github		** Github
		+
		+
		+	Decisions:
		+
		+	* we should be using US English in the source. Sometimes it is still en/GB - e.g. "licence/license", "color/colour", etc.

@@ Line 28: / Line 28: @@
 References:
-* Another great in-depth look at several alternatives and the process in general in this master study thesis about “Translations in libre software”: https:// larjona.wordpress.com/translations-in-libre-software/
+* Another great in-depth look at several alternatives and the process in general in this master study thesis about “Translations in libre software”: https://larjona.wordpress.com/translations-in-libre-software/
-* multilingual plugins for Wordpress: https:// wordpress.org/plugins/search/multilingual
+* multilingual plugins for Wordpress: https://wordpress.org/plugins/search/multilingual
-** Polylang: https:// wordpress.org/plugins/polylang/
+** Polylang: https://wordpress.org/plugins/polylang/
 * Wordpress internationalisation workflow
 ** http://www.cardinalpath.com/multilingual-wordpress-international-seo/