Buying professional translation for AnkiDroid in Hindi, Thai, etc?

46 views
Skip to first unread message

Nicolas Raoul

unread,
Jul 16, 2013, 2:47:21 AM7/16/13
to anki-android
Hello all,

Google Play has launched a professional translation service, and I
have registered for the beta to have an idea of what they can provide.

Translations are best done by the community, but in some cases I
believe paid-for translation might help quick-start AnkiDroid in a
country where it has no sizable community yet.

For instance, translating 01-core.xml (the indispensible part) to
Hindi would cost 42 USD. Other languages are similarly priced.
If anybody has been thinking of contributing financially, that might
be an opportunity to help in a particular area of the world.

Notable languages at 0%: Armenian, Azerbaijani, Belarusian, Bengali,
Georgian, Gujarati, Icelandic, Kazakh, Khmer, Kurdish, Latvian,
Macedonian, Mongolian, Punjabi, Swati, Tamil, Tsonga, Tswana, Urdu,
Venda, Xhosa, Zulu.
Notable languages below 10%: Croatian, Hebrew, Hindi, Lithuanian, Marathi, Thai.
Details: http://crowdin.net/project/ankidroid

PS: I just realized the Google Play translation service only offers
very few languages, and the only ones that seem applicable here are
Hindi and Thai.

Cheers!
Nicolas Raoul

stilla...@gmail.com

unread,
Sep 24, 2013, 7:08:43 AM9/24/13
to anki-a...@googlegroups.com
Cool.  FYI your project's list is missing Lao .

I'm surprised at the number of incomplete languages.  This software is such a great resource you'd think a school or something in each country would take this on.

Anyway thanks for bringing this to Android.  I emailed a few folks about contributing translations to Khmer (I'm in Cambodia) and other SE Asian languages for both AnkiDroid and the desktop version.

I also translated a few words on crowdin to Khmer.  It might be nice to know the steps to bring up the strings in the application.  For example, I hunted around for "Later" whose context is "CardEditorLaterButton" but couldn't find it in the app.  If the context were instead "Open app > Select deck > Browse cards > click on a card > ...." then I'd have an easier time.
Reply all
Reply to author
Forward
0 new messages