|
>At 14:00 08/26/98 -0400, Denis Robitaille wrote: >>Here is my problem: We support about 50 sites in north america, most of >>them in the province of Quebec. When we were only in Quebec, it was >>natural to use the french language for the TEXT and COLHDG. Now we need >>to support both french and english because a good portion of our personel >>speaks only one of the two. Is their a way to have alternate values for >>the TEXT and COLHDG keyword? > Shooting strictly from the hip... For display files, how 'bout 2 sets of DDS, creating 2 DDS libraries. The library list for the English-speaking users would include library 'ENGLISH' and for French-speaking users, would include library 'FRENCH.' This would require that all screens have enough space to handle both the English and French text. Data fields should not be a problem. An alternative would be to make all descriptive text on the screen output fields from a database file (containing all of the descriptive text). In this case, the database file would be overridden to use the appropriate language file. For data files, how 'bout 2 sets of logical files listing all of the fields of the physical but with different TEXT and COLHDG? This is awkward, because you have to maintain all of the logicals every time you change a field... --Paul E Musselman PaulMmn@ix.netcom.com +--- | 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 +---
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.