Baris6161TURK

No further reply is needed.

Hi, and thanks for your changes to https://www.mediawiki.org/wiki/Cli/guide/Docker-Development-Environment resizing the images. Unfortunately I had to undo your changes today as the gifs were not actually playing for me while looking at the page. I believe you can still see this at https://www.mediawiki.org/w/index.php?title=Cli/guide/Docker-Development-Environment&oldid=5065508

No further reply is needed.

Would you please translate Help:Sample discussion into Arabic for me? It would be helpful to me to have even part of the page translated into Arabic.

These are supposed to be normal talk-page conversations. The translation does not have to be exact. Please choose Arabic names for the editors.

I don't have any interests about translating the help page into Arabic. Maybe you should find someone else that has Arabic knowledge. But thanks for leaving me message anyway.

No further reply is needed.

I was wondering what was fixed with this edit? I have this template on a few projects and was wondering if those need to be fixed also. - FlightTime (open channel) 23:14, 3 March 2022 (UTC)

It's to fix lint errorrs. It will affect when transcluded. Everything is fine in your template.

No replies for 9 months.

Hi. After changing variable names, please update the existing translation pages by yourself as possible.

Yes. I am already doing it when you updated the translation (but if I had Translation Administrator, I would have updated it immediately and update the other translations). Thanks for leaving me feedback.

Please do not do the following edits at once:

• change variable names
• split a translation unit into multiple units

It breaks the existing translations and makes migration(updating translations) hard!

Note that your edits affect ALL languages other than English.

Oh sorry for that. I was practicing for the translation markup. I will be careful for that, thx.

See and . In this case, replacing "ll" with "Special:MyLanguage" makes translations hard to update.

Aww... It's bad that the translations are being hard to update... It is so disappointing.

About Manual:Upgrading/ja. Why did you insert Japanese translation?

About Manual:Upgrading/ja. Why did you insert Japanese translation?

Sorry for inserting (actually updating) your native translations. I was fixing the translations for better experience. Not only for Japanese language, I also do that for other translations. And for the variable names, I was trying to remove red links from Special:WantedPages to prevent populating there. Adding $1, $2, $3, $4, etc. are much better to add them without a variable names. I was saw some translation that they were translating thr variable names. So yeah, I was trying to maintain this wiki for better experience.

I see. Thanks. Special:Diff/4346636/4360390

See Special:Diff/4453829. Use the following style:

<translate>
== Heading1 ==
</translate>
<translate>Sentence1.</translate>
<translate>Sentence2.</translate>

instead of:

<translate>
== Heading 1 ==

Sentence1.</translate> <translate>Sentence2.</translate>

Alright I will do that. I was being confused which I should do for mark-ups. Thanks for giving me examples.

Please wait for translation administrator to mark the translation for this template. Adding units manually will not work. Thanks for your understanding.

I’m well aware of that, I just accidentally forgot to remove them after copy‑pasting.

Alright that's fine. Everyone can make all the mistakes. Thanks.

I was already did it, but it was too confusing for long pages. Thanks for info.

Hello Baris6161TURK,

Keeping translation units as short as possible is a recommandation to facilitate translators’ work. So, when some translations are already done, we should not split units, because it does not facilitate their work but they have to translate again instead.

If a unit has been splited anyway, we have to restore translations splitting them accordingly.

I notice on Lua manual that you have resored the first unit but not the other ones, so the other translations are lost. Please copy each part in the correct place, or let it untouched to allow readers and translators to see full previous translation.

The Wikimedia Foundation Board of Trustees is organizing a call for feedback about community selection processes between February 1 and March 14. While the Wikimedia Foundation and the movement have grown about five times in the past ten years, the Board’s structure and processes have remained basically the same. As the Board is designed today, we have a problem of capacity, performance, and lack of representation of the movement’s diversity. Our current processes to select individual volunteer and affiliate seats have some limitations. Direct elections tend to favor candidates from the leading language communities, regardless of how relevant their skills and experience might be in serving as a Board member, or contributing to the ability of the Board to perform its specific responsibilities. It is also a fact that the current processes have favored volunteers from North America and Western Europe. In the upcoming months, we need to renew three community seats and appoint three more community members in the new seats. This call for feedback is to see what processes can we all collaboratively design to promote and choose candidates that represent our movement and are prepared with the experience, skills, and insight to perform as trustees?

In this regard, two rounds of feedback meetings are being hosted to collect feedback from the technical communities in Wikimedia. Two rounds are being hosted with the same agenda, to accomodate people from various time zones across the globe. We will be discussing ideas proposed by the Board and the community to address the above mentioned problems. Please sign-up according to whatever is most comfortable to you. You are welcome to participate in both as well!

• Round 1 - Feb 25, 4:00 pm UTC
• Round 2 - Mar 4, 4:00 am UTC
• Sign-up and meeting details: Wikimedia Foundation Board of Trustees/Call for feedback: Community Board seats/Conversations/MediaWiki and Wikitech

Also, please share this with other volunteers who might be interested in this. Let me know if you have any questions. KCVelaga (WMF), 14:37, 21 February 2021 (UTC)

I think it's solved now.

Could you please provide a source for the tag's deprecation? Thanks.

The deprecated tags will be listed to Special:LintErrors/obsolete-tag page when they are using <tt>...</tt>, <center>...</center>, <strike>...</strike>, and <font>...</font> tags. Those tags should be replaced with current tags. See Help:Lint errors/obsolete-tag#Deprecated elements. Thanks.

I will be careful next time.

Hi! Please don’t make content edits (basically anything apart from fixing changed translation variables) in languages you don’t speak. In this edit, for example, you introduced an obsolete spelling vietnami instead of the currently accepted vietnámi. This is just a minor issue; you could have got the inflection, cases, and so on, wrong, which can make the result incomprehensible in the worst case. Fuzzying exists for a reason, you just have to wait until someone comes who speaks the language; and readers are warned (and invited to fix it) by the pink background for the time being.

No replies for 1 week.

I can help You for learn arabic

Thanks for your interest to teach me the Arabic language. Do you know where I can learn Arabic?