Support

Your request has been forgotten? Feel free to post a reply to bump the thread to the top. The thread summarization feature is broken, see: Phab:T245109. Very old threads have been archived.
- [View source↑]
- [History↑]
Contents
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
Suggest improvement to MediaWiki:Showdiff/en
This message should be "Show differences", since the current message "Show changes", look very alike to the near button "Publish changes" or "Save changes", which can easily cause mistake: clicking the wrong button.
Apparently a Phabricator task would be necessary to make the change, if a consensus can even be reached about this, since English messages cannot be translated here, as alluded to ("one of the developers at the project concerned will change the message") at FAQ#Improving the English source message. I don't think this is actually the best place to discuss such a change. Try Translating talk:MediaWiki instead.
Hi!
I would like to view a message which has parameters, in order to check its syntax.
For exemple, MediaWiki:Notification-header-mention-status-bundle/fr has many imbricated magic words, it would be nice to test it, previewing a draft page.
Is there a template created for this goal?
Thank you for your answer.
Unfortunately, I can’t use {{int:}} magic word because it includes the "official" translation and not the last edit.
With the given example, today {{int:}} displays a message starting with "Parmi" whereas the last version starts with "Concernant".
Maybe trying if the GENDER work or not? {{int:XXX|$2=Somebody}}
(assume that that has {{GENDER:$2|foo}}
) probably is useful
Neither int: nor Special:ExpandedTemplates is a reliable way to check how the message will work in action, especially for JavaScript messages.
However, if we assume that parsing will be okay and you just want to see the different versions, then I recommend Special:ExpandTemplates. Remember to set title to the full message title, so that correct language will be used for plurals, etc. and then use it like a template: {{MediaWiki:Notification-header-mention-status-bundle/fr|param1|param2..}}.
The downside is of course that you need to know and give all the parameters.
Thank you Nike. I didn’t know Special:ExpandTemplates.
However, I don’t achieve to give params. In the follwing code, params are not taken into account:
{{MediaWiki:Notification-header-mention-status-bundle/fr|aaa|Pols12|5|User talk:Pols12|3|2}}
.
The following code work: {{int:Notification-header-mention-status-bundle/fr|Bastard|Pols12|5|User talk:Pols12|3|2}}
But, as I explained to Nemo, int:
display the real message, and I’d like to test a new translation, not waiting for their daily export.
After https://translatewiki.net/wiki/Special:Contributions/188.32.0.0/16 was blocked here, he started making translation requests on Meta-wiki (https://meta.wikimedia.org/w/index.php?title=User_talk:Kaganer&diff=prev&oldid=17855311), and also using an IP 77.37.135.11 (https://meta.wikimedia.org/w/index.php?title=User_talk:Kaganer&diff=next&oldid=17896984).
Now per https://meta.wikimedia.org/w/index.php?title=User_talk:Metalhead64&diff=prev&oldid=17923834 I'm sure Headwikisponge12 user account belongs to the same vandal and you may want to block it.
Hmm, looks like that account was never created.
But now he is using User:Happy13241 (his message on dewiki).
Stryn, not read new comment. Other admin unblocking https://translatewiki.net/wiki/Special:Unblock/188.32.0.0/16.
@Stryn and Amire80: please, in future ping Russian community members or even write an email to them about this. We are experiencing effects of that machine-translated localisation until this very day, so there needs to be more vigilance on the part of Translatewiki sysops. We can’t notice all and we can’t untranslate anything after this gets into official localisation on Thursdays, so I am grateful that you are banning them but it is not enough in mitigating the effect.
The sign-up process is monitored by approximately 1.5 persons and none of them knows Russian very well. It is very hard to control for a persistent sock puppet who uses proxies to evade blocks. I have fuzzied all the translations made by this person. Let me know if I have missed some.
It would be great if your community could help us in any of the following ways:
- Review the translations marked as outdated: https://translatewiki.net/wiki/Special:Translate?action=translate&group=mediawiki&language=ru&filter=fuzzy
- Regularly proofread the new Russian translations: https://translatewiki.net/wiki/Special:Translate?action=proofread&group=%21recent&language=ru&filter=translated
- Participate in the general tasks required to support translatewiki.net as documented in Succession plan
Sorry for not answering quickly enough, thanks for responding to me.
This wasn’t a criticism, this is more of a regret that we are noticing the effects of this not quickly enough, although that person machine translates messages by hundreds and we could potentially do more about this if we’d notice this a lot faster. Translatewiki is still an ‘extra-territorial’ project to Wikipedia users and the like, so they don’t monitor the changes here even though it’s a very important project.
My original post was more about that, if such user translated obviously wrong text, the relevant translators could and should be notified to mitigate their wrongdoing. I’ll get to reviewing those translations later, thank you.
Hi, I'm the owner of the Blockly Games project. https://neil.fraser.name/proof/ We are gearing up for a new release which will involve some message edits. Can I get edit permission for this sub-project? Thanks!
Are you release the TranslateWiki mobile application?
There is no working mobile application right now, but you might be interested in https://www.mediawiki.org/wiki/User:Amire80/chat_bot_draft
Hi, While I translated Wikimedia:Xtools to Burmese (my), I accidentally translated about 15 texts to Marshallese language (mh). Someone with admin rights please delete those translations. Thanks.
Translated MediaWiki:Apihelp-query+imageinfo-param-prop from English to Korean.
- Source: MediaWiki:Apihelp-query+imageinfo-param-prop/en
- Destination: MediaWiki:Apihelp-query+imageinfo-param-prop/ko
The original source has "$1", but the following link says "unknown variable $1" https://translatewiki.net/w/i.php?title=Special:Translate&taction=proofread&group=%21recent&filter=%21translated&action=translate
I am a bit confused. Can anybody help with this problem?
It's not clear to which message you are linking to. Please use the "link to this message" from the dropdown from the message name.
If you mean the one outdated message in Korean, please check the definition again. It's not the same what you linked.
I've just discovered that there is difference between MediaWiki:Apihelp-query+imageinfo-param-prop and MediaWiki:Apihelp-query+imageinfo-param-prop/en. I had to translate the former one probably because I was taking the outdated English message.
I'm brand new to this and just started a test wiki over at Wikimedia Incubator and need to start translating the interface. My ISO 639-3 code is oka. The language name is 'Colville-Okanagan Salish – n̓səlxcin̓ (oka)̓ . The language is written LTR and uses it' own variation of the American Phonetic Alphabet.
Hi,
Sorry it took such a long time. I only noticed it now.
This language is available for translation now. Start here:
I also suggest reading https://blog.wikimedia.org/2017/10/26/translating-mediawiki/ .
Again, sorry it took so long.
does MediaWiki:Botpasswords-not-exist/en support GENDER?
It is needed to use {{GENDER:$1}}
in the Hebrew translation for this message. Does this message support it? It is not specified in the documentation, but the French translation uses it...
@Tgr: thoughts?
It is used via Status class: https://codesearch.wmflabs.org/search/?q=%27botpasswords-not-exist%27&i=nope&files=&repos=
Unfortunately Status really depends on the caller to call ->text() or ->parse(). I am not sure what is the caller/catcher of this Status :(
User:Nemo bis can you tell me how can I translate this ?
I don't know which language is that, but those are defined in jquery.ime in two places:
can you tell me who will change that word ?
Looks like you need to send a patch yourself, by registering on GitHub and clicking the pencil icon at https://github.com/wikimedia/jquery.ime/blob/master/src/jquery.ime.inputmethods.js
Currently it's called as "लिप्यन्तरणम्" @NehalDaveND: is this still wrong, or it's correct now (i.e. matches "transliteration")?
confirmed as fixed, thank you for regarding
- previous discussion: Portal_talk:Ko#Korean_language_name_of_ko-kp_53951
Hi. Would somebody teach me how to change language name from "한국어 (조선)" to "조선말"? I couldn't find it in CLDR and MessagesKo_kp.php of phabricator. Thanks.
You may consider submitting a Phabricator task, we may find out that how this is possible in our codes.
Hi,
Wikimedia Research would like to map section titles across six languages (ar, en, es, fr, ja, ru) and we have everything set up for it. We're planning on sending an email to Wikipedia users who can help us with this mapping. Our email needs to be in these six languages and that's why we're requesting a new project here. Would it be possible for you to create a project for this purpose?
Thanks!
Are you sure you couldn't do this with a translatable page on Meta?
We don't really "create" projects here, we just register l10n files from project's version control systems to this platform.
What about doing that as a Toolforge tool?
When translating Phabricator, pages like Phabricator:phabricator-project-4917eb42b43b64f5/qqq doesn't offer me really much of context, although maybe it's just me.
Having those autolinked to the source code is work-in-progress. I believe there isn't proper human written message documentation unless someone writes it.
Problem is that we can't be expected to provide good translations with bad documentation. I know it is not an issue of you nor from translatewiki.net itself; just feedback that this should be fixed where appropriate.
I'm sympathetic, but Phabricator developers have shown very little interest for a good i18n and what it entails (Nike was even forced to design an entirely new process to suit their non-standard methods and formats), so the alternative would be no i18n at all.
Our hope is that with this collaboration they will learn to appreciate i18n and adopt better practices. If it doesn't happen, at some point we'll need to reconsider...
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
- Support
- Open support requests for translatewiki.net
- Open support requests for MediaWiki
- Open support requests for MediaWiki
- Open support requests for translatewiki.net
- Open support requests for translatewiki.net
- Closed support requests for translatewiki.net
- Open support requests for Blockly
- Open support requests for translatewiki.net
- Closed support requests for translatewiki.net
- Closed support requests for translatewiki.net
- Closed support requests for translatewiki.net
- Closed support requests for translatewiki.net
- Open support requests for MediaWiki
- Closed support requests for translatewiki.net
- Open support requests for MediaWiki
- Closed support requests for translatewiki.net
- Open support requests for MediaWiki
- Closed support requests for translatewiki.net
- Open support requests for translatewiki.net
- Open support requests for translatewiki.net