Tuesday Sep 23, 2014

The Minimum you Need to Know about Internationalization

Internationalization (i18n). A vital aspect to development of enterprise applications in today's world. Without i18n at the core of development activity, product globalization would be impossible, feature localization a nightmare, and UI translation turned into a twisted joke on the eventual end user. True, thanks to the baked-in world-ready goodness of Unicode and Java itself, much of the pain we've endured in the past when it came to internationalization is gone. But...

It's still good to know the basics, and... there's still a lot of legacy stuff out there that needs to be integrated with, or needs to be rebuilt to work in, the cloud.

So, here's a great little blog post from John O'Conner (@joconner) on the absolute minimum you should know about internationalization.

John's an experienced Java and Android head, and an i18n veteran too. Yes, he really was doing i18n before it was cool!

Let's keep the following kinds of experiences behind us forever:

Realworld example of i18n #fail

A real-world example from ye olde days of #i18nfail. Character encoding failure, hard-coded line-breaks, no expansion space, no externalization from the SQL, it's a classic! Circa 1998 I think. The content has been reworked to protect the näive at the time.

To explore more about Oracle ADF internationalization, then head on over to the ADF Architecture TV YouTube channel and check out what our own Frédéric Desbiens (@blueberrycoder) has to say in his awesome series of recordings.

Friday Aug 19, 2011

UX On Your Terms: Terminology Considerations for Enterprise Apps

Terminology is a critical part of the user experience. Here's some guidance for enterprise apps UX designers to consider when creating designs and prototypes for testing.

  • When developing new terms, avoid puns, humor, jargon, symbols, or making up your own abbreviations or acronyms just to save space.

  •  Avoid compound words (that is, words consisting of multiple nouns and verbs), gerunds (that is, words ending in ing) and adjectives. These can be problematic for translation too.

  • When designing native mobile apps (for Android, iOS, Blackberry, and so on) or integrations with third-party applications, remember the user experience may require you to use terminology other than Oracle’s version of the term. In some cases, conflicts are inevitable, UX designers should be prepared to clarify to developers which version should be used and why.

    Apple iOS Starts term

    Oracle apps Starts term equivalent

Apple uses Starts and Ends in the iPhone Calendar. Oracle uses From Date and To Date, Effective Start Date and Effective End Date, From Date and To Date and so on in Oracle Fusion Applications.
  • The simple rule of terminology is that each term has only one meaning in that context. The same word can mean different things, depending how and where it is used.


    Supply a clear context for usage and a description for any new term requested. This information will be stored with the term. If you can, supply a screen shot of the prototype showing where and how the term is used to add more context. Specify what term should not be used in that context too--for example if users objected to particular terms during usability testing and you decided on something else, then include the rejected terms as deprecated versions of the approved one. 

  • Research your terminology and language style requirements. Never dumb down the language used in the UI. It is a critical part of the overall UX. If you believe a term or style is required in English then pursue it using UX testing and market justification. Terminology and style can be developed for new interactions in any language, for example, check out how Apple's iOS and Microsoft's Windows Phone 7 deal with these issues in Spanish and German respectively:

English

Spanish

Tap

Pulse

Double tap

Pulce dos veces

Touch and hold

Mantenga pulsado

Flick

Deslice el dedo

Drag

Arrastre

Pinch

Pellizco

Shake

Agite

(Source: Welinske J, Developing User Assistance for Mobile Apps)

Microsoft WP7 German style example

(Source: Microsoft)

Any other guidance on terminology for UX designers? Find those comments and share...

About

Oracle Applications Cloud global user experience (UX): Culture, localization, internationalization, language, personalization, more. A globally-savvy UX making it all fit together for Oracle's worldwide partners and 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
« March 2015
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
31
    
       
Today