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.

You can find this message translated into additional languages on Meta-wiki.

More languages • Wikimedia+Foundation+Annual+Plan%2F2022-2023%2FConversations%2FAnnouncement&language=&action=page&filter="}]]}">Please help translate to your language

Hello,

The Movement Communications and Movement Strategy and Governance teams invite you to discuss the 2022-23 Wikimedia Foundation Annual Plan, a plan of record for the Wikimedia Foundation's work.

These conversations continue Maryana Iskander's Wikimedia Foundation Chief Executive Officer listening tour.

The conversations are about these questions:

• The 2030 Wikimedia Movement Strategy sets a direction toward "knowledge as a service" and "knowledge equity". The Wikimedia Foundation wants to plan according to these two goals. How do you think the Wikimedia Foundation should apply them to our work?
• The Wikimedia Foundation continues to explore better ways of working at a regional level. We have increased our regional focus in areas like grants, new features, and community conversations. What is working well? How can we improve?
• Anyone can contribute to the Movement Strategy process. Let's collect your activities, ideas, requests, and lessons learned. How can the Wikimedia Foundation better support the volunteers and affiliates working in Movement Strategy activities?

You can find the schedule of calls on Meta-wiki.

The information will be available in multiple languages. Each call will be open to anyone to attend. Live interpretation will be available in some calls.

Best regards!

Hi,

I am a member of the PlanetQuest gaming community and as a good Fan, I want to create a wiki page in French, so that all players can go and find out about the game and learn new things.

But it is impossible for me to publish. I get this message:

"We're sorry, your edit was not saved as it matched the rule: new user youtube, &c.. This usually happens because the type of edit you made is often done by vandals and spammers. If that is not the case, we apologise.

If you believe your edit was constructive, please file a request here, explaining what you were trying to do."

How can I do?

Thanks in advance

Greetings

What page are you wanting to create? Does it fall with our content scope?

Tracked in Phabricator
Task T306233

On MediaWiki.org, the translation memory does not show any translation suggestions.

Could the following three pages be marked for translation in their current versions? One is new, and contains no translation markers as I wanted to leave it to the automatic tagging process.

Help:Extension:Kartographer

Help:Extension:Kartographer/Getting started (new)

Help:VisualEditor/Maps

Thank you!

Hi, I've been helping with these pages and I can confirm that they are ready to be marked for translation. We're done with major content changes, anything else will be very minor or adjustments to the <mapframe> examples which don't need translation. Is there any more action required from us?

Thank you for looking at this.

Done. I had to split up the new one so that the translatable chunks were more reasonable for translators, and to exclude large non-translatable chunks of content.

Much appreciated, both of you!

I'd love to know if there's a better way to place translation tags into a new document besides manually enclosing each segment in them. On our internal wiki there's a mechanism to infuse a new doc with tags that seemed to intelligently segment text -- that's what I thought would happen here too.

It's "intelligent" in that it breaks on paragraphs and section headings, but sadly that's about it.

@Jdforrester (WMF) Very helpful, thanks for getting our translation off the shoals!

I have the same question as Dan: the docs seem to instruct us to wrap the whole doc in a translate open and close tag, perhaps the docs should be adjusted? (1), (2).

I am sometimes no longer able to select a specific line properly and have to use the up or down key to get to the correct spot with the cursor. This started with the new line numbering feature in the Extension namespace. Did not really find a spot where to disable the line numbering in my preferences. Probably I am not the first one to report this. Note that I am using the Monobook skin and that it does not happen consistently. Anyhow it is no longer fun to edit.

The line numbers appear when you enable the "syntax highlight" button on the edit toolbar. Try disabling it. If you happen to consistently reproduce the issue (or even if you can't) you may want to bugreport it.

Thanks for your reply. Hmm, this does not help me since I would like to continue with highlighted editing. I just asked for this since it started, at least I believe so, with the introduction of line numbering. The workaround is to clear the cache after the first edit. Will report if this issue continues.

About Download#Development_releases, git clone does not work.

Terminal

\n$ git clone --recursive https://gerrit.wikimedia.org/r/mediawiki/core\nCloning into 'core'...\nfatal: project  not found\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n

"}" data-mw="{"name":"pre","attrs":{"style":"margin-top: 0; border: 0; border-top: 1px solid #bbb; background-color: #111; padding: 1em; color: #eee; overflow: auto;"},"body":{"extsrc":"\n$ git clone --recursive https://gerrit.wikimedia.org/r/mediawiki/core\nCloning into 'core'...\nfatal: project not found\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n"}}">$ git clone --recursive https://gerrit.wikimedia.org/r/mediawiki/core Cloning into 'core'... fatal: project not found fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

I see only git clone https://gerrit.wikimedia.org/r/mediawiki/core.git (i.e. without --recursive) on that page, but it seems to work both with and without --recursive for me. Maybe you had no or unreliable internet connection?

Dear all,

The Wikimedia Hackathon is coming up in May this year and there were calls for organizing local in-person events in parallel. I have applied for grant to hold local event in Nigeria.

More details about how to participate would be shared as the date nears. Before then, I can be reached via the 'email user' feature in the sidebar of this wiki in case of any inquiry.

Thanks.

You can find this message translated into additional languages on Meta-wiki.

More languages • Universal+Code+of+Conduct%2FEnforcement+guidelines%2FVote%2FClosing+message&language=&action=page&filter="}]]}">Please help translate to your language

Greetings,

The ratification voting process for the revised enforcement guidelines of the Universal Code of Conduct (UCoC) came to a close. Over 2300 Wikimedians voted across different regions of our movement. Thank you to everyone who participated in this process! The scrutinizing group is now reviewing the vote for accuracy, so please allow up to two weeks for them to finish their work.

The final results from the voting process will be announced here, along with the relevant statistics and a summary of comments as soon as they are available. Please check out the voter information page to learn about the next steps. You can comment on the project talk page on Meta-wiki in any language. You may also contact the UCoC project team by email: ucocprojectwikimedia.org

Best regards,

Movement Strategy and Governance

Dear community members,

Greetings from the EWOC Newsletter team and the education team at Wikimedia Foundation. We are very excited to share that we on tenth years of Education Newsletter (This Month in Education) invite you to join us by subscribing to the newsletter on your talk page or by sharing your activities in the upcoming newsletters. The Wikimedia Education newsletter is a monthly newsletter that collects articles written by community members using Wikimedia projects in education around the world, and it is published by the EWOC Newsletter team in collaboration with the Education team. These stories can bring you new ideas to try, valuable insights about the success and challenges of our community members in running education programs in their context.

If your affiliate/language project is developing its own education initiatives, please remember to take advantage of this newsletter to publish your stories with the wider movement that shares your passion for education. You can submit newsletter articles in your own language or submit bilingual articles for the education newsletter. For the month of January the deadline to submit articles is on the 20th January. We look forward to reading your stories.

Older versions of this newsletter can be found in the complete archive.

More information about the newsletter can be found at Education/Newsletter/About.

For more information, please contact spatnaikwikimedia.org.

---

About This Month in Education · Subscribe/Unsubscribe · Global message delivery · For the team: ZI Jony ^(Talk), Tuesday 10:19, 18 January 2022 (UTC)

Duplicate of Topic:Wc0xay4itri6uqcp

In Help:Extension:Translate, there are following codes:

<translate>
=== Reference documents for developers === <!--T:35-->
</translate>
* {{ll|Help:Extension:Translate/Installation|2=<translate><!--T:40--> Installation</translate>}} <translate><!--T:75--> and</translate> {{ll|Help:Extension:Translate/Configuration|2=<translate><!--T:60--> Configuration</translate>}}; <translate><!--T:73--> [[MediaWiki Language Extension Bundle]] should be enough in most cases.</translate>

However, this adds extra unneeded whitespaces between "Installation", "and" and "Configuration", which should have NO whitespaces between them in zh-* (Mandarin Chinese variants) language(s).

Please help fixing above grammar issue in the page.