Project:Village Pump

This page is only for discussing issues related to MediaWiki.org site.

To get help with MediaWiki software, ask on Project:Support desk.

Please help translate to your language

You are humbly invited to participate in the Wiki Loves Folklore 2021 an international photography contest organized on Wikimedia Commons to document folklore and intangible cultural heritage from different regions, including, folk creative activities and many more. It is held every year from the 1st till the 28th of February.

You can help in enriching the folklore documentation on Commons from your region by taking photos, audios, videos, and submitting them in this commons contest.

Please support us in translating the project page and a banner message to help us spread the word in your native language.

Kind regards,

Wiki loves Folklore International Team

MediaWiki message delivery (talk) 13:25, 6 February 2021 (UTC)

FR project page + banner : rereading done.

Christian 🇫🇷 FR (talk) 10:17, 3 August 2021 (UTC)

done.

Hello.

We are writing to you from the Digital Marketing agency Roi Scroll, on behalf of Aerobus.

We want to inform you that the https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2018/Prehackathon_Olot

with the title Wikimedia Hackathon 2018/Prehackathon Olot - MediaWiki

links to an Aerobus content http://www.aerobusbcn.com/en/

, but the link no longer works, the correct link is https://aerobusbarcelona.es/?lang=en.

We suggest you update it so that your readers are not sent to a page that no longer exists.

Thank you very much for your cooperation.

Regards.

ya esta; done, thanks.

Christian 🇫🇷 FR (talk) 09:29, 3 August 2021 (UTC)

In the 'see also' section Gerrit/Code review/Getting reviews#See also , there are two outdated links.

I wanted to change the links from http://www.gossamer-threads.com/ to https://lists.archive.carbon60.com/ because the gossamer-threads.com domain is now forwarding to a not relevant website.

But, I got an error (It seems that you're trying to add an external link to a page. ...)

Can someone change these links? Perhaps it is even better to link to archive.org

Hey there. I've replaced the links with links to our first-party archive, which are now stable, unlike in the old mailman2 times, AIUI.

There are quite a few links to that old third-party archive, sadly.

Done.

Can one of the translation admins mark Skin:Lakeus as ready to translate? Thanks!

Done.

See Ciencia Al Poder's reply.

How do I add dark theme from my personal CSS on MediaWiki? Is there any ways to do that?

You'll basically have to set all colors in your personal CSS to dark ones, with white text

Hi! Recently I have improved some translations of the main page, and found several problems doing the job:

1. It seems that there's a hardcoded whitespace after each sentence in the top section, but these whitespaces should not be seen in Chinese.
2. MediaWiki/zh-hant and MediaWiki/zh-hans don't work with LanguageConverter markups. It formerly use Template:Conversion-zh to function but making the translation quite a mess, and it also doesn't work with this (it use automatic conversion of the zh-hans version), so I removed it.

I'm asking here if anyone can provide a wise solution of these.

Other languages require whitespace after each sentence, so please compromise on whitespace.

No, there’s no need to compromise. Just like how you won’t force German translators to write common names in lower case, French to omit the space before colons or Japanese to write dates in MDY format, you shouldn’t force Chinese to have spaces where there shouldn’t be. There are multiple options to solve this:

• Conditionally insert the space, i.e. {{int:word-separator/{{pagelang}}}} ({{int}} doesn’t seem to work for this use case).
• Let translators translate whole paragraphs. This is how the Translate extension is designed to work, and it gives translators more freedom (for example, something that’s expressed in two sentences in English, may fit better in one sentence in another language).

Thanks! I think the second way may be a better solution.

Translating whole paragraphs wastes translator effort when only a sentence of a large paragraph is edited, and it invalidates a large region of text.

If only one sentence of a large paragraph is edited, then only that needs to be retranslated. Yes, the whole paragraph is marked as outdated and gets the pink background, but the translation interface shows a diff, so the translator can see which sentence they need to retranslate. They can ignore the rest (or check if the translation of the rest is correct, but that’s completely optional).

Well, that's true, but translation uses translation units instead of translating the whole page for the same reason.

Thank everyone here for your replies!

If using whole paragraphs as a translation unit is really problematic, I think the first solution is also acceptable.

DO NOT use the LanguageConverter marker (-{}-) on main page please; they would break when directly accessing the Main page instead of Main page/zh. @Tranve

I agree that translating whole paragraphs is the correct solution. Otherwise, high-quality translations are generally impossible anyway.

Translating whole paragraphs is not the same as translating the whole page.

How high-quality translations are impacted with the split of sentences? In all the translations I've made to Spanish, I have found no case where 2 or more sentences in a paragraph needed to be restructured when translated.

I run into it every now and then. For example, when the (in English) three-sentence first paragraph of Extension:Cognate/hu was split up into three units, I had no other choice than blanking one of them in Hungarian, as translating it as more than two sentences would result in text that simply doesn’t sound good. In English, short and basic sentences are usual. In Hungarian, it’s very common to use compound sentences. (Maybe it’s because Hungarian sentences tend to have less words than their English equivalents—the subject can often be left out, instead of prepositions and auxiliary verbs, we just put all information in affixes, compound words never contain spaces—except for some cases involving words with foreign origins—, and so on. For example, “I have already logged in to my mail account.” is translated as “Már bejelentkeztem a postafiókomba.”, five words less.)

Fair enough.

For large paragraphs and bullet points, I think splitting translation units is the correct approach. For example, adding a new sentence to an existing paragraph or a new bullet point to a list, when adding it to its own unit, makes only the new addition untranslated. On the other hand, merging it into the main unit, causes the entire paragraph or list to become untranslated. This is specially harmful when those annoying bots just blindly null-edit those outdated translations, making them current but without including the new content, and nobody will notice even reviewing changes.

Thank you all for your comments!

However, the problem I actually want to solve is the whitespace after each sentence. If treating the whole paragraph as a translation unit isn't a good approach, is it possible to replace the white space with something like {{int:word-separator/{{pagelang}}}}, just as what Tacsipacsi mentioned above?

UPD: It seems that this problem also exists on lots of pages besides Main Page.

Manually adding a template or something to conditionally insert white space would make wiki code much harder to read and edit (more than the current status).

I wonder if the software could provide some help here, for example, removing white space automatically when present between adjacent translation units, in languages where it's needed. There may be probably some corner cases where this is unwanted, though.

I am trying to publish the article about myself and company.

It was rejected because out of the scope of this site - see Project:About. If you continue to try and submit it you may be blocked for spamming.

so how i can fix the problem, what should i do ?

You did not read Project:About; your content is not appropriate here. Please stop asking.

I am trying to add the following link

* Moodle documentation wiki (customised layout, components and styles)

to the list at Skin:Chameleon#Examples and I am getting the error message ending with "If you believe that you received this message in error or have a legitimate need for the link, please file a request here." And so do I. Thanks in advance (and thanks the Chameleon author and contributors for such a nice skin).

You should be able to do so now.

The Movement Strategy recommendations published this year made clear the importance of establishing stronger communications within our movement. To this end, the Foundation wants to gather insights from communities on ways we all might more consistently communicate about our collective work, and better highlight community contributions from across the movement. Over the coming months, we will be running focus groups and online discussions to collect these insights. Visit the page on Meta-Wiki to sign up for a focus group or participate in the discussion.

ELappen (WMF) (talk) 18:56, 18 November 2020 (UTC)

My Page Create is not completing. My submission was rejected. Please accept my submission.

No, that is not appropriate for this wiki. Please read Project:About.