Monday Jun 01, 2015

Oracle PaaS4SaaS UX Enablement is Global

In case you were in any doubt, the recent Oracle Applications User Experience (UX) events in Singapore and Beijing serve as a timely reminder that our PaaS4SaaS UX enablement for Oracle Partners is global.

Our toolkit is internationalized (taking advantage of those Java i18n features and the best of Unicode) and supports translation and localization requirements for different countries and regions worldwide.

Rapid Development Kit in Simplified Chinese

The Oracle Applications User Experience PaaS4SaaS enablement for partners is based on the simplified UI rapid development kit approach. Oracle Applications Cloud partners in Beijing and Singapore saw a simplified UI deployed live to an Oracle Java Cloud Service-SaaS Extension service. Try the kit yourself here.

Check out the Usable Apps blog post Deep-diving Oracle UX PaaS4SaaS Enablement in Asia and the VoX (Voice of User Experience) blog posts Showing the Oracle Applications User Experience Roadmap to Oracle's Asia Partners and Laying Out the Oracle Applications User Experience Strategy for Partners in Beijing for more details. 

Thursday Nov 21, 2013

Shout-out for Oracle Cloud and Fusion Apps Multilingual Support: Pseudo-translation Explained

Ever heard the acronym "MLS" used in the context of Oracle E-Business Suite, Fusion or Cloud Service applications, and wondered what it meant? It stands for Multilingual Support. The Fusion Applications Developer Relations blog has the architecture details and is worth a read.

The business significance of MLS, along with the applications' translations known as National Language Support (or NLS) versions, and the localizations support required for doing business in different countries and regions, is that Oracle customers can run applications in different ways to suit their business requirements.

MLS architecture provides for such requirements common in the business world as when a multi-national customer needs the same application to support a wide variety of national languages, countries or regions globally, or where a customer needs an application user interface in one national language (the language of business, English for example) but to needs enter, store, view, and publish data in other national languages. The applications can be patched easily and safely (see how the tables separate logic from translatable strings) too. You can read more about the subject in my blog on the Oracle E-Business Suite features and capabilities for global user experience.

Those "Ω'+++ '+++ '+Ø" characters you can see in the table in the developer relations blog are, in fact, the ends of what we call pseudo-translated strings. This technique of automatically padding, or adding extra, or special characters to source strings ones is used in development environments to simulate what happens when an application is translated and deployed globally.

Pseudo-translated strings simulate text expansion (strings usually get longer than the source U.S. English ones by varying lengths) and that nothing gets truncated or misplaced in the UI, are a check for multi-byte (now Unicode) character set support, bi-directionality (or Bi-Di) enablement (for Arabic and Hebrew languages, for example), and are used to detect hard-coded source strings that cannot be accessed by the translation tool (in other words, will be left in English).

The pseudo-translated version of the application must be tested in a suitable environment with realistic data by development teams and tools. If something breaks in the environment during this functional testing then it can be fixed before translation, rather than finding out the hard way, after implementation. Oracle applications uses pseudo-translation simulations for Latin character-based languages, Asian-based characters, and for Bi-Di ones too.

You can find out the basics of making internationalized and easily translatable enterprise applications that meet the needs of local workers and global businesses, and about using best practices such as pseudo-translation and more, in my SlideShare presentation delivered at the Action Week for Global Information Sharing at the Localisation Research Centre in Ireland, a few years ago. 


Monday Jun 17, 2013

Context in User Experience? Meet Use of Context in Translation. Result: Great UX Globally

What makes for a great, compelling and modern user experience? Context. Context of use, context of device, context of task, all revolving around a source of truth in the cloud: that customer, that employee, that sale, that general ledger. And what makes for a great translation (or localization as the rest of the industry would say)? Context.

Here's a presentation I delivered at Localization World, London 2013 that shows how the two can work together. For me, context is just as useful for implementers and developers as it is for the translation team. And certainly providing the context for a great string in the UI, in any language, is what makes for a great experience.

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
« August 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