I have checked the regional settings in my emulator and I can't yet choose Hungarian.
I am wondering how can I make my application to work in hungarian? How do I set what language to use?
Updated answer:
Android supports Hungarian out of the box, took me some time to figure out it's called "Magyar" in the Languages list, and it properly uses all values contained in values-hu
Android does not officially support Hungarian at this time, so the emulator does not have Hungarian strings. You can see the list of supported languages on each SDK's release notes page.
Related
It is a tedious task to localize app's for multiple languages, and very often the same work is done over and over again:
For example, phrases like "OK", "Cancel" are in almost every android app.
Localization of mobile apps - Any resources available for the basics?
This question is 3 years old, I wonder if anything changed since then.
Are there any comprehensive libraries/collections which take care of this? So that I only have to translate the actually app-specific strings?
I would suggest using the Google Translator Toolkit. It supports the various localization files. It also has support for iOS and Android localization files.
Example: For Android you can upload your strings.xml you can select to which files you want to get it translated. It is automatically translated by Google Translate. It uses different colors to display how sure Google Translate is about the translation, and gives feedback about things that needs to be changed in the translations.
You can also use a translation memory. This is a database with saved translations. You can create a personal Translation memory. This contains all the translations you made. You can also use the global TM.
The global TM saves and stores translations from Translator Toolkit users everywhere. Please note that the global TM is available for anyone to see and use.
You read more about it on the support page
It has an editor build in which allows you to change the automatically translated words/sentences. You can export the translations as strings.xml again, so you can use them straightaway in your Android project.
A disadvantage: I don't think it is possible to switch between localization formats, so you have to translate all sentences for both the iOS and Android version.
You can read more about it on the support page
I published an application in English.
I do not have a plan for multi-language support yet, so the first version supports default language only.
I added ads(admob) for the second version, and localizations suddenly changed to default + 56 languages.
How can I change it back to default language only? Or is it okay to leave like that?
As stated by Andrew T. in the comment, it is quite possible that the admob library you have added is including the support for all languages, therefore you app is inheriting them.
I had the same problem, but thanks to this answer:
https://stackoverflow.com/a/15013558/2177061
I managed to solve it (I deleted the inappropriate res/- directories and the apk was not detected as multi-language anymore)
Hope this helps
We wanted to develop a web search app for Android 2.2+, and the language we're dealing with is Arabic script (RTL) based. We are using WebView as the rendering view.
So far only devices with Android 4.0+ (and some Sony phones whith 2.3) displayed the text correctly. But Android 2.x devices still consists a large part of our web users, we needed the same Arabic RTL support in Android 4.0 be availabe with our app.
To be clear, the mentioned Arabic support is not only the direction:rtl (which can be achieved with CSS), but more importantly a letter joining problem: most letters automatically change accroting to the previous and next letter when displayed.
On Windows, since 2000 version, there is a system shared library USP10.dll to handle the process. And applications have the file in their folder, would have the same support even on older Windows 98 systems.
Based on my research on the web, on android there are libicuuc.so and framework.jar to do the similar job.
My question is:
Since Android 4.0+ has the ability to hanlde the letter joining, is it possible to package the corresponding library with the apk to support Arabic in WebView?
If so, how (e.g where to put the file, and any code to add to activity)?
Many thanks in advance.
You can't add newer library for old sdk's. Old sdk's depend upon old java libraries.
I am currently developing an app which I want to support both danish and english. I know how things works with resource etc.
My app is currently running Android 2.1 (since most people in Denmark use this), but as far as I know Locale for Denmark is first avaiable in Android 2.3 (documentaion).
What wonders me, is that i got a couple of apps, which support danish language and runs on my phone (2.2). How is that possible?
Do they trick the system in some way, or do they just develop their application in Android 2.3 and make it runnable in lower version devices? Or is it possible to manipulate the native language with another app to make it "default".
I've searched around everywhere, but the danish Android community is very little.
It is actually possible to make a values-da with danish language even though it's not supported in Android 2.2 according to the documentation and it's working fine.
Don't know why it did not work earlier today.
ADB will compile your resources into apk no matter what suffix the folder values has (tested on values-qq). So I assume you can just add the proper suffix for your language, and these resources will be just ignored on pre-Android-2.3.
I am implementing overriding the locale of the device in my application allowing the selection of a different language via a preference.
Now when presenting the list of available languages I am looking at using Locale.getAvailableLocales() to see which ones are installed on the device.
Will that work and e.g. only return a smaller set of locales if they are not fulled installed down to the needed fonts and so on?
As Android's Documentation states:
Most locale-sensitive classes offer their own getAvailableLocales method, which should be preferred over this general purpose method.
To me that means you should test against these methods to be on the safe side. So it seems that the answer is no. However, in terms of installed fonts, I believe that system provides a way to display almost any language. Some symbolic glyphs might be missing but I don't think it regards to regular characters (or maybe it does in regards to some obscure scripts but I don't think you would use them).