Browse Prior Art Database

A method to make a custom build without existing flow in order to improve efficiency of translation and verification on Web UI (User Interface)

IP.com Disclosure Number: IPCOM000248116D
Publication Date: 2016-Oct-27
Document File: 6 page(s) / 96K

Publishing Venue

The IP.com Prior Art Database

Abstract

The methodology aims at providing a build and process that simplify the routine tasks performed by globalization team during each translation projects, makes it possible to present an prototype system UI (User Interface) before the product is completely constructed. By implementing the process flow and data structure proposed in this patent, the translation project team members can have a common place to precisely pin the asset, communicate and translate.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 45% of the total text.

Page 01 of 6

A method to make a custom build without existing flow in order to improve efficiency of translation and verification on Web UI (User Interface)

For customers, any incorrect UI(User Interface) translation in product easily confuses customers whether he/she is familiar with the product domain, and increases the chance that the system is used in inappropriate way may result in serious system problem. Due to limited translation project resource(time, headcount, project team member distributed in worldwide), it's inefficient or impractical to review every single words of the translated asset.

Also, a translation project starts at the development stage of product so it's not possible to supply an prototype system for either the globalization team member or the translators are not familiar with certain web system scenario/usage. With these difficulties, the completed localized system UI (User Interface) is easy to have incorrect translation content.

We would like to introduce a custom build, which only has its web UI (User Interface) but without existing flow in order to improve efficiency of translation and verification. Translator could also modify the translation directly on the custom build and the translation could be saved to resource file directly. Core idea:

The methodology aims at providing a build and process that simplify the routine tasks performed by globalization team during each translation projects, makes it possible to present an prototype system UI (User Interface) before the product is completely constructed. By implementing the process flow and data structure proposed in this patent, the translation project team members can have a common place to precisely pin the asset, communicate and translate.

The prototype system UI (User Interface) is modified from the work-in-progress system and focuses only the essential layout component of the web page.

By the precise page element pointer (XPath), the team members are able to see the target asset on the prototype page, discuss on the specific page element and verify the translated component on the prototype page in real-time.

With the indexed resource (PII files) build, the team members and translators are able to edit the target translation on the prototype page then update them to PII (resource files) on source repository.

Advantage:

Keep the same UI (User Interface) as snapshot


Remove existing flow and make a custom flow in asset
Translators can do translation directly on web UI (User Interface) with the comments from developers and even with collaborative editing
Testers can verify translation without having product operation knowledge
All the translation and TVT (Translation Verification Testing) could be done using this invention without knowing the products, just translate and edit directly.

Definition:

Resource file indexed build: A build with invisible Unicode tag as index


Page/Static page: A single web page
Page series: Collection of pages
Snapshot: Collection of "Page...