I'd like to rename some keys we added to core, with the string userExpLevel. They accidentally do not fit the convention (which says, lower-case, no CamelCase). On master of MediaWiki core, the desired rename is:
rcfilters-filter-userExpLevel-newcomer-label => rcfilters-filter-user-experience-level-newcomer-label rcfilters-filter-userExpLevel-newcomer-description => rcfilters-filter-user-experience-level-newcomer-description rcfilters-filter-userExpLevel-learner-label => rcfilters-filter-user-experience-level-learner-label rcfilters-filter-userExpLevel-learner-description => rcfilters-filter-user-experience-level-learner-description rcfilters-filter-userExpLevel-experienced-label => rcfilters-filter-user-experience-level-experienced-label rcfilters-filter-userExpLevel-experienced-description => rcfilters-filter-user-experience-level-experienced-description
Should I do it? If so, in all the files, or just en and qqq? Or is this something the TranslateWiki.net team could do?
Please allow Bengali-India (bn-in) translations to be contributed for the projects on translatewiki.net
Hello, An Indian Bengali (language code: bn, country code: in) version of translations have been followed for most of the Desktop/Application projects like GNOME, KDE, XFCE, Mozilla and others and having one for the projects on translatewiki.net will help us maintain the consistency across the interfaces.
I confirm I've read the request, and will grant it. There are some implications for MediaWiki's L10n that require a considerable amount of restructuring in the "bn" namespace. That's why it may take a while before I actually have the bandwidth to fix this.
Quick list of todos:
- Move all from /bn to /bn-BD in database
- Change all codes from bn to bn-BD in MediaWiki core and extensions
- Move core MessagesBn.php to MessagesBn_BD.php
- Add $fallback in MessagesBn.php to bn-BD
- Add bn-IN to MediaWiki, with $fallback to bn-BD
- Add blacklist on bn in twn settings
- Assess impact for other twn supported products and take appropriate action
All this needs to be done within as short a timespan as possible. All together I think it will take me about 4 hours.
I think that notification options in user's preferences should be more clearly described (translated). I suppose it's kind of hard for an average user to figure it out what particular option actually means. Even with description behind the question mark I hardly know what the option is about. Is it possible to make it more "description (longer) way", like:
- Someone leaves me a message on my talk page
- Someone thanks me for my edit
- Translations (what exactly is the purpose of this?)
- Someone mentions me with a link to my user page
- My mention of someone is not sended (for what reasons?)
- My mention of someone is sended
- Page link (what happens here?)
- Someone reviews a page I've created (what does "review" means?)
- Someone changes my user rights
- Someone reverts my edit
- Someone sends me an e-mail
- Education Program
So the tooltips next to the short name aren't enough? Clarifying the meaning of the messages in qqq is certainly useful; other than that, this is likely to be a controversial change and you should tell the developers directly.
MwEmbedModules/TimedText messages are not supported by translatewiki! They are not in groups and not updated. (don't know whether rest submodules of MwEmbedModules works)
The group is missing some message documentation in its qqq files. The message documenation needs to be fixed/added first.
Yes, without documentation translation could be hard. Everyone can do that, if he/she is familiar with the extension.
The missing messages are:
Maybe some more information could be added to:
But this documentation is usually added to git and than reimportet to translatewiki.net, so this needs repository access on gerrit.
There are other messages and message groups that are translateable here, but still lack documentation.
Without repo access you should be able to add documentation via translatewiki too once the message group is re-enabled here. E.g. it was done here recently.
On Project:Autoconfirmed_users it states that every new user on translatewiki is automatically an autoconfirmed user. As a new user even after being added to the "translator" group I can confirm this is not true. This means that either the page Project:Autoconfirmed_users is wrong or that MediaWiki is misconfigured. May somebody check this please?
I wrote a discussion page on this support to enable the bodo language in transwiki.net because it's now disabled by transwiki. I want translate massages in Bodo language to create create the new Bodo Wikipedia. Bodo wikipedia is already eligible in incubator request page. Bodo wikipedia will be created after translating massagese, so iam here to translate massages but bodo langiage is disabled. But why, anyway please someone resolve the problem for bodo language in translatewiki and enable the language to translate.
- A language code from ISO 639-3 or the Ethnologue website: brx
- The language name in English and in its own language: Bodo – बर' (brx)
- Is the language RTL or LTR: LTR
- If the language is commonly written in more than one script, please say in which script the language should be enabled. Other variants can be enabled as and when translators for those variants volunteer. In Devanagari.
- (For MediaWiki) Should the language fall back to another language other than English? If so which? No need.
You may need to answer the 4th and 5th questions
Language uses Devanagari script. So, language must enabled in devanagi script , if you don't believe then go to the incubator project of bodo wikipedia. If you have another important question then ask.
Thanks. Devanagari is ok. Are people who know Bodo also likely to understand Assamese? (Assamese is the official language of the state where Bodo is most spoken according to w:Bodo language and w:Assam?)
Assamese is the official language of Assam and Both Bengali and Bodo are co-official. Bengali is most spoken in barak valley and Bodo is most spoken in four districts of Assam, which is called as BTC, Bodoland, BTAD. Bodoland is autonomous counci. So, Bodo is Official language of Bodoland and many bodo people knows Assamese , Bengali .But, What is problem in official, why you're talking about Assamese?
The only thing that you can do, after providing the necessary information, is wait, your request is not only one pending new language request.
AFAIW, there are also:
- Sylheti (syl);
- Sakizaya (ais), Amis (ami), Atayal (tay), Seediq (trv), and Saisiyat (xsy)
- Saraiki (skr);
- Kalenjin (kln);
- Tunica (tun);
- Kaikavian (kjv);
- Persian in Latin script (fa-latn);
- Ho (hoc);
- Atikamekw (atj) and Southern East Cree (crj);
- Javanese in Javanese script (jv-java);
- Northern Thai (nod);
- Bengali in India (bn-in);
- Hakka in both Hans (hak-hans) and Hant (hak-hant) scripts;
- Spanish in Nicaragua (es-ni);
- Thread:Support/Please_support_"Traditional_Mongolian_Script" – I'm confused with this request, is this Mongolian in Mongolian script (mn-mong)? Or Inner Mongolian (mvf)?
- Occitan Nissart (oc-ni)?;
- Ladino in Hebrew (lad-hebr).
So it's likely that you have to wait for half years to 3 years.
I apologise for taking your time, please answer my question. I want to translate in offline, but I don't know how to be an offline translator. I want to know how to be an offline translator. I'll appreciate it if you would answer my question.
Thank you for answering my question. I read Translating:Offline article, but I have a question. If you have the time to answer, plaese let me know how to make a request for 'Offline Translator Rights'. Thank you.
the Blockly project can be visited on https://developers.google.cn/blockly/ in China.
In cases where a date/time parameter $1 is used, alternative date $2 and time $3 parameters may be given in message documentation suggesting that these two parameters can be used instead of the combined one, in languages that need to split date and time, such as Greek.
But editor doesn't seem to recognise that $2 and $3 together are legitimate substitutes of $1, leading to an edit warning and a fuzzybot edit.
See example message MediaWiki:Userrights-expiry-current/el screenshot:
Wow I don't miss LiquidThreads :)
MediaWiki:Editinguser/tyv is an outdated copy of the English string. Could a sysop please just delete it? We don't appear to have active translators in this language.
The message is already fuzzied, what do you hope to achieve by deleting it?
This message is used in two places: as a section heading on a file description page (for example, see this) and as a page title in Special:GlobalUsage. In English, the text "Global file usage" is suitable for both places, but this does not happen in other languages, like in Portuguese. Each of the two Portuguese variants have chosen a version that is good for only one of those cases. The European Portuguese version (MediaWiki:Globalusage/pt) has "Utilização global de um ficheiro", which means "Global usage of a file", and is suitable only for the special page. The Brazilian Portuguese version (MediaWiki:Globalusage/pt-br) has "Uso global do arquivo", which means "Global usage of this file", and is suitable only for the section on the description page.
It would be good if there were two distinct messages: one for the heading on the file description page and one for the special page title.
Trying to Translate BlueSky but I can't find it. (https://www.mediawiki.org/wiki/Skin:BlueSky)
I want to install [[[Bluesky]]https://www.mediawiki.org/wiki/Skin:BlueSky] on a new Wiki but it will be in Portuguese. I am trying to find the files to translate it but I can't locate them. Can someone please help find it?