Chris,

Please run, don't walk, to the AS/400 International Application
Development manual.  For your current development activity see the
chapter "International User Interface Design", which discusses several
ways of providing multi-lingual support and discusses some of the trade
offs involved with late vs early binding of messages.

Though you may be in the initial steps of Internationalization, there are
many AS/400 users who have been doing this type of work for years (and
years).

Bruce Vining

>
>I am constructing a system which needs the screens to be presented to each
>user in the langauage of their choice(eg English, German, French, Italian
>and Greek).
>
>I am initially exploring this using message files via the ERRMSGID and
>MSGCON keywords in the DDS. But it seems one has to designate the exact
>message file at compilation and so compile the DDS once for each language
>used which is a pain and means one has to retain multiple libraries of
>screens.
>
>Perhaps the COBOL programs could populate the texts on screen using a
>different msg file via OVRDBF at run time but what about the time overhead
>and the normal DDS ERRMSG processing would be lost.
>
>Anyone got any experience in this area? Any ideas or tips ideas gratefully
>appreciated.
>
>Kind Regards,
>
>Chris
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].