|
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. ----- "Simonse, Arco (CMK)" <ArcoSimonse@xxxxxxxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 06/06/2005 12:23 Please respond to RPG programming on the AS400 / iSeries To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> cc: Subject: RE: multi language interfaces Hello Peter, I'm open for every solution because we start with this from scratch. But personally I think it would be better to keep it flexible "on the fly". Creating a dspf object for every language looks not so flexible to me. Regards, Arco
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.