We can offer 2 version of the multi-language support realization:
1. We have to create the new fields Name, Description, Bullet description in the existing tables of the database for every language. This version take less time to work, but for new language we will have to develop program again. The defect of this version is problem with Bullet description stings priority. There are some restrictions:
The count of Bullet description strings must be equal for all languages;
If some string of Bullet description will be moved, the same strings in other languages will be moved too.
2. Instead of creation new fields we can create new table to store product Name and Description and language identifier for these fields. Besides we have to add new field in Bullet description table to store language identifier for this string of Bullet description. We have to create new table to store language list.
We have to develop user interface for both version.
We have to set basic (from which language text will be translated) and current language in program settings. Program will request these fields in compliance with the current language.
For more comfortable translation we have to develop new window, which allow you
to edit current language text;
to view basic language text.
The window consists of 2 parts. The left window part contains the fields Name, Description, Bullet description in basic language. The right window part contains the same fields in current language.
The text in basic language is "read only".
We can call this window from main program window for current product and from window "Details".
Besides we have to choose the generation .PDF option. It needs to put empty text for empty fields in the current language or text in basic language.
This is a final estimation for first version (for 1 new language).
| Work | Hour |
| Database modification: 3 new fields in different tables (Name_rus, Description_rus, BulletText_rus) | 1h |
| Rewriting the all queries to database in program | 8h |
| Automatic old database refreshing to work with old database version | 2h |
| "Settings" window modification: basic and current language setting | 2h |
| New window for more comfortable translation | 8h |
| Catalogue generation option for empty fields in current language | 3h |
| Letters, debugging, testing total | 6h |
| Total | 30h |
For second version we have to create new window to edit language list.
This is a final estimation for second version.
| Work | Hour |
| Database modification: new table for language list, new table to store Name, Description and those language identifier | 3h |
| Rewriting the all queries to database in program | 10h |
| Automatic old database refreshing to work with old database version | 2h |
| "Settings" window modification: basic and current language setting | 2h |
| New window for more comfortable translation | 8h |
| New window to edit language list | 6h |
| Catalogue generation option for empty fields in current language | 3h |
| Letters, debugging, testing total | 6h |
| Total | 30h |
We can realize any of proposed multi-price versions (see letter by 27.09.2007).
We can add to language reference book new field to store currency symbol for second multi-language version. Now the currency symbol is stored in program settings. We have to additional 2h for this.
This is an estimation of targets setting.
| Work | Hour |
| Multi-price target setting | 3h |
| Multi-language target setting | 3h |
| Total | 5h |