He means that you should provide these informations:
- language code: skr;
- language names: Saraiki – سرائیکی (skr);
- LTR or RTL? Clearly RTL;
- script: only Arab;
- Fallback: Skr - ur - en.
Last edit: 07:06, 3 October 2016
I think we should confirm something here, per Translatewiki.net languages#Enabling a new language for localisation at translatewiki.net:
- A language code from ISO 639-3 or the Ethnologue website (for example 'de'): hoc
- The language name in English and in its own language (for example 'German – Deutsch (de)'):
- In English: Ho
- (And what's the autonym of it?)
- Is the language RTL or LTR (written from right to left or left to right): Clearly LTR
- If the language is commonly written in more than one script, please say in which script the language should be enabled...
- Devanagari is always OKay as a number of modern OSes & browsers are having its support, not sure if Warang Citi (ISO 15924 Wara) could also be added or not, do you have a font for Wara?
- (For MediaWiki) Should the language fall back to another language other than English? If so which?
2. Autonym: 𑢹𑣉𑣉 (hoc)
4. It shall be enabled in Warang Chiti script. We have fonts for Warang Chiti.
5. The fallback language shall be English.
By this answer of 4th question, is this means that only Wara should be used? Or should be 1st Wara then 2nd Deva? This is so important because I've judged incubator:Wp/hoc, many contents are still Devanagari? Things should be decided here now, as changing it after decision, even possible, could be hard due to Wikidata compatibility (IMHO).
That is because there is no available input method for Warang Chiti. Most Ho language books are printed in Warang Chiti. Nowadays it is quite rare to see Ho language printed in Devanagri or any other script. Maybe we should wait till we have proper input methods. Also, Devanagri is seen as a foreign script by the Ho people because it contains so many sounds that are not present in Ho and lacks the most common sounds of Ho language.
Please amend When using Firefox at computers other than my own, I will type in "translatewiki + Shift + Enter" which the browser then redirects to http://www.translatewiki.net/ but that URI can't be found. Although the days of a "www" subdomain are long ago, it's still worth maintaining these to redirect to the proper https://translatewiki.net/
What version of Firefox is this? I've never seen such a behaviour.
Every version since at least 2.x has had this. Have you tried it?
You need autoconfirmed rights to send emails, edit semi-protected pages and skip CAPTCHAs, see Special:ListGroupRights.
I know the advantages, but when it is granted?When can I get it?
<del>Suggest to downgrade licenses of translations to public domain (or cc0, wtfpl...)</del>
Because for a generally used translation, there's no reason based on copyright to hold up the global usage.
Translation sites like TWN can become battlefields for edit wars between people holding different sets of terminology from different sources. Random people coming just to "fix this s****ed up string" and old translators can easily start to fight with each other. These fights are often pointless and counterproductive by nature, leading to potentially decreased overall translation quality.
A written version code of conduct based on general wiki principles such as openness, friendless, and sharing should help reduce such possibility. In jargons familiar to Wikipedians, this roughly corresponds to w:WP:IAR, w:WP:CIV (w:WP:BITE), and w:WP:OWN.
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
Is more information needed? What can I do to make this happen?
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.
No, this is a special keyword used by translatewiki.net -- see Plural#Plural in CLDR. Basically, unless the language you're translating to has special pluralization rules where words change based on the number of items, you should be fine to just translate the English words into the language you're translating to.
Last edit: 14:14, 16 February 2014
Hi. The trend to force users to use HTTPS everywhere throughout entire sites instead of only login pages really pisses me off since my connection can't handle it well. It's slow  and has limited bandwidth per month and there is no better choice than making it go through a local proxy cache (HandyCache) to save bandwidth, which however doesn't work with HTTPS.
We don't support that any more. You can look into offline translation if this issue cannot be overcome.
But why you don't support HTTP anymore? Aaand to use offline translation I have to go through HTTPS still... What the actual hell?
The WMF abandoned the Commons app in 2014 and I am now maintaining it (I am only a normal Commons user). I would like to allow users to improve the localizations, as they have not been updated since 2014.
QUESTION: Should I create the localization project on a third-party tool like Crowdin? Or can I somehow "resurrect" the app's localization project here, even though the app is now community-maintained rather than an official WMF app?
If the repository is active, the project can certainly be re-enabled here. These days are quite busy, you may want to send a patch against the "translatewiki" repository in gerrit yourself.
It doesn't matter whether the app is community maintained or not. What is important that the translations end up in front of the users, i.e. for mobile apps there needs to be regular releases.
Nicolas Raoul, I see there are plans for frequent releases. Can you add @Nikerabbit and @Siebrand to the committers so that they can merge l10n updates?
I added both @Nikerabbit and @Siebrand as Github collaborators, waiting for the commits, thanks :-)
I want to publish the translatewiki URL to our users, but where does the localization actually happen? A search does not show any active Commons Android project here.
WLMMobile is a completely different app, with a different purpose (see wireframes), untouched since 2014, and we don't have strings in common.
Could you please create a new project called "Commons Android app" as a sub-project of "Wikimedia Mobile Apps"? I have read https://translatewiki.net/wiki/Translating:New_project and we seem to fit :-) Thanks a lot!
So https://github.com/nicolas-raoul/apps-android-commons the canonical repository now? Nikerabbit and Siebrand will need commit access?
When is the first release planned?
Yes, https://github.com/nicolas-raoul/apps-android-commons is the canonical repository. @siebrand is already a committer. I have invited @yuvipanda and @Nikerabbit for committer access and I am waiting for them to accept the invitation. The app has been released already: https://play.google.com/store/apps/details?id=fr.free.nrw.commons I have signed a contract with WMF allowing me to use the official "Wikimedia Commons" brand name and logo.
Are you waiting for any action on our side? We did everything you asked for, what is blocking? More and more users are asking us where to localize the app, and it is a shame that we have no URL to give them. Looking forward to hearing back from you soon, cheers!
I have been busy. I'll try to re-check the status of this soon to get this sorted out.