Talk:Main Page/Archives/2014

user check

zh.wikivoyage have no one which is 18 years old, what should we do? --Gabrielchihonglee (talk) 14:24, 23 January 2014 (UTC)

• @Gabrielchihonglee: So this wiki will have no checkuser (and oversighter) if nobody more than 18 years old requests for this right. sysop and crat can be younger than 18 years old.--GZWDer (talk) 14:27, 23 January 2014 (UTC)

• I don't think CU/OS are needed in such a small project. Anyway, this is not the place to discuss that. LlamaAl (talk) 14:38, 23 January 2014 (UTC)

Wikimania 2014

Can we have the opening of submissions for Wikimania 2014 in goings-on? https://wikimania2014.wikimedia.org/wiki/Submissions EdSaperia (talk) 19:56, 25 January 2014 (UTC)

I have added it, along with the opening of applications for travel scholarships. Feel free to modify these announcements. LlamaAl (talk) 02:06, 26 January 2014 (UTC)

description of wikimediaannounce-l

wikimedia-l's "low-traffic equivalent"? I'm thinking maybe "counterpart" instead of equivalent? or "version"? --Jeremyb (talk) 06:10, 26 February 2014 (UTC)

Leaflet For Wikimedia Meta-Wiki At Wikimania 2014

Hi all,

My name is Adi Khajuria and I am helping out with Wikimania 2014 in London.

One of our initiatives is to create leaflets to increase the discoverability of various wikimedia projects, and showcase the breadth of activity within wikimedia. Any kind of project can have a physical paper leaflet designed - for free - as a tool to help recruit new contributors. These leaflets will be printed at Wikimania 2014, and the designs can be re-used in the future at other events and locations.

This is particularly aimed at highlighting less discoverable but successful projects, e.g:

• Active Wikiprojects: Wikiproject Medicine, WikiProject Video Games, Wikiproject Film

• Tech projects/Tools, which may be looking for either users or developers.

• Less known major projects: Wikinews, Wikidata, Wikivoyage, etc.

• Wiki Loves Parliaments, Wiki Loves Monuments, Wiki Loves ____

• Wikimedia thematic organisations, Wikiwomen’s Collaborative, The Signpost

For more information or to sign up for one for your project, go to:
Project leaflets
Adikhajuria (talk) 09:41, 13 June 2014 (UTC)

What does this have to do with the Main Page? PiRSquared17 (talk) 22:19, 14 June 2014 (UTC)

Migrating to translate extension

Hello. Does anyone think it would be a good idea to migrate the Main Page to the Translate extension? Pinging verdy_p. PiRSquared17 (talk) 16:57, 12 June 2014 (UTC)

I've started a bit to prepare it, but to avoid breaking pages (including those using the old model) this canot be done magically and as simply as we would like.

For now the Main Page uses many subtemplates designed in various ways, and that have kept their history. Cleanup is certainly necessary But before even thinking about restructuring it, it is possible to work subtemplate by subtemplate. This is very lengthy to do, and there's the need to keep sme useful stuff without taking care at reimporting the existing translations that are usable. verdy_p (talk) 00:11, 13 June 2014 (UTC)

Yes, we must migrate the main page. Verdy is right, for which reason I propose to keep the main page the same, but bring all the content back to the page itself (except goings on which are transcluded elsewhere too). The HTML structure and markup are not that complex, tagging the page itself will be easier. --Nemo 11:18, 16 June 2014 (UTC)

For now I'm collecting back the templates used in its parent category, because it is difficult for translators to locate where are the templates, notably because the "Edit" tan at top of translated pages does not show them the list of templates used (you can only locate them by editing the English source (and parts of the page using templates offer no "edit" or translate link (we could use a top notice in the main page that will bring to the transaltion of a translation group containing the main page and most templates specific to that page. The code is also complexified by the fact that translated Main pages use a translated page name not easily tracking which language is used for their content, so we constantly need to use a tempalte for the whoe layout that will pass the language code parameter down to all subtemplates.

The news part is still using the LangSwitch and has a visible link to translate them. The LangSwitch (forcing to edit wikicode) will probably remain for long due to the way news are managed and historied (but here also we need some cleanup because they are archived in a complex way with "Goings-on".

This is work in (slow) progress. But we cannot go fast without breaking too many things (and I certainly don't want to "simplify" it at the price of returning almost everything to English only). Changes are complex (and lengthy) to do; but this also means that the Main page is frequently outdated and not easily reformed; it has accumulated a long history of technics (including many that should not longer be recommanded for translating pages).

As much as possible,

• all pages on Meta-Wiki should use now the Translate extension (including templates), which greatly facilitates the maintenance and synchronization of contents,
• most contents should use the page content language (with pages named with a language code suffix after the English base page name: avoid translating page names themselves, translate them in the Translate tool): this language code is acessible with the {{pagelang}} template.
• some generic (site-wide) notification banners, or templates to be used in a central multilingual talk page (for all languages), or pages that are clearly not translatable (e.g. pages submitted by users for their proposals in random language without an English source), could use the user UI language instead independantly of the page content language (but this should be limited): this language code is acessible with the {{uselang}} template (whuch returns the prefered user language, or the language selected temporarily set by a "?uselang=code" query parameter in the URL,
• but all translated pages in a defined "/language-code" subpage should use preferably that page content language for all templates included in them (we'll have fallbacks for that language, else the user language or its fallbacks will be used for these templates before trying English)

Translated pages still do not necessarily use the Translate tool (for historic reasons, because their content is voluntarily not synchronized, or because migrating them is really complex and requires lot of preparation work and restoring some contents after the migration) : if a page is translated to other languages without the Translate tool, the English version should be moved to "/en" to explicitly set the page content language (because the base page has an unknown language causing diffculties with transcluded templates); the redirect will remain.

Some pages do not have any English version, even if they are translated to a few other languages: the redirect from the unsuffixed page will go to the page explicitly suffixed; also Engmosh is sometimes only a basic translation from another language (this is the case for pages like Local chapter reports whose natural language is not English), but for now the Translate tool still cannot assume another language than English for the base page verdy_p (talk) 06:07, 22 June 2014 (UTC)

Hurrah. Finally somebody started it :) Surely it should be migrated. It should also be done with other multilingual wikis' main pages which still use the old system. The task is complex and I'm too lazy to think about it wholly. But if any help on steps is needed I'm ready to give it as long as I'm on-line :) --Base (talk) 09:59, 22 June 2014 (UTC)

I have not just started it, I have made thousands migrations on Meta-Wiki, including sorting the most widely referenced content and fixing missing links in many more.

The single work of sorting the content and checking links, preparaing translations is something on which I am very active since several months. I started slowly, but now this is done on a nearly industrial scale. But there are still lots of things to do.

If you want to help, choose your language, and translate at least one item for each category in the "Categories" group, in order to help collecting pages. If you want to got fast for a first start, just translate the initial "Category:" prefix and make sure you append the language code suffix "/code" to the Engmish title if you don't want to translate everything for now. Then translate the category names to feed the translation memory, and make sure that the main page in each category (if there's one existing for your language) uses a consistant term in its title. Then start translating the most important pages here: active global policies and guidelines, tech news, description page of Wikiprojects (start by those pages that have been already prepared to use the Translate tool, there are many now, and other pages will be slowly migrated (preparing pages for translations is a lengthy task).

If you feel you can help prepare English pages for translations, try with one and ask for hep (but first you should look at how base pages were prepared because the process is not fully documented and there are still issues that we discover progressively (but such job requires some good technical knowledge, and you will need help from a Translate administrator to validate your preparation and test it (testing a translation preparation is essential, and requires doing the full translation of the page and detect things that are not well prepared and requires too much work or technical skills for translators, it must be done on at least one language you know and the layout must also be tested by initiating a translation on a RTL language such as Arabic or Hebrew, to make sure that every thing is correctly positioned, but it just requires performing a single translation for the title: the category name or just adding the language code; and ten returning back to the page to see how it looks.). Things to remember:

• don't break sentences in patchwork, and don't assume English rules for capitalization and punctuation (even a basic comma or full stop or just a space is not what you think!
• dates are complex to handle
• templates that could be used on either on untransalted pages or on translated pages must not assume that the page content language will be used.
• beware of right-to-left layouts in Arabic, Hebrew... CSS attributes using "left" or "right" or margins, borders and paddings that use parameters need special handling of the direction in the current page.
• beware of browser specific code, and make sure that pages are correct in the Mobile view and with narrow screens.
• most wikilinks should be translatable using the "Special:MyLanguage/" prefix just before the namespace. Hide these links in a tvar, and always add an explicit translable text in the wikilink displayed text. Do that even if pages are still not translated to your language, and never assume that the target will be in the same language than the source page.
• Read the documantation page of {{TNT}}.

verdy_p (talk) 16:35, 22 June 2014 (UTC)

Wikimania 2014

Please correct the Wikimania 2014 link which appears in red as of now. --Muzammil (talk) 03:16, 6 August 2014 (UTC)

Fixed by Ата diff. --Glaisher (talk) 15:39, 6 August 2014 (UTC)

Thank you very much! to both Ara and you. --Muzammil (talk) 04:29, 7 August 2014 (UTC)