Localization Profile
2011
2011 ESRI NeA Translation / Locolization Profile
2
Table of Content
1. ABOUT ESRI NORTHEAST AFRICA .............................................................................................. 3
2. ABOUT TRANSLATION / LOCALIZATION TEAM ........................................................................... 3
3.1 LOCALIZED TECHNICAL COURSES .................................................................................................... 4
3.2 TRANSLATION EN TO AR & AR TO EN ............................................................................................... 4
3.3 LOCALIZATION ....................................................................................................................... 4
3.4 KNOWLEDGEBASE .................................................................................................................... 4
3.5 TECHNICAL WRITING ................................................................................................................ 4
4.1 LOCALIZED TECHNICAL COURSES PROCESS .......................................................................................... 5
4.2 TRANSLATION EN TO AR & AR TO EN PROCESS..................................................................................... 8
4.3 LOCALIZATION ..................................................................................................................... 10
4.4 KNOWLEDGEBASE .................................................................................................................. 13
4.5 TECHNICAL WRITING .............................................................................................................. 14
5. TOOLS AND TECHNOLOGIES…. ............................................................................................. 16
5.1 TRANSLATION MEMORY ........................................................................................................... 16
5.2 SOFTWARE INVENTORY ............................................................................................................ 17
6. PREVIOUS EXPERTISE………………………… ............................................................................. 18
7. DETAILED PROJECT SAMPLE………… ..................................................................................... 20
2011 ESRI NeA Translation / Locolization Profile
3
1. About ESRI Northeast Africa
ESRI Northeast Africa (Esri NeA), the GIS leading Professional Services Provider and ESRI’s
first branded company in the Middle East and African region. Esri NeA has managed to
maintain its superiority over the years achieving a prominent regional and international
position, through its commitment to excel in the field of GIS application development
and consultation services.
Esri NeA is ISO 9001:2000 certified proving high efficiency in quality, responsibility,
resource, and analysis measurement. Esri NeA has already achieved the Capability
Maturity Model® (CMMI) certification Level 2, the most widely used model for software
development worldwide, to be the first GIS Company in MENA CMMI certified. CMMI is
an improvement model, defined by the Software Engineering Institute (SEI) and
implemented with noted success by numerous software developing organizations
worldwide, working in all types of application areas.
Surely we can say that Esri NeA is different, as it's differentiated from any other GIS
service provider in the Middle East. Esri NeA has a unique and exceptional down to
earth experience combined with a distinct perspective directed to client success. As Esri
NeA implementations are characterized by an enterprise nationwide perspective, solid
system development methodology that is supported with a formal project management
system, in addition to a staff real accumulated experience.
2. About Translation / Localization Team
As the international demand for localizing software and courses rises, successful titles
depend on their adaptation to various cultures and languages. These products tap into
a very essential activity within society: ―learn against language barrier‖. It is ―local
language‖ that first bonds us to our own culture and history, to what we see as normal,
relative to their knowledge, and appropriate. This adaptation is important since the
science in natural languages can be significantly different from one culture to another,
differences that extend from the syntactic layer of communication, to the semantic and
the pragmatic one.
The number of countries speaking Arabic language is very large and attracted us to
localize courses into its Arabic mother tongue to reach more customers in the Arab
region and Middle East. ESRI NeA worked on delivering an original course to a new
audience, in its mother tongue and within the context of its indigenous culture.
2011 ESRI NeA Translation / Locolization Profile
4
3. Translation / localization Professional Services
Esri Nea provides different varaites of translation / Localization Professional Services,
which are designed to meet various needs.
3.1 Localized Technical Courses
For the first time in the Middle East; now available all GIS courses in Arabic. We
managed to successfully translate ESRI Courses. Whether you need a specific translation
or a customized one of your own to GIS applications, Software, Tutorials, or courses.
There is only one destination; ESRI NeA you need a specific translation or a customized
one of your own to GIS applications, Software, Tutorials, or courses. There is only one
destination; ESRI NeA.
3.2 Translation En to Ar & Ar to En
Translation is the process of reading, understanding, interpreting, rephrasing and
delivering an original message—with all of its subtlety and impact—to a new audience,
in its mother tongue and within the context of its indigenous culture.
3.3 Localization
Localization is the process of translating and adapting both the content (text and style)
and the presentation (graphical and technical components) of an EXISTING product
according to the language and cultural characteristics of the target audience or region
for which it is intended.
3.4 Knowledgebase
Esri Nea worked on Translating Landmarks, Map labels, database for different projects
and purposes of spatial data services. We have made larage knowledge base contain
thousnds of records for different types of data.
3.5 Technical Writing
Technical Writing is a term that represents an increasingly broad set of activities that are
designed to communicate understandable information that can help people be
productive. Content created by technical writers has traditionally involved items such as
"how-to" manuals, reference guides and corporate reports. The emergence of new
technologies, trends and customs prompts us to expand the frame of reference that
encompasses a technical writer's activities.
2011 ESRI NeA Translation / Locolization Profile
5
4. Translation / Localization Methodology
4.1 Localized Technical Courses Process
4.1.1 Glossary Generating
Second to an in-depth knowledge of a product, glossaries are the most important
source of information for a translator. They are vital to ensure consistency in the
translation process when a job is done by several different translators. Glossaries must
always be up to date, approved by the ESRI NEA, and distributed to all linguists working
on a job. Outdated glossaries cause confusion and lead to errors. Every update to a
glossary can have major consequences in every component of a product; e.g., when a
term is changed in the software, all of the documentation and help files must be
checked for that term and updated accordingly. For this and other reasons, it is
important that there is competent language support on the client side. For example, a
language reviewer who does not speak Arabic but is equipped with an Arabic-English
CD-ROM dictionary is NOT capable of judging the quality of a translation into Arabic.
- Glossary Can be generated by
ESRI Nea Teams
Consultants of the field subjest of matter
Translators
- Glossaries should include
Product-specific terms
References to where a term occurs (software, documentation,
help file).
- Glossaries shouldn't include
Platform-specific terms, as these can be found in the respective
glossaries for the platform
Obvious terms like Yes, No, OK.
4.1.2 Text Processing
Translator should be native one.
English Expression or abbreviation should be typed beside the Arabic
translation only for its first appearance in the course.
Number of Arabic words shouldn’t exceed the English source words by
more than 100 words for the whole chapter.
2011 ESRI NeA Translation / Locolization Profile
6
Processing should be handled within Tag Editor Application first, then
within MS word if Tag Editor not applicable.
4.1.3 Proofreading
A final proofing of the manuscript, usually focused on cleaning up any typographical
errors before the manuscript is typeset.
Review grammar
Review Conjunctions
Review punctuation
Matching Glossary
4.1.4 Text / Content Editing
Remove Redundancy.
Omit Emotional Style.
Compare the style with other Experiments i.e. CAD Magazine.
Using Egyptian delicate which is commonly digested.
Compare the number of English words to Arabic words ensuring the range of
difference not exceeding 100 words over.
4.1.5 Technical Review
Reviewer should be Arabic native one.
Reviewer should be certified instructor in the course he reviews.
In-house revision to ensure high quality and security of work.
Recommended 1 reviewer per course.
4.1.6 Feedback Processing
Applying instructor recommendation to the translation.
Instructor point of view overrides translator’s one.
Holding instructor/ translator sessions for technical discussions.
4.1.7 Desktop Publishing
The following information is needed:
2011 ESRI NeA Translation / Locolization Profile
7
Name and version of the application to be used.
Font names and sizes.
Number of graphics in the document.
Is copy fitting required?
When creating a document that has to be copy fit in another language, the
expansion of the text should be taken into account. The very general rule is that a
translated text is about 30% longer than the English original. A page that is full of text
from top to bottom is hard to copy fit. Font size, leading and spacing can be
reduced, but that might make the text extremely difficult to read.
Examples for copy fitting are registration cards (which ideally should not contain
very small print squeezed into four columns with very little space between them), or
license agreements, which are generally written using a small font size. All
graphics/screenshots for a document should be supplied separately.
2011 ESRI NeA Translation / Locolization Profile
8
4.2 Translation En to Ar & Ar to En Process
4.2.1 Glossary Generating
Extracting glossary from bilingual files and creating glossary databases using advanced
CAT tools such as: Multi Term Extract. Afterwards, we run databases to quality assurance
process to prevent duplication and conflict. Now; we have all ESRI terms in Arabic in
addition to more than ten thousands glossary in hands.
4.2.2 Proofreading
A final proofing of the manuscript, usually focused on cleaning up any typographical
errors before the manuscript is typeset.
Review grammar
Review Conjunctions
Review punctuation
Matching Glossary
4.2.3 Text / Content Editing
Remove Redundancy.
Omit Emotional Style.
Compare the style with other Experiments i.e. CAD Magazine.
Using Egyptian delicate which is commonly digested.
Compare the number of English words to Arabic words ensuring the range of
difference not exceeding 100 words over.
4.2.4 Technical Review
Reviewer should be Arabic native one.
Reviewer should be certified instructor in the course he reviews.
In-house revision to ensure high quality and security of work.
Recommended 1 reviewer per course.
4.2.5 Feedback Processing
Applying Client recommendation to the translation
Client point of view overrides translator’s one
Holding Client translator sessions for technical discussions
4.2.6 Desktop Publishing
The following information is needed:
2011 ESRI NeA Translation / Locolization Profile
9
Name and version of the application to be used.
Font names and sizes.
Number of graphics in the document.
Is copy fitting required?
When creating a document that has to be copy fit in another language, the
expansion of the text should be taken into account. The very general rule is that a
translated text is about 30% longer than the English original. A page that is full of text
from top to bottom is hard to copy fit. Font size, leading and spacing can be reduced,
but that might make the text extremely difficult to read.
Examples for copy fitting are registration cards (which ideally should not contain very
small print squeezed into four columns with very little space between them), or license
agreements, which are generally written using a small font size.
All graphics/screenshots for a document should be supplied separately.
2011 ESRI NeA Translation / Locolization Profile
01
4.3 Localization
4.3.1 Localization Process
Preparation of Files prior to Localization
Analysis of the product and assessment of the level of its Internationalization
Freeze source code
Terminology research and Glossary development
Create Localization Kit
Pre-production planning, creation of a project schedule, setup of the project
team
UI Localization: Translation and Adaptation of User Interface
Isolate translatable strings from the software
Select and load Translation Memory created in prior translation projects
Translate and edit software strings
Finalize UI bilingual glossary
Resize dialog boxes
Adapt accelerator keys, tool-tips, tab order, menu options, buttons, sorting
orders in list boxes
UI Localization: Testing and Delivery
Functional testing of the localized product
Linguistic testing of the localized product
Client Review of UI
Freeze localized UI
Localizing Online Help and Translating Documentation
Screen Captures taken and incorporated in documentation
Help files and documentation translated and edited
Compile help files
Format translated documentation
Online Help Testing (including consistency checks against localized
software)
2011 ESRI NeA Translation / Locolization Profile
00
Client Review and Implementation of review changes
Client review translated GUIS
Apply clients comments and review changes
Update translation memory, get ready for the next software release
The Figure below shows a brief overview over the linguistic processes that take
place in a typical software localization project.
The Figure below shows a brief overview over the linguistic processes that take place
in a typical software localization project.
4.3.2 Software Localization:
Software GUI Localization refers to the translation of the software graphical user
interface (GUI) components, such as dialog boxes, menus, error and status
messages displayed on a user's screen. The best localization process usually starts
with the software GUI translation. Online help and user documentation translation
should only begin after all software GUI strings have been fully translated and
reviewed. This is because online help and user manuals often contain large
amount of references to the software user interface elements. This process will
ensure all GUI strings are translated consistently for all product components.
4.3.3 Online Help:
Online help is one of the largest translation components for today's localization
projects. We to localize a variety of online help systems including:
2011 ESRI NeA Translation / Locolization Profile
02
- HTML or XML based help such as HTML Help and JavaHelp (.chm)
- WinHelp 3 and 4 (.hlp and .cnt)
- Mac OS Help (Apple Help and Apple Guide)
4.3.4 Website Localization:
Web contents are often generated dynamically using templates, scripts,
backend applications, and databases. Properly localizing a website and
maintaining it for multiple languages can be a technically demanding task.
Once a website has been translated, it needs to be carefully formatted and
tested to make sure all links, forms, graphics, and scripts work properly for the
localized versions. We use a combination of software and human testing to QA
the localized site for functional, linguistic, and cosmetic issues.
4.3.5 Testing:
Localization testing focuses primarily on a product's cosmetic and linguistic
aspects. For example, once localized, the software needs to be verified on
different platforms to see if translated options fill in the target dialog boxes and if
all hot keys use unique letters, etc. When make a test, we consider the following:
If all UI strings have been tested (both hard coded and external resource strings)
Translation consistency between menu items and dialog box titles.
If accented characters display and print properly.
- Punctuation rules.
- Localized text wraps, hyphenation, and sorting.
- If hot key assignment is consistent with the target operating system.
2011 ESRI NeA Translation / Locolization Profile
03
4.4 Knowledgebase
Knowledgebase translation consists of four tables:
- Arabic Editing table: In this table, we correct and proofread the Arabic words in
the knowledgebase.
- Categories table: In this table, we categorize the words and terms in table called
Categories to reference to it when translating words subjected to this category.
- Common Name table: In this table, we collect the words and terms that is
common names.
- Compound Categories table: In this table, we collect the words and terms
subjected to this category.
2011 ESRI NeA Translation / Locolization Profile
04
4.5 Technical Writing
4.5.1 planning phase
- Gather existing information – any or all of requirement specifications, functional
descriptions, use cases, standards, contracts, etc.
- Determine which documents and other information we will create product
descriptions, installation guides, configuration guides, online help, error messages,
etc.
Note: If the documentation is to include tooltips, error messages, notifications, and
dialog boxes, we develop a plan to ensure that the wording of these is consistent, clear,
and grammatical.
4.5.2 Writing Phase:
1. Writing the document and make a list of glossary terms.
2. During slow periods, we research glossary terms using more than one source.
3. When the documentation is complete, we do a spell-check and review the work from
cover to cover.
4. Send the documentation to the reviewer for a technical accuracy check.
5. Make the required corrections.
4.5.3 Editing Phase:
In the electronic version of the document:
• Perform a spell-check on the document.
• Search the document for the following usage infractions:
- Passive voice (search for is, are, were, by, etc.); replace with the active voice.
- Future tense (search for will); replace with the present tense.
- Conditional tense (search for could); replace with the present tense.
- Contractions (search for n't and 've); replace with full words.
- Non-parallel construction (search for bulleted lists); ensure that the first word of
each list item is of the same type (noun, verb).
- Unclear antecedent (search for "This"); ensure that "This" is followed by a noun and
not a verb.
2011 ESRI NeA Translation / Locolization Profile
05
- and/or; replace with ". . . or . . ., or both".
- Forbidden words (search for "kill," "abort," and any other words that your
company has deemed inappropriate or inexact).
After you have completed the steps above, print the document and look for any
obvious problems in the following:
- Headers and footers (incorrect position of elements, incorrect text).
- Headings (inconsistent capitalization, improper hierarchy).
- Pagination (incorrect position of page number, chapters beginning on a left-
hand page, Roman numerals where there should be Arabic numerals and vice
versa).
- TOC (incorrect alignment, tab positions, and hierarchy).
- Table format (improper page breaks, poor alignment).
2011 ESRI NeA Translation / Locolization Profile
06
5. Tools and Technologies Technology has been reshaping the concept and practice of translation in many
aspects. Until some time ago, translators were expected to be able to work solely on
definite source texts with the exclusive aid of dictionaries. Specialists were called
upon where research references failed or left holes, but, even in such cases,
translators had the chance to develop familiarity with their source texts, becoming,
in many cases, experts themselves in some fields. Textual material to be translated
was basically conceptualized as having a beginning and an end, thus making
contextualization of meaning easier.
5.1 Translation Memory
Translation memory, an efficient tool for locating and re-using previously translated
phrases and sentences, is an ideal aid to the translator.
Some notable functions and features are listed below:
Indexes complete or segmented sentences. Displays the source sentences
aligned with the target translation.
Creates word and phrase match using a bilingual morphology analyzer. Utilizes
monolingual lexicons for automatic sentence alignment.
Alignment can be performed on a word-by-word basis.
Many-to-one/one-to-many word alignment can also be done, i.e. for idioms
and multiword.
Terms Elimination of ―noise‖ words, e.g. the, a, an, etc.
Ability to map entire phrases or sentences for specific contextual use.
Intuitive user interface for fast and easy manual sentence alignment.
Centralized database in both client-server and standalone systems.
Automatic bilingual translation-memory creation allows sentences to be
added dynamically.
Uses both exact-match and partial- or block-match techniques.
User-defined glossaries can be imported into translation memory.
We have many TMs in many fields that we accomplished. Our TMs include about
1000000 words. The below shows a brief overview over the TM we use in Localization:
2011 ESRI NeA Translation / Locolization Profile
07
5.2 Software Inventory
Localization Tools
CAT Tools
Trados 6.0/6.5/7.0/7.5/8/9
Alchemy Catalyst
Wordfast
Terminology Tools Trados Multiterm 6.01/7.0
Software
O/s Microsoft Windows 98/NT,
2000, XP,7
DTP & Others
Microsoft Office NT.2000,
XP, 2003, 2007, 2010
Adobe Acrobat 3.0, 4.0,
5.0, 6.0, 7.0
Adobe Illustrator7.0, 8.0,
9.0, 10.0, CS, CS2
Microsoft Visual Basic 5.0
Adobe Indesign 1.5, 2.0,
CS, CS2, CS3
Web Works Publisher 2003
for FrameMaker
2011 ESRI NeA Translation / Locolization Profile
08
6. Previous Expertise
Listed below some of our Previous Expertise:
1- LRA project
Client’s Industry – Real Estate
Type of Product – Software Localization
Type of project - Localization, Translation, review, engineering processing, resizing,
compilation
Languages Involved – English/ Arabic Translations
Amount of work – 70000 words
Time Frame – 4 weeks
2- LRS project
Client’s Industry – Real Estate
Type of Product – Software Localization
Type of project - Localization, Translation, review, engineering processing, resizing,
compilation
Languages Involved – English/ Arabic Translations
Amount of work – 100000 words
Time Frame – 7 weeks
3- ESRI ArcGIS COURSES 9.1, 9.2,9.3,10
Client’s Industry – GIS
Type of Product – Courses Localization
Type of project - Localization, Translation, review
Languages Involved – English/ Arabic Translations
Amount of work – 1000000 words
Time Frame – Ongoing Project
2011 ESRI NeA Translation / Locolization Profile
09
4- ArcGIS 9.1
Client’s Industry – GISType of Product – Software Localization (GUI)
Type of project - Localization, Translation, review, engineering processing, resizing,
compilation
Languages Involved – English/ Arabic Translations
Amount of work – 149134 words
Time Frame – 12 weeks
5- ArcGIS Server Geoportal Extension 9.3.1
Client’s Industry – GIS
Type of Product – Website Localization
Type of project - Localization, Translation, review
Languages Involved – English/ Arabic Translations
Amount of work – 30000 words
Time Frame – 7 weeks
6- ISO –CMMI Standrads
Client’s Industry – Quality Assurance
Type of Product – Software process Localization
Type of project - Localization, Translation, review
Languages Involved – English/ Arabic Translations
Amount of work – 20000 words
Time Frame – 7 weeks
7- I2 Telelcommunication Product
Client’s Industry – Telecommunication
Type of Product – Techical guides Localization
Type of project - Localization, Translation, review
Languages Involved –English/ Arabic Translations
Amount of work – 15000 words
Time Frame – 2 weeks
2011 ESRI NeA Translation / Locolization Profile
21
7. Detailed Project Sample
ArcGIS Server Geoportal Extension 9.3.1
Bussiness needs
Translation of all this project content that includs localization services,
engineering processing, text resizing and compilation of over 30,000 words. Our
client needed a reliable translation while taking on extra DTP tasks
(Template/layout adjustment, file formatting and preparation).
Solution Methodology
Web contents are often generated dynamically using templates, scripts,
backend applications, and databases. Properly localizing a website and
maintaining it for multiple languages can be a technically demanding task.
Once a website has been translated, it needs to be carefully formatted and
tested to make sure all links, forms, graphics, and scripts work properly for the
localized versions. We use a combination of software and human testing to QA
the localized site for functional, linguistic, and cosmetic issues.
Used software
Trados Workbench
TagEditor
Alchemy Catalyst
Golden Points
We offered automated workflows that helped our client manage his tasks
easier.
Our team worked to ensure that all track alignment, design and all parts of
the website were adapted correctly.
ESRINeA adapted its translation work-flow to suit our clients’ needs, by
performing the following steps:
2011 ESRI NeA Translation / Locolization Profile
20
1. GUI translation
2. Resizing and binaries compilation,
3. Client review,
4. Correction,
5. Building by the client,
6. Finally build approval
Our team used CAT tools and TM to reduce the amount of translated text
strings on over 9,000 words of content that had 100% matches, passing the
savings back to our client,
ESRINeA utilized TM over 46% of all the content, significantly reducing the
final project costs for our client.
by the end, ESRINeA completed the assignment in under 7 weeks and under
deadline. After client review of the translation in binaries format, ESRINeA
received positive feedback and was presented with new projects.
Background Information
Client’s Industry – GIS
Type of Product – Website Localization
Type of project - Localization, Translation, review
Languages Involved – English Translations
Amount of work – 30000 words
Time Frame – 7 weeks