internationalization

问题 I use GWT i18n Messages to translate messages: @DefaultLocale("en") public interface Messages extends com.google.gwt.i18n.client.Messages { @DefaultMessage("Size") String size(); } For German I have the Messages_de.properties file. size=Größe äüö ÄÖÜ In one of my UIBinder templates I use <ui:text with="{messages.size}"/> When the user's browser is de I get Grösse ÄÖÜ ÄÖÜ instead of Größe äüö ÄÖÜ being displayed. My workspace as well as my .properties file is set to UTF8. How can I get the

问题 Using i18next, how can I translate JQuery Mobile widgets? Specifically, I'd like to know how to do that without resorting to using data-i18n-target to modify generated inner elements, because that is brittle since future widget versions may change the generated code. Is there a specific page lifecycle event I can subscribe to in order to be able to have i18next modify the DOM before the widget transformation happens? In this example (see jsfiddle), some markup is correctly translated, but

问题 Settings.py constants TIME_ZONE = 'Europe/Vilnius' LANGUAGE_CODE = 'lt' USE_I18N = True USE_L10N = True USE_TZ = True MIDDLEWARE_CLASSES = ( 'django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', ) If I add LocaleMiddleware to the

问题 I'm localizing my Angular app using Angular's i18n tools, which extract text from HTML templates into an xlf file, and then build a localized version of the whole app using AOT (ahead of time compilation). My question is: Can is use this framework to extract string literals in typescript code, so they are listed in the same xlf file and replaced in the localized AOT build? Ideally, I'd like to write something like this in my typescript code: foo() { this.bar = i18n('baz'); and the string 'baz

问题 I have a UITableview with a UISearchBar, which contain Japanese words, and I want to test if it works to search Japanese words with Japanese keyboard. I can't find how to change the default keyboard on iPhone simulator. 回答1: Open on simulator Settings application ->General->International->Language . Select here your language and keyboard will have required letters. 回答2: I think what we really want to do is add an international keyboard, not change the language of the simulator. Open Simulator

问题 I have a directory with a name that contains Japanese characters, and I need to use the zip utils in java.util.zip to write it to a zip file. Writing the zip file succeeds, but when I open the resulting zip file with either Windows' built-in compressed file utility or 7-Zip, the directory with Japanese characters in the name appears as a bunch of garbage characters. I do have the Japanese/East Asian language pack installed on my system -- I can create directories with Japanese names, so that

问题 For example, I would like this default ASP.NET MVC 4 validation message: The value 'qsdqsdqs' is not valid for Montant to be displayed in french. I found this package http://nuget.org/packages/Microsoft.AspNet.Mvc.fr/ and installed it but how do I get it to work ? I added <globalization culture="fr-FR" uiCulture="auto:fr" /> to web.config and referenced the dll but the message is still in english 回答1: First of all you should keep your messages in Resources files like that: Resources

问题 How do I use NSLocalizedString to build a string with multiple parameters while giving the translator control to change the order if they wish? An example in my Localizable.string is: "score_out_of"="Your score is %i out of %i"; And would be invoked like [NSString stringWithFormat:NSLocalizedString(@"score_out_of", nil), correct, total]; But on some locales the grammar rules might dictate that total goes before correct. In Objective C it seems the interpolation order is hard coded. In other

问题 I am in the process of internationalizing a large legacy codebase in C++, and I am faced with a difficult decision: should I use boost::locale's or std c++ locales? I am commited to using utf-8. We have to do a reasonably broad range of text processing, although it is not the core of what our code does, it is important. We can expect to do most of what one might need to do: time, date, number, and money formatting, collation, regexp, substring isolation, interaction with boost::filesystem, DB

问题 Here is a quick test program: public static void main( String[] args ) { Date date = Calendar.getInstance().getTime(); System.out.println("Months:"); printDate( "MMMM", "en", date ); printDate( "MMMM", "es", date ); printDate( "MMMM", "fr", date ); printDate( "MMMM", "de", date ); System.out.println("Days:"); printDate( "EEEE", "en", date ); printDate( "EEEE", "es", date ); printDate( "EEEE", "fr", date ); printDate( "EEEE", "de", date ); } public static void printDate( String format, String