Terminology Data Modeling for Software Localization

1
Terminology Data Modelingfor Software
Localization

• TKE 2005Copenhagen, 17 - 18 August 2005
• Prof. Dr. Klaus-Dirk Schmitz
• University of Applied Sciences Cologne
• Faculty 03 - ITMK - IIMklaus.schmitz_at_fh-koeln.de

2
Overview

• Some basic definitions
• What is localized? Which tools are used?
• Terminology management for localization
• Data modeling for localization
• Conclusion

3
What is Terminology ?

• Note If you omit the password, MultiTerm
  prompts you for a password when loading, assuming
  the database is password-protected. If you log on
  as the system administrator, you are normally
  asked whether you want exclusive access to the
  database. This is not the case when opening a
  database using parameters in this case, it is
  assumed that you do want exclusive access. Only
  when exclusive access is not available, MultiTerm
  does assume that you still want to take part in
  normal multi-user operation.

4
What is Terminology ?

• databaseexclusive accessloadinglog
  onMultiTerm multi-user operationopen a
  databaseparameterpasswordpassword-protectedpro
  mptsystem administrator

Terminology vocabulary of a subject field
Gesamtheit der Begriffe und Benennungen in
einem Fachgebiet(DIN 2342) set of
designations belonging to one special language
(ISO 1087-1)
5
What is internationalization (I18N) ?

• Developing a product or service in such a way
  that it will be easy to adapt it to other markets
  (languages and cultures)
• Goal eliminate the need to redevelop, reprogram
  or recompile the original product / content
• Carried out by the development group in
  conjunction with the localization people

6
What is localization (L10N) ?

• Adapting a product or service to a local or
  regional market
• Goal Appropriate linguistic and cultural aspects
  
• Performed by translators, localizers, language
  engineers
• LISA Localization is the cross-cultural
  communication process of preparing
  locale-specific versions of a product or service
  and consists of translation of textual material
  and adaptation of non-textual material.

7
Software localization what how
8
Localizing software

• When localizing software, you have to
  differentiate between the localization of
  resource files (RC) and the localization of
  executable files (EXE, DLL, ...). Different
  treatment of menus, dialog boxes, tool tips,
  (error) messages etc.
• Tools
• editor (RC, tag)
• localization software
• (translation memory)
• terminology system

9
Localizing online help

• When localizing online help, you have to care
  about formatting information (HLP, CHM, ...),
  document structure and links.
• Tools
• editor (HTML)
• word processor (RTF)
• translation memory
• terminology system
• localization software

10
Localizing documentation

• Localizing printed documentation (handbook,
  manual, installation guide, packaging material
  etc.) is similar to traditional translation of
  LSP texts.
• Tools
• editor
• word processor
• DTP software
• translation memory
• terminology system

11
Localizing websites

• When localizing websites (and HTML help), you
  have to care about formatting information (HTMP),
  document structure, links and multimedia
  elements.
• Tools
• editor (HTML, tag)
• translation memory
• terminology system

12
Terminology for software localization

• The selection of appropriate terminology with
  well defined concepts as well as the correct and
  consistent usage of terms are pre-conditions for
  successful software development and software
  localization
• very often innovative domains and topics
• large projects with many persons involved
• consistent terminology through all parts of the
  software product
• pre-defined terminology (operating system,
  related software, laws and regulation, corporate
  language)

13
Localization QA
Kick-off
Analysis Source Mat.
Scheduling Budgeting
Setup Terminology
Prepare Source Mat.
QA Procedure
Establish Equivalents
Screen Captures
Software Translation
Software Engineering
Software Testing
Translate Online Help
Test Online Help
Product QA Delivery
Pre-Sales Activity
Translate Documentation
DTP
Project Closure
Esselink
14
Tools for software localization

• Consistent terminology needed across all
  components of a software product, therefore
  terminology management systems
• (internally externally) repetitive texts allow
  for translation memory systems
• localization of the program itself requires
  specific localization software
• complexity and tide schedules require project
  management tools

15
Tools for software localization

• Established interaction between terminology
  management and translation memory software
• Cooperation between terminology management and
  localization tools still lacking
• Established principles of terminological data
  modeling are not always adequate for software
  localization terminology solutions? Research
  needed

16
Current procedures / approaches

• Linguistic elements (localization units, terms?)
  of the software (GUI) are transferred from
  localization tools to translation memories (TM)
• BUT TMs cannot appropriately document and manage
  these elements (no datcats, bilingual)
• Terminology management systems are ideal for
  managing these units, but not very much used in
  LION. No appropriate interchange functions
  between tools (terms units lt 4 words)

17
Terminology data modeling

• Terminological data categories? ISO 126201999 /
  new version
• definition, subject field, grammar, context,
  project code, author, date etc.
• Terminological data modeling principles? ISO
  12200 / 16642 / meta model
• Concept orientation
• Term autonomy

18
Research needed!

• Which additional data categories are needed for
  software localization terminology management?
• Is it helpful to know, if the term appears in a
  menu, in a dialog box, in an error message, in
  an online help file or in the manual?
• Is it helpful to know, if e.g. the term within a
  dialog box refers to a check button, push button
  or radio button?
• Activate Task List Aktiviert die
  Aufgabenliste Aufgabenliste
  aktivieren Aktivieren Sie die
  Aufgabenliste(status line / dialog box / user
  request)

19
Localization unit types

• Menu item
• Dialog box
• Register card
• Button
• Box
• Message
• Tooltip

20
Localization unit types

• Menu item
• Dialog box
• Register card
• Button
• Box
• Message
• Tooltip

21
Localization unit types

• Menu item
• Dialog box
• Register card
• Button
• Box
• Message
• Tooltip

22
Localization unit types

• Menu item
• Dialog box
• Register card
• Button
• Box
• Message
• Tooltip
• push button / spin button / radio button

23
Localization unit types

• Menu item
• Dialog box
• Register card
• Button
• Box
• Message
• Tooltip
• check box / text box / combo box

24
Localization unit types

• Menu item
• Dialog box
• Register card
• Button
• Box
• Message error message / status message
• Tooltip

25
Localization unit types

• Menu item
• Dialog box
• Register card
• Button
• Box
• Message
• Tooltip

26
Terminology data modeling for LION

• Additional specific data categories
• localization unit type (menu, dialog, message)
• environment subset (Windows, Linux, Apple)
• product subset (Notepad, Word 2003)
• etc.
• And
• Do we need / can we have a (trad.) definition?
• Is the meaning of context the same?

27
Research needed!

• What is a concept / terminological unit ?
• Format
• Paper jam
• Date and Time
• Print
• Save as ...
• Copy file
• Convert into Adobe PDF and send via e-mail
• File f could not be opened
• etc.

28
Conclusion 1

• Only appropriate terminology management taking
  into account all aspects of software development
  and software localization
• reduces efforts and costs for software
  localization
• brings products faster to the market
• supports user friendliness of products and
  documentation (also for the home market)
• (will also help non-mother-tongue speakers)

29
Conclusion 2

• Only a proactive and multi-disciplinary
  terminology approach will really help.
• proactivewhen concepts are created and named
• multi-disciplinaryprogrammers, interface
  designers, technical writers, web designers,
  marketing experts, hotline people, localizers
  etc.

30
Conclusion 3

• Adequate terminology management is needed for
  software localization
• with a terminology management system
• with specific data modeling (datCats)
• for all localization units ( concept)
• Requires
• improved standards and program interfaces
• improved theories, principles and methods

31
Thank you for your attention

• Prof. Dr. Klaus-Dirk Schmitz
• Fachhochschule Köln Fakultät 03 - ITMK/IIM
• Mainzer Str. 5
• 50678 Köln
• klaus.schmitz_at_fh-koeln.de