Home » RADICORE » RADICORE Suggestions » Internationalisation suggestion
|
|
|
|
|
|
|
|
 Re: Internationalisation suggestion [message #1390 is a reply to message #1385] |
Tue, 01 July 2008 04:55   |
bonzo_bcn
Messages: 152
Registered: June 2008
|
Senior Member |
|
|
| AJM wrote on Mon, 30 June 2008 16:37 |
I do not consider you suggestion to be an improvement over the existing method, it is just different. I have worked with other systems in the past that used non-database files for all foreign language text, so I am not alone in thinking that is has merits.
Unless you can present a compelling reason why I should switch to a different method I see no reason to change anything.
|
I've been working also with a big ERP (kind of SAP) and they had it done this way. There was a cache system where all the labels where stored the first time they where retrieved.
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.
As for other labels fr buttons etc create a table with "label_id, language_id, text" then a global function can be used wherever you want to retrieve a label for a given language.
You also avoid the hardcoding of titles in the screen.inc files.
|
|
|
|
|
|
|
|
| Re: Internationalisation suggestion [message #1396 is a reply to message #1394] |
Tue, 01 July 2008 05:36 |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Internationalisation suggestion [message #1407 is a reply to message #1406] |
Tue, 01 July 2008 07:45 |
bonzo_bcn
Messages: 152
Registered: June 2008
|
Senior Member |
|
|
| AJM wrote on Tue, 01 July 2008 07:32 |
Your method just affects the changing of column labels but has nothing to do with screen titles, menu buttons, navigation buttons and error messages. My method covers everything.
Besides, changing column labels is not something you do everyday. They are normally set once and remain for eternity.
|
No, you could use the same idea for everything. In fact, the software I used had every single string of text of the application in the database, so nothing was hard coded anywhere.
If you wnated to change any string you got into the dictionary and changed it.
You could have a table for error messages, a table for titles, for menu buttons etc. or everything in a single table.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Wed Jun 18 13:48:14 EDT 2025
Total time taken to generate the page: 0.01715 seconds
|
Radicore Forum
Search
Help
Members
Register
Login
Home
)
