View source for Thread:Support/"Templated param" in MediaWiki:Apisandbox-templated-parameter-reason/en

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 |
Hi all,
We would like to integrate Translatewiki.net with our project. The project's name is MAZI, the main output of the project is the MAZI toolkit and we would like to translate the software part of the MAZI toolkit.
This is the MAZI project's page in GitHub: https://github.com/mazi-project and this is the specific repository we would like to translate: https://github.com/mazi-project/portal
We are in a very active phase of our development and it would be great if we have your support for translating the MAZI portal. We are going to give to translatewiki staff push rights to our repo in order to integrate new translations.
We already support i18n and our files are in yaml format.
Looking forward for your reply about the next steps for the integration of translatewiki and the MAZI toolkit.
Harris
Could you point out where the i18n files are in https://github.com/mazi-project/portal/? With quick search I only found config.yaml, but i18n strings should be separated from other configuration.
You can find the i18n strings in the locales/ folder https://github.com/mazi-project/portal/tree/master/locales.
We have prepared the en file for english and the el file (Greek) for testing, translated directly from google translate.
Thanks a lot for your support
version-message-1: "This Portal is " version-message-2: "commits` behind."
Can you use variables? We call these lego messages and they are problematic for proper translations.
framadate-tab: subheader1: "Description" paragraph1: "Framadate is an open-source and free application like Doodle. It’s easy to create an appointment or a survey without registration to invite your collaborations." paragraph2: "Here is how to works" paragraph3: "" paragraph4: "" paragraph5: "" paragraph6: ""
Can the empty message be filled or removed?
Please also start adding message documentation.
OK we edited the lego messages we had and we now use variables instead.
We also filled the empty messages.
Regarding the message documentation, it is not clear to us what exactly we are supposed to do. Could we have some examples of code to check? Should we create a separate documentation page? Or it is something we can do as soon as have the MAZI project integrated in translatewiki page?
Thank you for supporting us.
Hello, could any of the administrators delete the following pages:
The first is no longer marked for translation, and the latter was created by mistake. Thanks.
Before I had searching some word like अविशिष्टपृष्ठम्, which may use in some translation, so I had get result properly. It had shown me where is the usage of the word. But now It has completely changed. Now I can not get any result. Please help to find word अविशिष्टपृष्ठम्/sa/ Thank you.
under reconsideration
I'm trying to start translating text for a Tunica-language wikipedia. Here is the required info about the language:
- ISO 639-3 language code: tun
- Language name: Tunica – Yoroni (tun)
- Left-to-right language
Thanks.
I checked Wikipedia and ethnologue and they both say it's a basically dead language with no fluent speakers. This makes me doubt how are you able to translate MediaWiki which contains many technical terms to this language. Is there a standard orthography? We are having troubles with other languages here where there is no standard orthography and then translators are fighting with each other about correct spelling.
I completely understand your skepticism. The language is being revitalized, much like Manx or Cornish have been. There is a standard orthography, a textbook, children's books, and other materials. Information can be found at the University of Hawaii's Catalogue of Endangered Languages (elcat). The revitalization project, of which the Tunica-Biloxi tribe itself is the main driver, continues to gain momentum, and we have several editors up to the task, with over 50 years of combined experience with the language. We're eager to get started on translating.
Thanks so much for your help.
Rejected. Heritage language of the Tunica-Biloxi Tribe of Marksville, Avoyelles Parish, Louisiana. There is no benefit in creating this as a UI language. Please focus your efforts on digitizing the language corpus, etc.
There is a great benefit to creating this as a UI language for the students who are learning it. I appreciate the suggestion to focus on "digitizing the corpus, etc." but that has already been done. The comment seems to imply that the language has no current speakers. The page from which the heritage language quote is pulled clearly shows that this is not the case.
Why has Cornish, which also has a small number of L2 speakers and no L1 speakers, been granted not only translatewiki permission but also its own wikipedia page, while Tunica can't even get past this step? If there is a lower limit to the number of L2 speakers that must exist in order for a wikipedia UI to be beneficial, or something else that differentiates Tunica from Cornish, please advise.
I realize that the service offered here isn't vital to the continued revitalization of the Tunica language (nor was it vital to Cornish), but it would be helpful, and it's disappointing that a single sentence in contradiction of everything that's been updated more recently can scuttle approval. If you require more proof that people speak and use this language, I'd be more than happy to provide it. There are people who want to learn in this language, as there are people who want to learn in Cornish. There is no one who speaks Cornish who doesn't also speak English, but this does not mean it wasn't beneficial to create a Cornish Wikipedia. In the same vein, it is indeed beneficial to allow for the creation of a Tunica Wikipedia.
I hope you reconsider your rejection. Additionally, I hope that, as the wheels of bureaucracy gradually turn and more updates are made on the sites of various gatekeepers of language status, it will hopefully become harder for people to find outdated information on the Tunica language that they can use to inappropriately justify rejection of a spoken language for translation.
@Plandu: There may be a good news for you, that the SIL change request 2017-015 is adopted. That request is to change the type from Extinct to Living.
@Nike and Siebrand: Should we reconsider this thread because of this request?
@Liuxinyu970226, Nike, and Siebrand: I would support revisiting this decision. I would be much obliged if the admins would consider enabling Tunica for translation.
Niklas asked for my opinion. I am not opposed to adding it. Does it add any significant maintenance overhead?
The Language committee is usually flexible when it comes to translatewiki, because it's not really part of Wikimedia. It's stricter about eligibility and approval of going out the Incubator, so I'm not saying anything about that here, as I'm really not sure what the outcome will be. But since we're mentioning the Incubator here, and since User:StevenJ81 has been so amazingly helpful lately with cleaning up old requests at Meta: Steven, can you please check whether it can be eligible?
Also, just out of curiosity: User:Plandu, can I take a look at some digitized texts? Can they be made available for Wikisource? (It's mostly a matter of license.)
"Templated parameter" in MediaWiki:Apisandbox-templated-parameter-reason/en
You do not have permission to edit this page, for the following reason:
You can view and copy the source of this page.
Return to Thread:Support/"Templated param" in MediaWiki:Apisandbox-templated-parameter-reason/en.
GENDER support for MediaWiki:Skin-minerva-blocked-drawer-creator-header
Hello! I'm helping a project in a community who can help to translate some interfaces but if they have more languages than English in the right panel, as most of them are not english-speakers and the instructors are more able to speak Basque and Spanish. Would it be possible to add more translations in the right panel to help the translators? -Theklan (talk) 19:02, 16 May 2018 (UTC)
Special:MessageGroupStats works bit strangely. When used by format "Special:MessageGroupStats/id" it shows the right statistics but Message Group indicator shows "Translatewiki.net" (group wiki-betawiki). Consequently, after (de)marking some option for (not) showing statistics for fully / none translated languages, it shows statistics for Translatewiki.net, instead of the expected group. The URL than is "Special:MessageGroupStats/id?group=wiki-betawiki&x=D".
It created problem in Template:Project subtitle but I am now solving it. I suppose that the previously used format worked before and than some software change occured which introduced this bug.
Please activate Mandailing language, ISO 639–3 code btm. Thank you.
Thanks. It's on the way: https://github.com/wikimedia/language-data/pull/17
Still somethings need confirmed:
- What's the autonym of it?
- Should it have any languages as fallback, or just translate from English?
I asked about fallback at https://incubator.wikimedia.org/wiki/Talk:Wp/btm/Alaman_Utamo#Fallback_language .
Hello, would you like to help to active and create a localisation of Rejang language (ISO 639-3 rej). I am a native speaker and active at Wikipedia Indonesia and Incubator of Rejang Wikipedia. Thank you.
Hello, good afternoon. Please create a localisation for Rejang Language (ISO 639-3 rej). I am a native speaker of Rejang Language. I am active in Wikipedia Indonesia. Thank you.
- ISO 639-3 Code: 'rej'
- 'Rejang language – Baso Jang'
- Written from left to right
FWIW, this language is written in Latin script (you wanna Arabic or Javanese scripts???); but now I'd love to know if you want fallback languages or not, and if yes, fallback to which languages?
Hello, sorry for a quite late reply. Historically our language was written in aksara RIkung, a type of abugida arose in Southern Part of Sumatera. Then, after teh colonisation and Indonesia gained its independence, native spekaers slowly favoured Latin over the aksara Rikung to write down the language. Pardon me, I do not really understand with fallback.
Hello, good night from Indonesia. Please help me to create a localisation for Rejang Language (ISO 639-3 rej). I am a native speaker of the Language and need the localisation for our project in wikipedia incubator of Rejang language. Thank you so much.
Hello, could you please give permission to User:Anok_kutai_jang to edit the page?
Nevermind, I found their request in Special:ManageTranslatorSandbox and approved it.
Hello, please grant me translator right for Rejang language (ISO 639-3: rej) and Ambon Malay (ISO 639-3: abs). Thanks.
You already have access to all supported languages. For more languages, see Translatewiki.net languages.
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.
![]() First page |
![]() Previous page |
![]() Next page |
![]() Last page |
- Support
- Closed support requests for translatewiki.net
- Open support requests for translatewiki.net
- Open support requests for translatewiki.net
- Open support requests for translatewiki.net
- Closed support requests for translatewiki.net
- Closed support requests for MediaWiki
- Open 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 translatewiki.net
- Closed support requests for translatewiki.net
- Closed support requests for translatewiki.net
- Closed support requests for translatewiki.net
- 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