(to be continued)
I do search user for create main pages for more languages of etnic groups in Russia (/sah, /udm, /os etc). --Kaganer15:32, 4 October 2011 (UTC)[reply]
I have been at a desperate search for translations. I have been somewhat successful with languages with a greater IRC presence but for others I am rather baffled. I could of course hunt down translators on their individual local wikis but that is far too much work on top of making sure template complies with everyone's needs. I designed the template structure to provide with all the content needed for the translation. I do not have a documentation for it but the task could be simplified as (this could be the to do list)...
Once that's done the next task is to translate the English content on the sub pages. You can see what I mean in Template:Main Page/sr. Whenever the "Edit" links are clicked it will generate the relevant template to be translated and will automatically replace the /en usage the moment the /xx template is created. Sub template structure (edit links will update or create these):
Main Page/Intro
Main Page/World Heritage
Information thread (optional)
Main Page/Requests
Main Page/Community and communication
Main Page/Core issues and collaboration
Wikimedia Foundation
Sisterprojects
I'd like to point out {{Sisterprojects}} already has a lot of translations done but they need to be templateified.
The fun part is once the translations are complete and we decide to add something to the main page, all non translations will display the English text letting translators know exactly what needs to be translated.
Mind you some languages has material that could be used from the current main pages they have. :) On the bright side {{Sisterprojects}} templatification process is complete with the help of multiple people. They still need translations here and there but at least it is no longer the complicated wikitable. -- とある白い猫chi?08:00, 7 October 2011 (UTC)[reply]
I added RTL support now. It has a few issues but those can be addressed in due course. First step is to make everything translated, then fix visual issues IMHO. :) -- とある白い猫chi?16:11, 8 October 2011 (UTC)[reply]
Ah nice! I was asking around for that! It could be incorporated into the month template to limit the visibility of complex code. I'll look into this, thank you for the heads up. -- とある白い猫chi?14:34, 11 October 2011 (UTC)[reply]
Perhaps, better use following code (without "int:"):
where "{{{1}}}" is month, "{{{2}}}" is year, {{{lang}}} is page language code.
This will result not in a user interface language, but in a language of current page. It's more correctly. NB: This method requires support translateviki.net for all languages and dialects (with MediaWiki messages for month names).--Kaganer05:13, 12 October 2011 (UTC)[reply]
That doesn't work:
April 2024
Are you sure it works? The order can be culture specific so I do not want to compromise on that.
I think we could make without this template if it is incorporated into the /Intro template. I'd like to ask you to copy the parameters from Template:Main Page/World Heritage/xx to Template:Main Page/Intro/xx for all existing World Heritage template translations? I will then modify the code for the main page to use these parameters. :). Problem is translators keep missing the edit link. -- とある白い猫chi?03:19, 14 October 2011 (UTC)[reply]
Great! Also there are a few pages that can be templetified like Баш бит. There isn't much of a translation for the bulk of the page but the sisterprojects translation appears more or less complete. I wonder how many Sisterprojects templates we haven't templatified still exist. -- とある白い猫chi?04:36, 16 October 2011 (UTC)[reply]
_by_Ron.jpg)
