Hi, I've taken apart to translation rally (as usual) but today, 30 June 2016 I have no receive any money.
In passed months I've received some mails from other users, with the same request. I've always replied "Don't worry, in the past I've no trouble about payments, it will arrive", but today my hope fade away.
This is very strange because in the other rallies, the prize has always arrived, may be with after some months, but now has passed more than one year. Please tell us when we can receive our prize.
Thanks in advance
Currently Wikipedia in Min Dong Chinese language are written in Foochow Romanized, mainly used by Christian churches in Fuzhou. However, for most of the native people who stay in Fuzhou and other Min Dong people, they faced difficulties in understanding the Foochow Romanized. Hence, we request for enabling a new variant which is Min Dong language in Chinese characters script, which is used by most people in Min Dong. Thank you. Below are the information of variants:
Language Code:ISO 639-3:cdo
Original script: Foochow Romanized (Bàng-uâ-cê)
New script variants requested:
cdo-han: Min Dong language in Chinese characters script (閩東語漢字)
cdo-han is incorrect. Which language tag should it be?
-Hans - Han (Chinese Simplified variant) -Hant - Han (Chinese Traditional variant) -Hani - Han (Hanzi, Kanji, Hanja)
I think it'll be "hans", but I want to be certain that we are in agreement.
Well, it cannot be "hans", because if you use simplified Chinese characters, it will make Min Dong language ambiguous. Simplified Chinese characters merge many Chinese characters into one Chinese characters. For example, traditional Chinese characters have "嬭" and "奶", and they are merged in simplified Chinese characters as "奶". It doesn't matter in Mandarin Chinese, because their meanings are the same in Mandarin Chinese, but it does matter in Min Dong language, because there meanings are different in Min Dong language, and therefore it will cause ambiguity. Moreover, two traditional Chinese characters "只" and "隻" is merged in simplified Chinese characters as "只", but it really makes ambiguity in Min Dong language. So if it is really need to be chosen between "hans" and "hant", I will choose "hant", in order to make Min Dong language unambiguous.
P.S. in fact, the "hant" charset is not enough, we in fact need an entire Unicode CJK character set, because "𣍐" and "𡅏" are used very often in Min Dong language, but these two Chinese characters are located in Unicode CJK Ext-B block. "𣍐" means "cannot" in Min Dong language and "𡅏" is a common interjection in Min Dong language.
Okay, let me be unambiguous: As "han" is not a correct script tag, this cannot be used. What 4 letter language script tag should be used for the variant you request to add? If you don't know, please consult a linguist. I suggested a few, but you appear to reject all those.
I have just checked the script code in ISO 15924 standard. The script code for Min Dong language in Chinese characters script should be 500, i.e. hani.
ISO 15924 Hani (code number 500) includes Hanzi, Kanji, Hanja. "Hanzi" is used in classical Chinese (Mandarin) and several related languages in the past imperial China. As a result, Min Dong language in Chinese characters script in a part of "Hanzi", so it should be "hani".
So let's decide that the script variants for Min Dong language to be: cdo-hani.
Request for enabling new variants for Min Dong Chinese language
cdo-latn: Foochow Romanized (Bàng-uâ-cê)
New script variants requested:
cdo-hani: Min Dong language in Chinese characters script (閩東語漢字)
Our contributors on Min Dong language (cdo) Wikipedia have agreed to allow the use of both the Chinese characters and Latin orthography of Min Dong language. Therefore we request that the interwiki name for Min Dong language be changed to:
What is the status of this issue now? It has been open for years. Has the proposal by Yejianfei been approved? Siebrand, would you please reply to this message? Thanks.
Scripts (ISO 15924)
Pârsi is Latin-based script that is clear, simple, and consistent. To make reading and writing of the Persian language readily accessible to most users.
What is the "State of the Map". Is that the background for the magnifying glass, or is it something else. Some documentation might be needed to understand this sentence.
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.
I have a new application, called the Miga Data Viewer, or Miga for short - it provides a lightweight data-browsing interface for structured data contained in CSV files, and it also has some "importer" scripts to enable creating CSV files from data from Wikipedia, Wikidata and other sources. The application is available under the GPL, and it's hosted on GitHub. Would it be possible to get this application's messages to be translated by Translatewiki.net? If so, what would I have to do, both in terms of modifying the code (right now all interface text is hardcoded) and otherwise?
You'll also have to add documentation for the messages and to add @siebrand and @nikerabbit as users with push access. As for a more detailed evaluation, Siebrand or Niklas will check at some point.
Hello Yaron, I've read m:Grants:IEG/MediaWiki_data_browser/Midpoint and I saw expansion to other languages is among the next steps. If you plan to use PhoneGap, you may want to see what WikimediaMobile did for managing the localisation here on translatewiki.net. In any case, let us know if there is any blocker for you to choose and adopt some localisation format we support. Thanks!
We are running a free POS software named Pastèque and are looking for a translation platform. The project is broken into 3 parts: the web server, the desktop client and the android client. We already have translation for English, French and Norwegian (almost full) and basis for other languages. These translation files are versionned with git along the projects.
The desktop translation uses java properties files, the Android client uses the embedded xml translation and the server has now multiple json files (common translations and feature modules translations)
We are looking for an easy to use interface and more user friendly than editing text files and Translate Wiki passes all the requirements. How does it work to apply new projects on Translate Wiki?
Thanks in advance
My message haven't got any feedback since, has it been missed because of the holidays?
Anyway, we are still counting on Translatewiki to host the translation service as it is easy and pleasant to use.
Feel free to ask any question, I'm also present on IRC during office hours (GMT+1) as I work professionaly on Pastèque.
Hello Cedric, we did see this and put it on our queue but the queue is slow. We do support properties format; I suggest you submit a patch yourself to start with, see an example and the docs at mw:Help:Extension:Translate/Group configuration.
Thanks for your answer. I've set a local translatewiki once a while but it still have some flaws (mainly regarding enconding). While I'm there I'm thinking about migrating for the embedded java i18n tool to a more flexible one regarding plurals and genders.
I'll send you the files once they at least don't show those unicode escapement sequences :) (the messages are also moving a lot with the development of the next major version)
I want to add my Moodle-plugin to include MW-pages into Moodle to translatewiki.net. You can find the source code here: https://github.com/JanLuca/Moodle_Include_MW_plugin
We do not support localisation for MediaWiki extensions that are developed outside of gerrit.wikimedia.org.
this is not a MW-extension, this is a plugin for Moodle.
Got some repo URL's i'd like to give you to add to translate wiki for plugin translation - if I give you a few git paths, can you handle these?
Hey Paul. At the moment this isn't really possible. Our infrastructure isn't set up for this type of requests. We either have major projects (like Mantis BT core) or very many similar repos (like MediaWiki extensions) for which we have specific implementations. Best ask Nikerabbit in IRC for some tips if you feel like implementing the latter for MantisBT extensions.
Self-answer: the plugins seem to be https://github.com/mantisbt-plugins
I want to add this Project: https://translatewiki.net/wiki/Translating:RespondCMS in translatewiki. Would be possible to help me with steps I should follow?
Hi Edlira! Are you still interested?
I see that the translation files contain lots of string in English. Will your project be able to fall back to English if a translation is missing? We are not able to prefill missing translation with English strings.
Also some of the messages would really benefit from message documentation.
Two messages: iNaturalist:Fields/en and iNaturalist:Fields_/en are they intentionally or should it just be one message?
¡Azul! Could the Talossan language be enabled for localization?
The Talossan language is a very extensive constructed language with more than 28,000 words and it exists since 1980.
It has its own Wikipedia article on multiple Wikipedia editions, has its own official language regulator (Comità per l'Útzil del Glheþ (CÚG)), is supported by some major internationalization platforms (Crowdin, Transifex and Launchpad) and there is even a translation of The Hobbit in the making.
Currently there are already two names at the translators list, I read that one would already meet the needs of the rules.
Adding Talossan would probably also solve this ticket.
Soon we also want to start a Wikipedia edition here on the Incubator.
All requirements are met now.
Last edit: 12:59, 18 June 2016
Good day, could you add Atikamekw (atj) and Southern East Cree (crj) languages please. Both of those projects start to become active on Wikipedia and may want the opportunity to translate the interface (i.e. I will point them to translatewiki).
Thanks for taking care of translations in advance. What's the activity on incubator? I see you just created incubator:Portal:Nehirâmowin and incubator:ᑳ ᐋᐸᐦᐄᔥᑌᒡ:ᐃᔨᔨᐤ ᐊᔨᒧᐧᐃᓐ which don't seem to follow the usual incubator format? What's the status of the Cree languages here on TWN, is there a central portal like incubator:ᓃᔥᑕᒻᐹᔅᑌᒋᓂᑲᓐ? Are fallbacks possible, so that they don't always have to be translated from scratch?
There is no need to go through the Incubator since the Cree Wikipedia already exist at cr.wp. The cr code is already "activated" on translatewiki, however, it doesn't really make sense to translate the interface under the code cr which is a macro-language code, because it will be done in one of the dialects (which all have their own language ISO code) or even in a mix of dialects if translators from a different language community come to translate. The Cree community has decided it doesn't worth nor make sense to divide their Wikipedias in different projects and are happy with the work in progress on cr.wp to support the different Cree languages/dialects. There is no intent to have atj.wp or crl.wp anytime soon, and the portals you linked are not incubators, they are there to stay as they are and to grow. That being said, it doesn't mean users can't translate and use the mediawiki interface in their own language. I'm not sure why you ask about the activity level on Wikimedia, how is that a pre-requisite to have a language supported on translatewiki? For potential translators, atj just finished the normalisation of its orthograph and is undertaking pedagogic projects across their schools to develop Wikipedia and I will point them to translatewiki as well, for crj there is a very motivated contributor that will be interested in doing some translations of the interface as well.
Fallback would be English for most Cree languages and French for some (atj speakers for example mainly have French as second language). That being said we could make up a more elaborate "fallback tree". For example I asked for crj in the first post, but crl is very similar to crj (in fact the main differences are with pronunciation, they write the language pretty much the same according to a Cree language consultant and Eastern Cree speaker).
P.S. Your links to the incubator don't work, I think you in fact tried to link the Cree Wikipedia.
Last edit: 10:30, 23 January 2016
Language name: Sindarin
ISO 639-3 = sjn
Sindarin language - Lam Sindarinwa (sjn)
Written in Latin Alphabet and Sindarin's Tengwar.
It seems unlikely to support the Tengwar script (ISO 15924: Teng), because
it's not included in Unicode?
Included but is there any font support?
No, unicode is not support Tengwar. Only any font (for now...).
Which script would be used for translations? Translations should not be in mixed scripts.
Last edit: 13:17, 18 June 2016
I want to translate Chinese to Northern Tujia language (tji) but "tji" isn't listed.
Help me! 各位大哥大姐，求帮忙。
Please see Translatewiki.net languages for the needed information (in English please, sorry).
Last edit: 13:33, 18 June 2016
I'd like to start a new localization project for nod (Northern Thai). What do I have to do? The ISO 639-3 is nod. It's written from left to right. The name in English is Northern Thai, and its native name is written in two scripts: คำเมือง (Thai script) and ᨣᩴᩤᨾᩮᩥᩬᨦ (Tai Tham script).
Hi! Thanks for the interest in adding a new language. Can you follow the instructions at Translatewiki.net languages?
Alifshinobi has listed himself as a translator for this language (nod).
- Do you want the language to fall back to another language, not English?
- You mention two scripts for the language. Only Thai script is listed on the portal (ISO 15924). Does Tai Tham script have an ISO code? Will you be translating into Thai script first? Should Thai script be the script in which the language is enabled first?
Currently Wikipedia in Hakka language are written in roman script (Mainly used by Hakka people in Taiwan). However, for Hakka people who stay in China，South East Asia and others country, they faced difficulties in understanding the Hakka roman script. Hence, we request for enabling 2 new variants which are Traditional Hakka Script (which used by Hakka people in Hong Kong or Older Hakka people）and Simplified Hakka Script（used by Hakka people in China or others country). Thank you. Below are the information of variants:
- Language Code:ISO 639-3:hak
- Script:ISO 15924:Hani
- New variants requested:
- hak-hant: 客家語（繁體） (Traditional Hak script)
- hak-hans: 客家语（简体） (Simplified Hak script)
Was this discussed with the Wikimedia language committee? It may also be preferred to use automated script conversion for Hakka in this case, but we need people to actually implement that.
Are you serious? Automated script conversion for Hakka is not as simple as conversion from Arabic to Cyrillic to Latin. For example, this comprehensive Chinese character to Hakka online dictionary consists of 58,592 words or characters. Is there a department on Wikimedia which can help assist that?
By the way, there is an online Han-viet conversion tool (by clicking on the "Phiên âm 翻音" subheader) which converts entire Chinese character articles into the Romanized Vietnamese pronounciation. However that is for Vietnamese, not Hakka. No such automated script conversion for Hakka exists yet but I know some Hakka who might be willing to aid in creating this conversion system. This can prevent and avoid future script conflicts between Hakka users of different script preferences.
Thanks for your information. However, we don't know the standard procedure because we just want to add the new scripts for Hakka language despite adding a new language in Wikipedia.
Even if such a tool was eventually created, it has to be converted from Chinese characters to Romanized Hakka; not the other way around. Because certain romanized pronounications. For example, the word "sṳ" could mean "事" or "視" or "市" or "世" or "勢" or "示" or "士" and the list goes on for many other different words as well. This makes Romanized Hakka to Han Character Hakka conversion implementation to be impossible.
The conversion system must be from Chinese characters to Romanized Hakka. I humbly request you to enable the translation to hak-hant or hak-hans to be allowed.