|

What is the type of software?
What is the operating system?
What is the development environment?
Does the application allow for double-byte characters?

Are translatable parts contained in the source files?
Or, are they separate in the resource files?
Target
language
Consistency of Development Environment
Are development tools available?
Method to review operation
Target operating system and cost
Preparation of hardware (rental or
purchase)
Range of work
1. Translation alone
2. Translation, resource embedding, verification
3. Creation of Help files
4. Creation of installer
Translation method and accuracy
Checking method
Glossary of terms
If there are any specific technical terms for the software,
the client is contacted.
Scheduling with client
Rough
costing
On
receipt of a firm order, project teams are established on both sides.
Prompt
and efficient communication is essential. A protocol to keep you informed
about modifications and verify revision is arranged.
It
is advantageous to create Excel files with IDs. But in the case of multilingual
translation, it is difficult to use the same operating systems and applications
as translators.
Special care is needed not to falsely delete %d or \n and not to use wrong IDs
(in the case of Windows), otherwise the program will not run, and this can be difficult to correct.
Are
diacritical marks displayed? No garbled characters? Disconnected strings?
Original language remaining? Is Help correct? Is Help linkage correct?
Translation
must sometimes be reduced. Bitmaps of buttons must sometimes be remade.
After
creating the installer, verify operation under the target language operating
system.
|