Talk:Multilingualism

From Meta, a Wikimedia project coordination wiki
(Redirected from Talk:Multilingualism/en)

Polyglott wikipedians[edit]

I have contributed to wikipedia in six different languages, and I think many other wikipedians have.
I think that a stimulus to that cross-language cooperation could be the publishing of statistics about the wikipedians contributing to more than one language edition.
Is it possible?
Lele giannoni 16:03, 16 September 2009 (UTC)[reply]

Page names[edit]

Multilingualism has been translated into many languages and those translations are on pages named in the target language instead of on a language code subpage of the English page. This is in contravention of the page naming convention expressed on Meta:Interlanguage links, which itself should be moved to a more accurate page name as suggested long ago on its talk page (which I may do). If no one objects, I will move the several translations of Multilingualism to the appropriate language code subpages. --Rogerhc (talk) 01:12, 4 January 2013 (UTC)[reply]

"as of July 2004"[edit]

Can someone update this? PiRSquared17 (talk) 00:04, 14 May 2013 (UTC)[reply]

It seems to be a lot closer to 50% English now - see User:PiRSquared17/Random. PiRSquared17 (talk) 18:26, 30 May 2013 (UTC)[reply]

Move request[edit]

@Verdy p: is proposing moving this to Multilingualism, any reason it should be on this page? — xaosflux Talk 16:58, 25 January 2023 (UTC)[reply]
@Xaosflux I would like to upgrade the page using Translate extension. The source page should not have a /lang-code suffix, since the suffix will be automatically added to translation pages, including /en page. I don’t see any reason to oppose to this simple change. We can wait for Verdy_p feedback, though. -- Pols12 (talk) 17:21, 25 January 2023 (UTC)[reply]
@Pols12 I think that's a better option as well - I don't oppose it - just wanted to get feedback from the other admin, maybe something else is going on I'm not aware of. — xaosflux Talk 17:24, 25 January 2023 (UTC)[reply]
I can't remember when I made that request (that was probably a long time ago when there were fixes for msising redirects in English), but translations were made initially manually without the translation extension, a long time ago. So there may be some differences in the content in existing pages, with some addional links, we can still convert the English subpage into the parent page to use the translate extension, then mark it for translation, then reimport items from the subpage history (I can help doing these reimports, there's not a lot of pages and pages are not very long ans still have roughly the same structure), and add some items that were listed in subpages but could be useful for other languages, or add specific optional items that may be empty in English.
Such items would be for referencing for example specific talk pages in other languages than English, and documentation speaking about multilingualism support within non-English-speaking areas, or additional notes and references to external sites or projects (e.g. mulilingualism policies and support within Francophonie have reference contents not available in English, but aailable in Arabic or focusing regional language or educational and cultural programs in specific countries): those extra links however should still be useful in English pages to avoid biases, or preserve NPOV and completeness. reference links to external sites or documents do not necessarily have to be in the same language as the translated page hosted here. verdy_p (talk) 19:03, 25 January 2023 (UTC)[reply]

I reopen an edit request, since there Verdy_p has answered. I have prepared the page, and I’m ready to upgrade it to Translate extension and to migrate already done translations in the following days. --Pols12 (talk) 16:02, 31 January 2023 (UTC)[reply]

Done @Pols12:xaosflux Talk 11:09, 22 February 2023 (UTC)[reply]
Thank you. I have marked the page and migrated what I can migrate. I still discourage the translation, since a major update is needed. -- Pols12 (talk) 20:34, 22 February 2023 (UTC)[reply]