We compiled multiple printer files, one for each language within the
"language" library using the appropriate message file.
At runtime we override the printer file before opening it.
Mit freundlichen Grüßen / Best regards
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Jon
Gesendet: Wednesday, 03.9 2014 01:34
An: Midrange-L Midrange-l
Betreff: Question for Printer Gurus
I'm beginning to believe that the folks who did DDS for printer files never
talked to the folks who did display files ...
Latest barrier in my conversion effort is lack of support for the MSGID
keyword on printer files. MSGCON is supported but that is of no use to me
since I need to be able to use the LIBL to control the message file that is
used and MSGCON values are resolved at compile time as far as I can tell.
I know a number of you out there write apps that support multiple languages
- how the heck do you handle that for printer files?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l