Talk:Localisation

From MediaWiki.org
Jump to: navigation, search

Initial source[edit | edit source]

As noted in the edit summary, this from an exchange between Edward Z. Yang and Tim Starling from the wikitech-l mailing list, posted by User:Nickj. Nick - can you post confirmation here once you have got permission that they are happy to release this as GFDL. --HappyDog 01:08, 23 November 2006 (UTC)


where is the ISO 8601 bug report?

All bugs should be reported on Bugzilla. --HappyDog 13:20, 2 April 2007 (UTC)

== British English? ==--Purodha Blissenbach 00:31, 17 March 2009 (UTC)

Is there any reason why this page is Internationalisation and not Internationalization? The text of the page itself as well as the text accompanying links like the one on Developer_hub use the z version as does Wikipedia (http://www.google.com/search?q=internationalization%20site:en.wikipedia.org vs http://www.google.com/search?q=internationalisation%20site:en.wikipedia.org). Don't really care which one is used. Well that's not true, I would prefer Internationalization. But regardless we should at least be consistent. --Cneubauer 02:35, 29 August 2007 (UTC)

That's likeli becauze peoples automatikally type vot thei are uzed to, and mybee they don't recognise even that ther are differences ;-) --Purodha Blissenbach 00:31, 17 March 2009 (UTC)

Article content Localisation[edit | edit source]

Greetings.

Is there any way to use Localisation to translate custom words inside an article content?

What about page title in the article content?

Thanks

Palanolho 17:58, 21 March 2011 (UTC)

You should check IMSLP. They use a system of templates for that. But I'm not sure if that's the standard solution. --Micru 09:18, 30 January 2012 (UTC)
There isn't any standard solution, several hacks have been used in the past. Now the Extension:Translate is providing a proper (albeit not complete yet) solution. This is offtopic for this page, by the way. Nemo 09:41, 30 January 2012 (UTC)

{{GRAMMAR}} in JS[edit | edit source]

Is {{GRAMMAR}} working in JavaScript?  « Saper // talk »  02:55, 1 March 2012 (UTC)

Font not working[edit | edit source]

Good day, when I open the Cree wikipedia (cr.wikipedia.org) from my work computer, I only see squares instead of Cree syllabics. First, I would like to know if that's normal or if that's bug. Second, would there be a way to fix that from the MediaWiki end since people on computers like that don't have access to change the settings of their browser or install new fonts (now I'm from a work computer, but same thing could happen from a computer in a library for example). I'm using Internet Explorer 7. I wasn't sure if that's the right place to ask that, if it isn't, could you please point me in the good direction. Thanks, Amqui (talk) 21:03, 14 September 2012 (UTC)

Yes, it's a problem with your system, it works fine with GNU/Linux (fedora 17 here).
Extension:WebFonts#Adding a new language support should explain you how to fix that problem for all users; to enable it locally you'll need a separate bug with local consensus. Further questions should be asked on the extension's talk I think. --Nemo 21:31, 14 September 2012 (UTC)

Coding convention on line length[edit | edit source]

What's the coding convention on how long lines should be? I notice that often, the lines in these i18n files go beyond 80-100 columns. Leucosticte (talk) 09:09, 18 October 2012 (UTC)

Huge TOC[edit | edit source]

This TOC is huge. Please consider collapsing it, making it float or something. Of course the better solution would be to split all the content here in different pages, leaving in this one what is essential for (new) translators. We are pointing to this page from How to contribute, so a nicer landing for newcomers would be great. Any takers?--Qgil (talk) 22:13, 31 December 2012 (UTC)

What's wrong with the TOC being long? What's important is that it's navigable. How to contribute links to the only section which is really relevant for translators, so they don't have to care about the TOC or the rest of the page (while they'd see the TOC if it was floating). --Nemo 22:39, 31 December 2012 (UTC)

Namespace localisation[edit | edit source]

I tried to localize my custom namespace the way it is described in Localisation#Namespaces.

In my LocalSettings.php I defined:

...
define( 'NS_MYEXTENSION', 2750 );
...

And in my MyExtension.namespaces.php I defined:

<?php
$namespaceNames = array();
/** English */
$namespaceNames['en'] = array(
	NS_MYEXTENSION => 'MyExt'
);
 
/** German */
$namespaceNames['de'] = array(
	NS_MYEXTENSION => 'MeineErw'
);

I registered MyExtension.namespaces.php with $wgExtensionMessagesFiles, but the namespace was not available on the wiki.

When I added

...
$wgExtraNamespaces[NS_MYEXTENSION] = 'MyExt';
...

to my LocalSettings.php the namespace got accessbible by "MyExt:" prefix, but not by "MeineErw:".

Has anybody an idea what I'm doing wrong? --Osnard (talk) 08:57, 10 September 2013 (UTC)

What's your wiki's language code? --Nemo 09:07, 10 September 2013 (UTC)

Proposed additions to "Internationalization hints" section[edit | edit source]

Avoid using message strings generated by the browser[edit | edit source]

Not all MediaWiki languages are supported by any or all browsers. So strings generated by the browser may appear in a different language to the interface, or may use incompatible terms to the interface.

Avoid using message strings generated by CLDR[edit | edit source]

Not all MediaWiki languages are supported by CLDR.

Are the above proposed additions to the Localisation page advice correct? Lloffiwr (talk) 00:51, 2 December 2013 (UTC)

(Context: bugzilla:57643#c11, bugzilla:56813.) Currently the direction taken seems to be the very opposite, so even if adopted those principles wouldn't reflect the reality. Before proposing them, you should try and get at least one such usage changed in the code. I'd suggest to (find someone able to) submit a patch directly, because bugzilla reports on such matters tend to focus on unproductive theoretical discussions about who should spend time doing what rather than on concrete issues and solutions. --Nemo 13:37, 3 December 2013 (UTC)
Nemo:Are you able and willing to discuss these issues on some developer platform? Lloffiwr (talk) 11:31, 14 December 2013 (UTC)
Sorry, I would have no idea where to start. Echo i18n issues, for instance, are intractable for me. It's better to start from some marginal corner of the codebase nobody cares about and then address controversial drama-prone "in the news" areas like Echo only after the dust settles down, IMHO. --Nemo 10:41, 15 December 2013 (UTC)