This page is only for discussing issues related to MediaWiki.org site.
Archives
|
|---|
|
|
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of Use for details.
In the original page Skin:Lakeus, the first line description is not seperated into two lines, but in Skin:Lakeus/zh, it is separated.
Also the "Planned Features" paragraph; the link to Skin:Vector using {{Ll}} with parameter nsp is set to 0; however it still shows the ns prefix in zh subpage, while the other two links does not.
Can someone help me fix these problem? I would like these to behave the same as the original page.
(1)It is caused by {{NoteTA}}.
(2){{ll}} does not support translated namespace names (皮肤, etc.).
(1) hmm, but NoteTA is required in this case (since only `zh` is available for translation and we are told to use NoteTA and Language Converter syntax to apply regional differences); I guess I'll just say "fine". Seems like can be fixed by adding a return line after {{NoteTA}}.
(2) I simply would like to remove the prefix in that ll template. Why other two links are fine?
Use Skin: instead of 皮肤:. See https://www.mediawiki.org/w/index.php?title=Special:Translations&message=Translations%3ASkin%3AVector%2FPage+display+title
Read this message in another language • Please help translate to your language
The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
They will switch all traffic back to the primary data center on Tuesday, 14 September 2021.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
Other effects:
SGrabarczuk (WMF) (talk) 00:45, 11 September 2021 (UTC)
Hi all,
I would like to add a point to the top navigation. e.g. upload file?
what is the best way to do this ?
BR,
Handrik
What is the top navigation? The links in the sidebar below the logo? See Manual:Interface/Sidebar.
Add the following to your common.js (or global.js or skin-specific JS file):
mw.util.addPortletLink(
'p-personal', '/wiki/Special:Upload',
'Upload file', 'pt-upload-link', 'Upload a file', '', '#pt-mytalk'
);
Read this message in another language • Please help translate to your language
Hello!
As we have recently announced, we, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on September 15th, 23:00 UTC on Zoom, and will last an hour. Click here to join.
Agenda
Format
The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (first three points in the agenda) will be given in English.
We can answer questions asked in English, French, Polish, and Spanish. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.
Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.
Invitation link
See you! SGrabarczuk (WMF) (talk) 03:03, 11 September 2021 (UTC)
Hello! Could a passing administrator please change the content model of my talk page (User talk:Tol) to wikitext rather than Structured Discussions? Thank you!
Thank you to everyone who participated in the 2021 Board election. The Elections Committee has reviewed the votes of the 2021 Wikimedia Foundation Board of Trustees election, organized to select four new trustees. A record 6,873 people from across 214 projects cast their valid votes. The following four candidates received the most support:
While these candidates have been ranked through the community vote, they are not yet appointed to the Board of Trustees. They still need to pass a successful background check and meet the qualifications outlined in the Bylaws. The Board has set a tentative date to appoint new trustees at the end of this month.
Hi! Recently I have improved some translations of the main page, and found several problems doing the job:
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:
{{int:word-separator/{{pagelang}}}} ({{int}} doesn’t seem to work for this use case).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.
hi everyone
My problem: I wanted to upload a picture (png.) from my computer into my wikipage.
Everything looks good until i get this:
We could not determine whether this file is suitable for Wikimedia Commons. Please only upload photos that you took yourself with your camera, or see what else is acceptable. See the guide to make sure the file is acceptable and learn how to upload it on Wikimedia Commons.
I've got the permission to use this picture, it shows nothing sexualthere is nothing violent or anything at all in it. What should i do?
thanks.
Looking at task T146938, it looks like a filter used to prevent newbie users from uploading files to commons directly from other wikis (from the visual editor of a wiki different from commons). You should be able to upload it from commons: and then link to it from your page.
@Ciencia Al Poder Hi, even in commons link which you have provided above, I tried to upload my pics and I've authorised lisence to use these photos as the photos I'm trying to upload belongs to me but still I'm getting an automated error
"We could not determine whether this file is suitable for Wikimedia Commons. Please only upload photos that you took yourself with your camera, or see what else is acceptable. See the guide to make sure the file is acceptable and learn how to upload it on Wikimedia Commons.
The content must be freely licensed. Do not copy files illegally (in violation of copyright) from other websites.
If you believe that the file meets our licensing standards: Upload the file again or click "Retry failed uploads"/"Submit modified file description"
Please guide me how can I upload these pictures.
I am getting exactly the same issue with my picture - one that I took, Any solutions?
Same issue. This is ridiculous! It also seems biased towards American public figures.
Hello everyone,
We hope all of you are as well and safe as possible during these trying times! We wanted to share some news about a change to the Community Wishlist Survey 2022. We would like to hear your opinions as well.
Summary:
We will be running the Community Wishlist Survey 2022 in January 2022. We need more time to work on the 2021 wishes. We also need time to prepare some changes to the Wishlist 2022. In the meantime, you can use a dedicated sandbox to leave early ideas for the 2022 wishes.
In the past, the Community Tech team has run the Community Wishlist Survey for the following year in November of the prior year. For example, we ran the Wishlist for 2021 in November 2020. That worked well a few years ago. At that time, we used to start working on the Wishlist soon after the results of the voting were published.
However, in 2021, there was a delay between the voting and the time when we could start working on the new wishes. Until July 2021, we were working on wishes from the Wishlist for 2020.
We hope having the Wishlist 2022 in January 2022 will be more intuitive. This will also give us time to fulfill more wishes from the 2021 Wishlist.
We are thinking how to make the Wishlist easier to participate in. We want to support more translations, and encourage under-resourced communities to be more active. We would like to have some time to make these changes.
We will have gone 365 days without a Wishlist. We encourage you to approach us. We hope to hear from you in the talk page, but we also hope to see you at our bi-monthly Talk to Us meetings! These will be hosted at two different times friendly to time zones around the globe.
We will begin our first meeting September 15th at 23:00 UTC. More details about the agenda and format coming soon!
If you have early ideas for wishes, you can use the new Community Wishlist Survey sandbox. This way, you will not forget about these before January 2022. You will be able to come back and refine your ideas. Remember, edits in the sandbox don't count as wishes!
Answer on the talk page (in any language you prefer) or at our Talk to Us meetings.
SGrabarczuk (WMF) (talk) 00:22, 7 September 2021 (UTC)
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)