How to change language Japan to English Enterprise Architect - enterprise-architect

My EA language of me is Japan, I dont know Japanese, Could everyonee help me change Jp to English ?
thanks!

I think you might've downloaded from Sparxsystems.jp .
Please download it from Sparx Systems Australia ( HQ ) .

Related

Does Watson NLU support Hebrew?

does Watson NLU support Hebrew, including entities, sentiments? couldnt find it in the documentation
thanks very much
Lior
Lior, according to the documentation not. Not yet.
But, I can suggest to you use one Language Translator for using this API with Hebrew and translate to English for using each feature(English has more features available).
In the official documentation has one list of the Supported languages.
The following table shows the supported languages for each feature. Natural Language Understanding automatically detects the language of your source text by default. You can override automatic language detection if you want to specify the language manually.
Supported languages:
See the Official reference here.
You can see this article about other's API's and Supported languages. [Last Update: 24th of April 2017]
No it doesn't. It is very clear in the documentation.You can find it here.
https://console.bluemix.net/docs/services/natural-language-understanding/language-support.html#language-support
At the time of this post, the compatible languages are:
Arabic
Dutch
English
French
German
Italian
Japanese
Korean
Portuguese
Russian
Spanish
Swedish
Currently, English is the only language that supports all functions provided by Watson NLU. The rest have limited support.

Moodle login page language change

In my moodle site english and chinese are enabled. The rest of site changes to chinese when language is changed, but the login page does not change. Can anyone guide me ? Please help.
You should be able to set the default here
yourwebsite.com/admin/settings.php?section=langsettings
Or put this in config.php
$CFG->lang='yourlangcode';
In Site Administration => Language => Language Settings:
Turn off Auto detection
Set language to Chinese
Important: The server where your Moodle is hosted may be in english. If you cant change it to chinese, you may have to set the Locale field to one of these:
ISO-2022-CN (Simplified Chinese)
ISO-2022-TW (Traditional Chinese)
BIG5 (Traditional Chinese in BIG5)
GB2312 (Simplified Chinese in EUC)
And also the config.php setting as Russel said:
$CFG->lang='yourlangcode';
Please let us know if it worked!
HTH!

iOS secondary language localization

I properly set localization for es (Spanish), en (English) and ca (Catalan). Spanish and English are primary while the secondaries are like es-xx and en-xx. Catalan is a secondary that has es-ca code.
Problem is that if I launch the app for example with en-us, en.lproj resources are called because en-us does not exist. Good until this point but, if I remove catalan localization, should do the same and load primary one, es. However, does not load it and loads default one instead (en). I am missing anything? thank you
I'm not sure you're modeling the problem the right way.
The problem with removing Catalan (not sure why you'd remove a localization) is it will fall back to Spanish correct? I assume people in Barcelona and who speak Catalan also speak Spanish but it doesn't feel right to change the language on those users.
In my app I offer English (both UK, US), French, Japanese and Spanish. At startup I get the user's preferred locale and use an NSDictionary to map them to the most appropriate match and if no match is found I fallback to US English. For instance if you live in South Africa the closest English is UK English but if you live in the Philippines US English is more appropriate.
Catalan users will fallback to English unfortunately but in the next version I'll be letting users specify their preferred language from the supported language list as well so they can fallback to Spanish in the future.
Try using NSDictionary to map the user's locale to your app's available languages and see if it solves your issue. Hope this helps!

How to find the official international country code for localization with iPhone app?

I want to localize my app , and I didn't find that the official international code for it. and I found the Korean is ko, is it right? and what are other codes? and the English is en-GB, is it right ? what means about GB, and when I localize my app , I add the en.lporj or en-GB.lproj? Thank you very much!
Correct, Korean is "ko". Full list of language codes. You may be able to append a country code to the language code for resources that are specific to a country. Such as "en_GB" or "fr_CA".
Please review the Language and Locale Designations document.
English is international "en". "en_GB" is for English in Great Britain. It's best to create an en.lproj that contains your international English. If you choose to add GB specific spellings such as "Colour" instead of "Color", add them to en_GB.lproj.
A nice easy list can be found on Applingua's DevZone blog:

iphone, localization, info.plist

If I declare "Japanese, French, German, Simplified Chinese, Thai" in the "Localization" field of my app's myApp-info.plist file, will the iTunes Store detect this and correctly advertise these (together with the "Localization native development region" of "English") as the languages in which my app is available?
If not, what should I do to make sure these localizations are advertised?
Should I replace the "Localization" entry with comma-separated string of ISO_639-1 codes "en, fr, de, ja, th, zh-Hans"?
Thanking you in advance.
In your Info.plist, you need a "Localizations" (CFBundleLocalizations is the raw key name) entry of array type. Add all the supported languages to the array as separated items of the form "English", "German", etc. You don't need to use ISO codes.
On iTunes Connect, you will also want to localize the description of your app when you do the submission.
At the end of the document iOS User Experience - Internationalization Programming Topics it says that the words English, French, Portuguese,... are now deprecated and their ISO codes should be used instead.
(I wanted to add this as a comment to the most voted post, and that's why I registered in the first place, but apparently I don't have enough reputation to do so yet. Oh! And thank you, Julio, your answer helped me a lot. ;) )