Translating talk:Localisation for developers
|Thread title||Replies||Last modified|
|Encoding format||1||11:49, 27 April 2014|
|Translation||1||11:04, 2 February 2014|
|mw:Localisation||6||15:32, 22 July 2012|
|New page - localisation for developers||5||19:03, 13 July 2012|
Translatewiki and our project seem to have gotten into an unintentional tit-for-tat war over encoding formats. Which of these formats does Translatewiki prefer for qqq.json?
" or " or \u0026quot; or \u0022
> or > or \u0026gt; or \u003e
Looking at our logs, we see each of the above arriving from Translatewiki at one time or another.
Why are there no translations for this page? Should it not be translated or are there just no translations _yet_ ?
The MediaWiki page is for MediaWiki developers. This page is for developers of all current and potential future projects at translatewiki.net.
Yes, but isn't there a lot of general advice on the MediaWiki page? And, doesn't mw:Help:Extension:Translate/Translation best practices also have suggestions for developers which should maybe centralized there?
Is there some way to know how many page visits this page has had?
The mw:Localisation page says: "This page gives a technical description of MediaWiki's internationalisation and localisation (I18N) system, and gives hints that coders should be aware of."
How happy are they going to be that it is extended to cover details of the internationalisation and localisation system on translatewiki.net?
Can you explain a little more about why you are wanting to delete this page? Is it doing any harm as it is now? Is there a project underway to get rid of all help pages on translatewiki.net?
I have set up a new page as a resource for the developers and project managers of both potential new projects and existing ones - Translating:Localisation for developers
Target audience: Project developers and managers, also providing translators with understanding of project management and communication mechanisms.
Please make additions and corrections.
Thanks for the effort. Not really sure where to integrate this in our current documentation. Any suggestions?