Re: Internationalisation suggestion [message #1396 is a reply to message #1394] |
Tue, 01 July 2008 05:36 ![Go to previous message Go to previous message](/theme/default/images/up.png) ![Go to next message Go to previous message](/theme/default/images/down.png) |
bonzo_bcn
Messages: 152 Registered: June 2008
|
Senior Member |
|
|
AJM wrote on Tue, 01 July 2008 05:29 |
Quote: | In this scenario: you have you application finished, full of transactions etc, now you client asks you to change the title of a column, as it is right now you should have to deal with a lot of files and I'm sure you will forget some. With my suggestion you just go to the dictionary, change the label and that's it.
|
If you have a separate entry in your database for each language then changing the label text for a column will still require a separate update for each language.
In my design each subsystem has a single text file for each language containing the text for everything - task titles, column labels, menu buttons, navigation buttons and error messages - so to change the label for a column still requires one update per language. There is no saving with your method.
|
I found myself wanting to change a label in a list1 transaction and I had to oppen the screen.inc file in order to change it, what if I had hundreds of screen.inc files? Should I go one by one changing the label?
In my option I should go to the column dictionary and update the label for each language, but only one update per language.
With my suggestion internationalization is straigh out of the box.
|
|
|