Wednesday Feb 22, 2012

Oracle Fusion Apps NLS Release: Translations Available

Oracle Fusion Applications NLS versions (that's translations to you lot) are available.  The following translations are included (I make it 11): Arabic, Chinese (Simplified), Chinese (Traditional), Dutch, French, German, Italian, Japanese, Korean, Portuguese (Brazilian), and Spanish.

See the document Oracle Fusion Applications NLS Release Notes, 11g Release 1, Update 1 (11.1.2.0.0) [ID 1394137.1] on My Oracle Support (MOS). Access to MOS required to read the notes.

Oracle Fusion Applications Arabic version during language QA. Image may not represent final, released version.

Oracle Fusion Applications Arabic version during language QA. Image may not represent final released version.

Some notes:

  • Fusion Apps UIs, including embedded help is fully translated. Basically, seed data, messages, and anything in ADF resource bundles (I think that just about covers it) is translated. XLIFF is used.
  • Nonembedded help (that means the doc and help) is not translated in 11g Release 1, Update 1 (11.1.2.0.0). The strategy for that translation is communicated in-country and can also be explained to any Oracle Usability Advisory Board (OUAB) members who are interested in apps globalization issues.
  • Arabic requires the use of a later version of Microsoft Internet Explorer, still. Other browsers are currently in certification. If you have observations on this, let me know.
  • NLS install requires you to have English Oracle Fusion Applications 11g Release 1, Update 1 installed first. See the following docs:
    • Oracle Fusion Applications Installation Guide
    • Oracle Fusion Applications Patching Guide
    • Oracle Fusion Applications Release Notes for instructions for installing Oracle Fusion Applications 11g Release, 1 Update 1 (English, on MOS)

Wednesday Sep 07, 2011

What's in a Name: Global Considerations for Apps

Enjoyed this article about the assumptions made by programmers (and therefore developed applications) about names:

Falsehoods Programmers Believe About Names

"My system will never have to deal with names from China.
Or Japan.
Or Korea.
Or Ireland, the United Kingdom, the United States, Spain, Mexico, Brazil, Peru, Russia, Sweden, Botswana, South Africa, Trinidad, Haiti, France, or the Klingon Empire, all of which have 'weird' naming schemes in common use."

Head-wrecking stuff. Actually, it's a little unfair to blame it all on programmers, they aren't the only ones to fall into this trap, and if they have not been educated in the ways of internationalization, there's little point in blaming them. However, there are serious UX implications of these kinds of assumptions. You can read more about this impact on users in the usableapps entry Cross-Cultural Factors Should Be Considered in Enterprise Software UX Design.

"Names may require prefixes to delineate male or female employees, but sometimes there is no place to put these prefixes in the form fields. And some recent immigrants to Europe do not use last names (for example, those from Myanmar, Afghanistan, and Pakistan)."

Oracle Fusion Applications offers superb support for global names and how the user wants to see them. That's another post.

Bottom line:

  • Don't allow developers to design your apps, leave that to user experience professionals.
  • Internationalize code so that it is neutral of any one name format and can be localized for regional requirements.
  • Investigate your target market and what regional conventions means for the UX and design accordingly.
For more great information on the global challenges of handling names, and how you might deal with them on the UI and database side, see the W3C's Internationalization article Personal Names Around the World.

Friday Aug 19, 2011

Translatability Best Practices for Doc and Help

Translatability guidance aimed at user experience (UX) designers who are prototyping doc and help interactions and content. Considering these points will make your content easier to translate. Areas for attention include respecting the demands of XML structured authoring (DITA, DocBook, or other), how to share content, avoiding  translatable attributes, not contributing to the horrors of hard-coded alphabetical sorting orders, steering clear of the PRE element for tables and such like, allowing for graphics text expansion and redraw,  taking care with indexing and keywords, dealing with UPK translation issues, and so on. [Read More]
About

Oracle applications global user experience (UX): Culture, localization, internationalization, language, personalization, more. For globally-savvy UX people, so that it all fits together for Oracle's worldwide customers.

Audience: Enterprise applications translation and localization topics for the user experience professional (designers, engineers, developers, researchers)!
Profile

Ultan Ó Broin. Director, Global Applications User Experience, Oracle Corporation. On Twitter: @localization

Links

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today