Difference between revisions of "Handling Translation Issues"
From Apache OpenOffice Wiki
PetrDudacek (Talk | contribs) m |
PetrDudacek (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | This page provides information about handling translation issues for languages | + | This page provides information about handling translation issues for languages where Sun is involved in the translation. At the moment, this applies to the following languages: |
| + | * French (FR) | ||
| + | * Italian (IT) | ||
| + | * German (DE) | ||
| + | * Spanish (ES) | ||
| + | * Brazilian Portuguese (PTBR) | ||
| + | * Swedish (SV) | ||
| + | * Dutch (NL) | ||
| + | * Polish (PL) | ||
| + | * Russian (RU) | ||
| + | * Hungarian (HU) | ||
| + | * Portuguese (PT) | ||
| − | + | ||
| + | __TOC__ | ||
| + | |||
| + | ==How to submit a translation issue== | ||
A correctly submitted translation issue should: | A correctly submitted translation issue should: | ||
| − | * have Component set to '''l10n''' | + | * have '''Component''' set to '''l10n''' |
| − | * be assigned directly to the person responsible for fixing translation issues - currently '''petr_dudacek''' | + | * be assigned directly to the person responsible for fixing translation issues for the languages listed above - currently '''petr_dudacek''' |
| − | * have the language code specified in square brackets in the beginning of the Summary field, for example: '''[IT] missing | + | * have the language code specified in square brackets in the beginning of the '''Summary''' field, for example: '''[IT] missing translations in File -> Open dialog''' |
| + | |||
| + | |||
| + | Additional information that is useful for locating the strings that need to be fixed: | ||
| + | ; provining information about both UI and OLH | ||
| + | : when submitting a UI (User Interface) issue, it is always good to add information about the needed fixes in the OLH (Online Help). This means not only saying ''this needs to be fixed in the Online Help as well'' but try to find the corresponding Help page(s) and add information about how to get to that page(s). | ||
| + | ; KeyIDs | ||
| + | : each string is identified by its KeyID, which is a unique 6-digits identifier that helps to quickly locate the string in the Sun translation database. The KeyID can be obtained from a so called [[KeyID_Build|KeyID build]]. Providing the KeyIDs of strings that need to be fixed makes it very easy for the responsible engineer to find the string in the translation database. | ||
| + | ; steps to locate the string(s) | ||
| + | : when a KeyID build is not available, it is enough to provide the exact steps to locate the string, for example: | ||
| + | :In Writer: | ||
| + | :# go to '''Format''' -> '''Character...''' | ||
| + | :# select the '''Hyperlink''' tab | ||
| + | :# click the '''Events''' button to open the '''Assign Macro''' dialog | ||
| + | :The '''Remove''' button text is not translated. | ||
| + | ; suggested fix | ||
| + | :if possible, it is always useful to suggest a fix: most often, this means to suggest how the string should be translated or how the current translation should be changed. When suggesting a translation change, it is good to provide | ||
| + | :* the current (wrong) translation | ||
| + | :* the new (corrected) translation | ||
| + | :This helps the responsible engineer to see the difference. | ||
| + | When there are more strings to be fixed, it is not necessary to provide the steps to locate each of them - this would be too time consuming. In that case, the workflow described in the next section will be used. | ||
| − | + | ==Handling complex translation issues== | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 11:42, 1 June 2007
This page provides information about handling translation issues for languages where Sun is involved in the translation. At the moment, this applies to the following languages:
- French (FR)
- Italian (IT)
- German (DE)
- Spanish (ES)
- Brazilian Portuguese (PTBR)
- Swedish (SV)
- Dutch (NL)
- Polish (PL)
- Russian (RU)
- Hungarian (HU)
- Portuguese (PT)
How to submit a translation issue
A correctly submitted translation issue should:
- have Component set to l10n
- be assigned directly to the person responsible for fixing translation issues for the languages listed above - currently petr_dudacek
- have the language code specified in square brackets in the beginning of the Summary field, for example: [IT] missing translations in File -> Open dialog
Additional information that is useful for locating the strings that need to be fixed:
- provining information about both UI and OLH
- when submitting a UI (User Interface) issue, it is always good to add information about the needed fixes in the OLH (Online Help). This means not only saying this needs to be fixed in the Online Help as well but try to find the corresponding Help page(s) and add information about how to get to that page(s).
- KeyIDs
- each string is identified by its KeyID, which is a unique 6-digits identifier that helps to quickly locate the string in the Sun translation database. The KeyID can be obtained from a so called KeyID build. Providing the KeyIDs of strings that need to be fixed makes it very easy for the responsible engineer to find the string in the translation database.
- steps to locate the string(s)
- when a KeyID build is not available, it is enough to provide the exact steps to locate the string, for example:
- In Writer:
- go to Format -> Character...
- select the Hyperlink tab
- click the Events button to open the Assign Macro dialog
- The Remove button text is not translated.
- suggested fix
- if possible, it is always useful to suggest a fix: most often, this means to suggest how the string should be translated or how the current translation should be changed. When suggesting a translation change, it is good to provide
- the current (wrong) translation
- the new (corrected) translation
- This helps the responsible engineer to see the difference.
When there are more strings to be fixed, it is not necessary to provide the steps to locate each of them - this would be too time consuming. In that case, the workflow described in the next section will be used.
