| |||||||
|
|
|
DATABASES |
|
PowerGlot stores all the text found in files you give to it in databases. A database consists of a single file containing references to the files that were included in it (i.e. applications, resource files), all text that could be extracted, translations and item comments (comments are small notes that you can add to each item in the database).
Files you put in the database are called Work files in this manual.
Work files can be any kind of file containing resources: resource files (mostly used by developers), applications, INITs, control panels, and so on. The following figures shows you typical PowerGlot databases:
A simple database from an application
A database from resource files
![]()
![]()
|
|
TEXT CONTAINERS |
|
For ease of use and comprehensive presentation, PowerGlot groups all the text found in your files in text containers, which displays all the text belonging to related sources in the same list (for example, all text appearing in alert and dialog boxes is grouped in a single text container, named ÔAlerts & dialogsÕ).
Note that in a database there is no visual distinction between text items coming from one work file or another. They are all mixed together, grouped by text container. If this is a problem for you, then you should create several databases for files related to different topics.
|
|
TEXT ITEMS |
|
A text item is the basic element with which you will work in PowerGlot. It contains a single string of text (for example the title of a button in an alert box), along with its translation. PowerGlot commonly represents text items in the items list as two lines of text, the top line showing the original text and the bottom line showing the translation. One exception to this is the ÔmenusÕ text container, which shows menu items as real menus (it displays the original and translated menus side by side so you can better see what the result is).
|
|
DATABASE FILES |
|
A database containing the text from one or more work files is stored on the disk as a single file that you can easily backup, move or send to someone. The specific icon for database files is shown below.
PowerGlot database files can be moved on any machine, even if you donÕt have the original files. As long as you do not need to build a localized version of the files, you can work with just the database file on your machine.
Once you want to build a localized version of your files, just make sure the original files are available on a mounted disk. In case the original files have been moved or canÕt be found, PowerGlot will ask you to locate them.
|
|
DATABASE WINDOW |
|
The database window is where you do most of the work in PowerGlot. It is divided into three parts:
- On top, the text container pop-up menu which allows you to select the group of text you see in the list.
- In the middle, the list of text items in the current text container
- At bottom, editing fields in which you type the translations.
|
|
GLOSSARIES |
|
A glossary is a file which contains a list of terms, and the translation for each term. PowerGlot uses glossaries to automatically translate terms in your databases, thus providing for automatic pre-translation which can save you a lot of time. A carefully designed glossary can help you perform a complete translation of an application in a fraction of the time you would otherwise need.
A glossary is made of terms, and has two main properties: the source language (of source terms) and the target language (of translated terms). When translating a database with a glossary, PowerGlot checks that source language for the glossary matches the databaseÕs source language, and that target language of the glossary matches the databaseÕs target language. If the match is reversed (glossary source language matches database target language and glossary target language matches database source language), PowerGlot automatically reverses the use of source and translated terms.
One of the most useful features in PowerGlot is its ability to generate a glossary from translations you have done on a database. This tool creates a new glossary containing all the terms that have been translated. A common use for this tool is if you want to translate version 1.1 of and application, and already have translated version 1.0. Most of the text usually remains the same, so applying the glossary built from the database of version 1.0 automatically translates most of version 1.1.
As youÕll see in the Advanced features: Using previously localized versions chapter, you donÕt even need to have worked on the previous version of the software with PowerGlot. You can have it fetch text from original 1.0, match this text with the localized 1.0, build a glossary from this, then apply this glossary to the database you create for version 1.1.
|
|
GLOSSARY TERMS |
|
A term is the basic unit in a glossary. It contains a text to look for, along with its translation and various options. These options control how PowerGlot searches for the source term. The snapshot below shows a glossary term with its options.
Creation of glossary terms is described in the glossary Term options of this manual.
|
|
GLOSSARY FILES |
|
A glossary file shows up in the Finder with the icon below. It is also identified (when you choose the ÔView by nameÕ options in the Finder) as a "PowerGlot glossary".
|
|
GLOSSARY WINDOW |
|
The glossary window is divided into three parts:
- On top, the Source and Target language selectors allow you to select the languages targeted by your glossary. When applying a glossary to a database, PowerGlot checks that the source & target languages of the database match those of the glossary.
- In the middle, the terms list displays the list of terms in your glossary, along with their translation, and an icon identifying contextual terms.
- At bottom, the term edition fields, options and context selector allow you to add or modify terms and term options.
Please refer to the Glossaries section of this manual for a detailed description of the glossary editor.