|
Hi Peter, That's the way I also lean toward. But how to implement such? Do I have to use a seperate lib for every language in which I store message files and datafiles? Or is it better to use datafiles in the same lib wich have the content for all the languages that should be used? Now only three languages will be supported, but you'll never know for the future. TIA, Arco > -----Oorspronkelijk bericht----- > Van: rpg400-l-bounces@xxxxxxxxxxxx > [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Namens > Peter.Colpaert@xxxxxxxxxx > Verzonden: maandag 6 juni 2005 12:34 > Aan: RPG programming on the AS400 / iSeries > Onderwerp: RE: multi language interfaces > > Hi Arco, > > in that case, I'd go for a solution where you have output > fields in the display file instead of constants, and fill > them - either from a data file or from a message file - > depending on the language specified in the user preferences. > > It is in my opinion the most flexible and easiest solution. > If ever you need an additional language, it's not necessary > to re-compile the display files, you can simply point the > application to a different data/message file. > > HTH, > > Peter Colpaert > Application Developer > Massive - Kontich, Belgium > ----- > Yoda of Borg are we. Futile is resistance, assimilated will you be. > ----- DISCLAIMER: This message contains information that may be privileged or confidential and is the property of C.Meijer B.V. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy,disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This footnote also confirms that this email message has been swept by the presence of computer viruses
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.