× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Language selections
  • From: MacWheel99@xxxxxxx
  • Date: Fri, 30 Jun 2000 01:02:38 EDT

I alluded to this in my posting ... you can generate all invoices from a 
single AS/400 in which one invoice is in French & the very next one is in 
Spanish & the very next one is in whatever you like & the whole run is the 
same job same program.

In DDS you can refer to a text line as some message member in some library, 
knowing that this MSGF contains a different English word you want translated 
for each entry, and that the identically named MSGF contains a set of one to 
one translations 

TXT0001 TXT0002 TXT0003 TXT0004 etc, correspond to the words on the invoice
Library ENGLISH has the English versions of the words
Library SPANISH has the Spanish versions of the words

When one level of the program calls for the invoice print program to output 
the next invoice, you use data from the customer master file to say "oh this 
is going to BRAZIL & their language is PORTUGUESE, so do the over-ride to get 
the message members from THAT library.

I find this to be a pain to program modify ... I like my literals right in 
front of me when programming.

Another approach would be to use field names like DISCOUNTX and NETX where 
DISCOUNT and NET is the actual dollars while *TX is the text label ... when 
the customer number changes, you check what language is relevant to that 
customer & if it is different from the prior customer, or this is the first 
of the run, then populate all the *TX fields in which you look up some table 
like an SQL select such that the language matches the latest one for what 
record you read & the fields input are those for the *TX that the program 
needs, so when you feed that to the output specifications, you are not 
messing with TXT#### confusion.

>  From:    DRobitaille@cascades.com (Denis Robitaille)
>  
>  You are assuming that the software will run on different AS/400 setup with 
> different code page. I assumed that all invoices would be generated from a 
> single AS/400.
>  
>  Denis Robitaille

>  >>> leif@leif.org 06/29/00 01:56pm >>>
>  From: Reger, Bill <breger@levitz.com>
>  Subject: RE: Language selections
>  
>  > The technique is to use Message Files with the OVRMSGF command.  
>  > The trick is to externalize all the hard-copy printed text 
>  > and replace them all with message ID's.  You need someone 
>  > to translate the message ID's in the different message files.  
>  > Set up the OVRMSGF based on the language of the
>  > customer and you got it.

Al Macintyre  ©¿©
http://www.cen-elec.com MIS Manager Programmer & Computer Janitor
+---
| 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 thread ...


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

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.