Conference iosg::all-in-1_v30

1693.0. "Bug in the Spanish kit" by TARUGO::LIDIA (Spain) Fri Oct 30 1992 16:34

	Hi all,

	I've just found a bug in the translation of ALL-IN-1 v3.0.

	A customer has performed an ALL-IN-1 upgrade to v3.0. Then,
	he tries to change the format parameters to print a WPS document.
	He select the document, press the print key and press GOLD A.
	He receive the message (in Spanish): 

	"...cannot change the format parameters for this document"

	And he obtains the A1TRACE.LOG file with the following lines:

     
![FUNC]   Function: OA$SCP_DISPATCH, Cmd line: .IF FORMAT.STDFORMAT[#PRINT_FORMA
!               T] EQS SM$_Y   THEN GET #PRINT_FLAG_WF = 1\GET OA$STATUS = 1  EL
!               SE GET OA$STATUS = 0
![A1LOG]  Entry: %OA-I-LOGFUN, Funci�n: OA$SCP_DISPATCH .IF FORMAT.STDFORMAT[#PR
!               INT_FORMAT] EQS SM$_Y   THEN GET #PRINT_FLAG_WF = 1\GET OA$STATU
!               S = 1  ELSE GET OA$STATUS = 0
![SCRIPT] Form: WPPARG, Statement: .IF FORMAT.STDFORMAT[#PRINT_FORMAT] EQS SM$_Y
!                  THEN GET #PRINT_FLAG_WF = 1\GET OA$STATUS = 1  ELSE GET OA$ST
!               ATUS = 0
![SYMBOL] Symbol: #PRINT_FORMAT, Value: WPSPLUS
![FLOW]   Form FORMAT opening, Library: DISK$AGUILA_PAG:[ALLIN1.LIB_SPANISH]OAFO
!               RM.FLB;
![IO]     Opening FORMAT, File: OA$DATA_LLV:FORMAT.DAT, Class: DATA, Mode: INPUT
![IO]     Getting record from FORMAT, Key: WPSPLUS, Key-of-ref: /0
![IO]     Getting field STDFORMAT from FORMAT, Value: 1
![SYMBOL] Symbol: FORMAT.STDFORMAT[#PRINT_FORMAT], Value: S
![SYMBOL] Symbol: SM$_Y, Value: Y
![SCRIPT] IF Operation starting
![SCRIPT] .IF condition FORMAT.STDFORMAT[#PRINT_FORMAT] EQS SM$_Y    is FALSE
![SCRIPT] THEN Operation starting


	As you can see, the values in FORMAT.DAT are translated, but the
	SM$_Y symbol not.

	This is the problem if we perform an upgrade. But, if we perform
	a full instalation, we have the following problem:

	FORMAT.DAT values aren't translated and SM$_Y isn't translated.
	Then, no problem with GOLD A. 

	How can we fix this problem? We think the symbol SM$_Y should 
	be translated (you can see in the Application Programming Refe-
	rence Volume 1, 5-37 page. But if we translate this symbol, the
	new installation doesn't work. What we can do?
    	
    	Thanks in advance,
    
    		Lidia	
    	
    	
    	    

    
    Lidia,
    
    Hmmm, what happens during an upgrade installation is:
    
    	- Save old FORMAT.DAT to V2X_FORMAT.DAT
    	- Create new FORMAT.DAT
    	- Write all entries for V3.0 in FORMAT.DAT
    	- Loop through V2X_FORMAT.DAT and update the records in FORMAT.DAT
    		for the values in V2X_FORMAT.DAT
    
    The STDFORMAT field is (probably) the only field which will cause you a
    problem:
    
    V2FORMAT.FLX (used during the upgrade):
    
    ;;STDFORMAT;;
    /VALID=OA$YN/HARD=OA$_FORMAT_STANDARD/LANGUAGE=OA$_LANG_YES_OR_NO
    
    The value for OA$_LANG_YES_OR_NO will probably be 'S,N/Y,N' in Spanish.
    
    FORMAT.FLX in V3.0:
    
    ;;STDFORMAT;;
    /HARD=OA$_FORMAT_STANDARD/LANGUAGE=SM$_LANG_YN_NUM/VALID=OA$YN:SM$_YN
    
    The value for SM$_LANG_YN_NUM is 'Y,N/1,0', which is quite different
    from V2.*.
    
    When modifying the records during the upgrade the value for STDFORMAT
    V2.X (S in your example) is put into STDFORMAT V3.0. As 'S' is not part
    of the internal translation string, it will be stored as an 'S', and not
    as a '1' (or 'Y' in the worst case).
    
    A way to fix this is (in V3.0):
    
    FOR FORMAT WITH .STDFORMAT:U == OA$Y DO -
      GET #KEY = .%KEY \\-
      WRITE CHANGE FORMAT %KEY = #KEY, STDFORMAT = SM$_Y
    
    If the spanish OA$N isn't 'N', then you have to do the same for all
    'Ns':
    
    FOR FORMAT WITH .STDFORMAT:U == OA$N DO -
      GET #KEY = .%KEY \\-
      WRITE CHANGE FORMAT %KEY = #KEY, STDFORMAT = SM$_N
    
    And submit an SPR (if not already done)... 
    
    Ciao,
    
    	Simon                                 
    
    
    
    
    

    Also, SM$_Y should only be translated if the SM subsystem is *ALSO*
    translated!
    
    It's there so that you get to answer English questions in the SM
    subsystem with English answers, even though the rest of the product is
    translated.
    
    Graham

    Please refer to Spanish language Release Notes, 1.7
    	Stefan