Template talk:Main Page/Sisterprojects/Code

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search


Shouldn't it be possible to translate this template for the benefit of translations of the main page? If so, how would it work to effectuate that? – McDutchie 06:13, 2 April 2009 (UTC)

People usually just copy it and create a subpage. Cbrown1023 talk 20:58, 2 April 2009 (UTC)


What about adding the Wikipedia Usability Initiative?--Kozuch 13:14, 13 February 2009 (UTC)

I don't think it's reasonable to call usability.wm.o a sister project. For that matter, I think the same arguments likely apply to test.wp.o and some others. I'd be in favor of removing more projects, not adding ones. --MZMcBride 21:18, 24 October 2009 (UTC)
I propose removing the following special projects from this template: Bugzilla, Wikipedia Usability, Wikimedia Strategy, Wikimania, and Test Wikipedia. (Keeping MediaWiki, WMF wiki, and Incubator, as all three have previously used Meta as a home.) Alternately, we could add dozens of other special projects (quality, internal, the labs wikis, etc.), but I think that would be a bit silly. --MZMcBride 18:44, 25 October 2009 (UTC)
I would like to see all the major wikis linked on Meta homepage. We can split these into two templates, if you donw want to call the others "sister" ones. I have no idea what the other special projects you mention are (quality, internal etc.), but as long as some of them has its own wiki (I mean an instance of WikiMedia running as a separate website) I will be happy to include these - possibly in the other, new template. I dont know the situation with labs wikis, as far as I have noticed they have no central web (like at labs.wikimedia.org), which I find pitty - dont know how many projects there are, maybe we could create another place for these. Also, do you think WMF web is a sister project? I dont.--Kozuch 07:22, 26 October 2009 (UTC)
Maybe this template could be moved to "Otherprojects" - that would solve the issue pretty much.--Kozuch 17:11, 26 October 2009 (UTC)

why removed link to WMF site ?[edit]

Why was deleted link to wikimediafoundation site ? --Kaganer 16:43, 7 December 2009 (UTC)

Hi, I removed the link because it is not a Wikimedia project but a website of an organization. The preceding unsigned comment was added by Kozuch (talk • contribs) .
Hi, it is a "backstage" project that is a wiki owned by the Wikimedia foundation. There are far looser projects on this template that I'd rather see off before the foundation's project is. I'm re-inserting it. Killiondude 04:00, 10 October 2010 (UTC)

Why not included wikistats ?[edit]

Why not included wikistats project ? --Kaganer 17:38, 7 December 2009 (UTC)

Yes check.svg Done - Are included ;) --Kaganer 17:54, 11 December 2009 (UTC)

classify "Backstage" projects[edit]

I think the "Backstage" projects could be classified better. Some are technical some are cultural. Suggestions? -- とある白い猫 chi? 15:47, 4 October 2011 (UTC)

Isn't incubator a content project? I am moving it as such, feel free to revert. :) -- とある白い猫 chi? 16:42, 4 October 2011 (UTC)
Hi, I would remove WMF from Backstage projects since it is actually not a "project" in this sence itself and it is also prominently linked at the footer of all wikis (together with MediaWiki, which might also be removed here).--Kozuch 21:22, 4 October 2011 (UTC)

Fixed width[edit]

To be honest, the fixed width is not particularly nice ...--Kozuch 18:28, 6 October 2011 (UTC)


Tenwiki: has been closed, so it should probably be removed from the list of backstage projects. --Yair rand 05:09, 28 December 2011 (UTC)


I know, yet another discussion about the Wiktionary logo...

If I recall correctly, Smurrayinchester proposed using a single, large tile when listing Wiktionary as a sister project, since the nine tiles hardly fit a 35-pixel square. So I switched to that image; hope it isn't a problem for anyone. More importantly, there's now a WiktionaryLogo parameter so that the English Main Page, say, could display the same textual logo the English Wiktionary community still uses.

 – Minh Nguyễn (talk, contribs) 23:16, 29 December 2011 (UTC)

Thank you. This is not the right place to discuss it, but shouldn't we do the same on the portal as well? After all this is certainly the "main" if not only logo. In any case, I think we are not forced to be fully consistent and that it makes sense to use this logo when the space is limited and the other one clearly unsuitable. Nemo 23:30, 2 January 2012 (UTC)

Labs link[edit]

The link to Wikimedia labs is wrong. It should be //www.mediawiki.org/wiki/Wikimedia_Labs, because //mediawiki.org/wiki/Wikimedia_Labs always forwards to http. πr2 (tc) 15:02, 8 April 2012 (UTC)

Fixed Pmlineditor (t · c · l) 15:13, 8 April 2012 (UTC)

Wikisource link fix[edit]

The link to Wikisource is wrong. It should be:

{{Main Page/Sisterprojects/Cell/{{{dir|ltr}}}
  |text={{{The free library|The free library}}}

Thanks. --FRacco (talk) 15:35, 15 July 2012 (UTC)



繁體首頁內容計畫處,各個中文維基計畫的連結有誤。例如:中文維基百科被錯誤連結至zh-hant.wikipedia.org。 -- By LNDDYL.(留言) 2014年6月25日 (三) 12:18 (UTC)

去看了一下,是 http://meta.wikimedia.org/w/index.php?title=Template:Main_Page/Sisterprojects/Code&action=edit 这个页面的问题。zh-hans或zh-hant被作为语言代码当作这个模板的参数(|link=//{{#if:{{{wp|{{{lang|}}}}}}|{{{wp|{{{lang|}}}}}}.wikipedia.org/wiki/{{{WikipediaLink|}}}|www.wikipedia.org/}})。需要加一个判断是否zh-hans或zh-hant。不过我不太会改,谁会改的去改一下。 --SFSQ2012留言) 2014年6月26日 (四) 02:43 (UTC)

我尝试修改了相关模板,但 未修复 囧rz...-- By LNDDYL.(留言) 2014年6月26日 (四) 08:47 (UTC)

The home page is still not fully prepared to use the Translate extension.
What you tried was to deprecate the "zh" code, but in fact it is the reverse: "zh" is recommanded for BOTH Simplified and Traditional Chinese as the "zh" locale is already designed to support the selection of a "variant" with transliterators (without using separate translated resources). So all the Chinese "languages codes", like "zh-hans", "zh-hant", "zh-cn", "zh-hk", "zh-mo", "zh-sg" are deprecated. The priority is to translate the "zh" resources only (all others have had their support removed as locale codes in the Translate extension). If you visit a page that uses the "zh" locale, you'll be offered the translietarion option.
However we know that we have problems on the home page, because it does not explicitly sets its content language (and the support far adding the additiona support of variants withiknn te same locale is still missing)
So for templates that will be used in the home page, we need to "relay" the variant as if it was still a locale code, but translations must still use templates named with "/zh".
Your code did not work because it used an invalid #if code (you cannot use "or" in a #if or #ifexpr expression when comparing strings and #ifexpr only supports numeric expressions).
And in fact ou code would have not worked anyway becaues you attempted to use the subpagename and the Homepage does not have any sybpagename.
Unfortunately the best we can do for now is ti use the {{pagelang}} template that attempts to detect the content language from the page, checks some known problematic subpage; checkd the validity of the language code (it also ensures it is only made with lowercase ASCII latin letters, hyphens or possibly digits, and starts by a lowercase etter); and if everything is OK, it will return the last subpage name in a normalized form. May be later we'll have some metadata that can be set in a page to explicitly set its content language, and another keyword to retrieve it in template, and then {{tl[pagelang}} will be updated to use that information if it's available.
For this reason, the home page transcludes a template generating it completely, but this template is named with a /lang suffix and specifies explciitly the langauge code to use in all other subtemplates. The only interest of using this tempalte is that it allows defining the page title. Later when everything will be managed in the Translate extension, we(ll be able to use that general template as the home page itself, because it can have its own displayed title localized (even if the page name is named "Main/code".
For now it is difficult to support the "zh-hant" variant, but the generic "Main/zh" template must work and must use the simplified version. When it will be rendered as the viewed page, it should display to you the variant selector allowing the traditional variant to be displayed. But for now this requires using the page stored in "Template/Main/zh" and that page cannot be renamed (but its displayed title can still be set)
In my opinion we should simplify things by redirecting existing pages whose name has been localised without the suffix, to pages named "Main/code" and make that page translatable, we would no longer need "Template:Main/code".
But this cannot be done or now for tricky reasons on how existing templates are working (they have used various old Translation mechanisms which are slowmy being migrated) Additionally we still have Main page translations that do not exhibit the new layout and we must still keep a way or them to remain functional. tHe new scheme is being enforced in "Template:Main/code" pages, but not in pages of the root namespace named "Main Page" (translated) which conditionally use the template version incompatible with the few old unmaintained main pages incompatible with the new scheme (but these pages are still used and at least partly functional, so we don't want to remove them immediately).7
Another thing to consider is that external links coming to Meta-Wiki must remain functional (at least via a single redirect) so we need to keep the old page names "Main Page (translated)" in the root namespace at least with a working redirect (but the redirect could go to "Template:Main Page/code" (with the untranslated page name).
So it's not as simple as what you thought. So please avoid braking the "zh" version by forcing to go to "/zh-hans" or "/zh-hant" when we know that these codes will not work and that your code will even be unable to perform the correct test!
Even before you tried, we were already aware of the problem and actively working on it (this requires much more preparation and checks, as hacking the home page is very risky and tricky). verdy_p (talk) 13:44, 26 June 2014 (UTC)
I made a template {{Wikilangcode}} to remap standard BCP47 codes and legacy codes to codes used in Wikimedia project subdomains. It should solve most problems. Note that languages that don't have a full Wikipedia (for example) but that have a working test project in Incubator are being redirected automatically to incubator:Wp/code/... by the webserber hosting the base domain name of that project (e.g. Wikipedia or the most recent Wikivoyage). The template does not discriminate between projects, as it only has a language code, so it you don't like these redirects, the code in "Template:Main Page/code" will need to specify the appropriate wiki code to use. Some languages or undetermined languages are mapped to "www" (the user needs to choose the language edition).
So now this works from the "zh-hans" and "zh-hant" main pages: the links to sisterprojects are directing you to "zh" projects. {{Wikilangcode}} may need other edits (I based it from the code in {{BCP47}} slightly modified) to reverse some mappings (but not all: some legacy language codes that were used in Wikimedia projects are now using standard BCP47 codes... but still not all). verdy_p (talk) 15:29, 26 June 2014 (UTC)
Note: all language codes starting with "zh-" with variants appended are progressively being migrated. "zh" alone supports the choice of variant locales (taking into account user preferences) for its transliterator, just like in Chinese Wikipedia or Wiktionnary. This also applies to transliterations for Serbian and a few other languages written with alternate scripts and working rules
This transliteration does not work with some languages; such as Kashmiri written with Devanagari or Arabic scripts, because the transliteration from Devanagari to Arabic is lossy and many texts written with the Arabic scripts are ambiguous for the reverse conversion of vowels, unless the Arabic vowel points are strictly written (there are also some issues with a few consonnants and there's a lack of standard orhographic rule to perform these conversions safely, or it would require complex dictionary lookups and we don't have a good dictionnary for that language, Kashmiri linguists are still militating for the adoption of their own alphabet that will be easily convertible to Arabic and Devanagari; but this is not solved and there are strog disagreements between India, Pakistan and China, in this region (and former independant kingdom) split now on three countries. For these languages, we still need separate translations with separate language codes. verdy_p (talk) 15:50, 26 June 2014 (UTC)