[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1202.0. "Customisation for mail.msg?" by KERNEL::OTHENJ () Fri Aug 07 1992 12:02

Hello,

	ALL-IN-1 v3.0

	Can someone give me a few more details on the new Customisation 
Management element type of A1MSG??

	A customer would like to make a change to the symbol AFCANCELED (as 
cancelled is spelt with only one 'l'). The symbol is held in mail.msg, but 
not in siteem.a1$msg. Therefore, the customer cannot customise mail.msg from 
the CM option - what was the reasoning behind leaving some symbols out of 
customisation within ALL-IN-1?

	The customer tried to comprise by adding the symbol AFCANCELED into 
SITEEM.A1MSG, and after moving the customisation to live, the customer 
could

<get oa$_em_afcanceled

or

<get em_afcanceled

and both produced the new (correct spelling) of 

Auto-forward cancelled.

	If he chooses option CF though, the message

Auto-forward canceled

is displayed. What symbol is the option CF using???

	Any explanation of the above would be much appreciated.

	
		Julie

T.RTitleUserPersonal
Name
DateLines
1202.1Linked and Dynamic loaded message symbols?CESARE::EIJSAll in 1 PieceFri Aug 07 1992 14:1420
    
    Hi Julie,
    
    I can't give you full details of the technical implementations, only
    the following:
    
    - The new 'literal symbols' are held in some kind of hash table. They're
      not actually linked in the OA$MAIN image, as is done with message
      files like OAMESS.MSG, MAIL.MSG
    - Message which are called by code routines still reside in files like 
      OAMESS.MSG and MAIL.MSG. (Let's call them) Scripting messages now
      in the new hash table
    - It was decided that CM would support the new 'Literal symbols' and
      the old MSG files
    
    Only a start...
    
    Ciao,
    
    	Simon
1202.2Easy...IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeFri Aug 07 1992 14:4216
    So you can fix this message, but you have to edit MAIL.MSG without the
    benefit of CM, $mess/compile it twice, once with /TEXT and once with
    /NOTEXT, put the objects in OALLV.OLB and DMPLUS.OLB respectively,
    relink the image.... I think this is still described in the Management
    Guide somewhere.
    
    Are they put off yet?
    
    Graham
    
    PS there are at least five other uses of "canceled" just in MAIL.MSG.
    
    PPS So is this going to be fixed in a PFR Simon?
    
    PPPS Canceled is the "correct" spelling in the US, not that that counts
    for anything (he said ducking :-) )
1202.3Two different types of message fileSCOTTC::MARSHALLPearl-white, but slightly shop-soiledFri Aug 07 1992 15:1916
Just to clarify:

The *.A1$MSG files contain messages used in scripts, named data, etc.  They are
an ALL-IN-1 specific file type.  They are "compiled" with OA$MESCOMP to produce
"section" files, *.A1$SECTION, which do not need to be linked into the ALL-IN-1
image.  CM provides a high-level way to do this.

The *.MSG files are VMS message files containing messages used in code.  They
must be "compiled" with MESSAGE, and the resulting object files linked into the
image.

The *.A1$MSG files were created new in V3.0 to make it easier to customise and
add new messages to ALL-IN-1, and also because the *.MSG files were becoming
overloaded.

Scott
1202.4PFR?CESARE::EIJSAll in 1 PieceFri Aug 07 1992 15:5313
    
    Graham,
    
    > PPS So is this going to be fixed in a PFR Simon?
    
    Futures? In this place? And you, out of all moderators, ask me? ;-)...
    
    CM Should support all elements within ALL-IN-1 (the OA application).
    *.MSG files are part of it so I suppose...
    
    Ciao,
    
    	Simon
1202.5IOSG::MAURICECeci n&#039;est pas une noteFri Aug 07 1992 16:459
>    PPPS Canceled is the "correct" spelling in the US, not that that counts
>    for anything (he said ducking :-) )
    
    Presumably this is a bug in the British kit. Who owns those problems I
    wonder?
    
    ;^)
    
    Stuart
1202.6PAULUS::HOFMANNStefan Hofmann, LC Frankfurt, ISEMon Aug 10 1992 12:535
    The Localization Center (or is it Localisation Centre) should take care
    of the language specific details :-)
    
    	Stefan
    
1202.7InfoSCOTTC::MARSHALLPearl-white, but slightly shop-soiledMon Aug 10 1992 14:018
re .5 and .6

The majority of US-specific spellings are not changed in the British kit.  I
don't think "bugging" it will do much, as it is an intentional decision not to
change the spelling.  Also, the Localisation Centre doesn't produce the British
kit; it's done here in engineering, in parallel with the base (US) kit.

Scott
1202.8FORTY2::ASHGrahame Ash @REOMon Aug 10 1992 19:0616
>>>>
The majority of US-specific spellings are not changed in the British kit.  I
don't think "bugging" it will do much, as it is an intentional decision not to
change the spelling.  Also, the Localisation Centre doesn't produce the British
kit; it's done here in engineering, in parallel with the base (US) kit.

Scott
>>>>

This seems a little bizarre (IMHO and all that stuff!) So what is the British 
kit? Does it contain a spellchecker which would flag the product's own error 
messages as being spelled wrong?! I'd always thought that the changes to make 
the product look 'British' rather than American were fairly trivial . . . are 
customers supposed to do it themselves now?

grahame
1202.9V3.0 MG missing other bits tooAIMTEC::WICKS_ADEC Mail Works for ME sometimesTue Aug 11 1992 00:2618
    And avoiding all the noise in this reply
    
    The way to 'customise' messages in .MSG files appears to be
    yet another piece that got lost in the MAnagement Guide for v3.0
    like Moving ALL-IN-1. So for Julie's benefit it's on page 16-21 of
    the v2.4 Management Guide.
    
    Also look at the index for the management guide in v3 and you'll see
    that it has entries that point to v2.4 sections of the book?
    
    I know i'm naturally skeptical but did these sections just get lost
    or were they removed?
    
    regards,
    
    Andrew.D.Wicks
    
    
1202.10British Explanation...IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeTue Aug 11 1992 11:2121
    Re .9
    
    I'm not sure it's noise, but perhaps a valid discussion of interest to
    British readers.
    
    I notice from your spelling of "skeptical" that you have now switched
    to loading the "American" spelling checker when you get up in the
    morning :-)
    
    re .8
    
    The British version, even when produced by the British Local
    Engineering Group, rather than the Central Engineering Group (who sit
    about 50 yards away from each other :-) ) never had very many changes
    to the spelling. the only things that are changed are replacment of Zip
    Code with Post Code, use of the British Spelling Dictionaries, and
    about two hundred (only a slight exaggeration!) changes of default
    language to British. Corrsesponding changes to Help and CBIs complete
    the alterations.
    
    Graham
1202.11FROIS1::HOFMANNStefan Hofmann, LC Frankfurt, ISEWed Aug 12 1992 19:0318
    re: several.
    
    of course I know that the British variant is produced in Reading,
    because I work in the Localization Center. I always though that it's
    not correct to discuss American or British English issues in the BIV,
    since there should be a British and US-American variant of the BIV
    who take care of language and country specifics. (remember: BIV = Basic
    International Version). 
    I guess it wasn't a good time for a joke :-)
    So, please forget that I replied to this topic.
    
    
    re .10:
    
    Graham, 
    not to forget the famous "�" sign !
    
    	Stefan
1202.12ECCGY4::HAIGHOh God.Tue Feb 16 1993 15:2318
    
    	With very little help from the documentation, I found some files in
    [allin1.sources_<language>] called SITE$%%.A1$MSG. It seems these files
    should be used to contain customisations to message symbols!
    
    	I wanted to change the value for EM$_TELNO, so like a conscientious
    ALL-IN-1 manager, I copied the SITE$EM.A1$MSG to the dev area added a
    line 
    
    	TELNO	<New text>
    
    	compiled it, installed it and guess what -  nothing! I still get
    the original text when I print or read a document. 
    
    	Can someone shed some light?
    
    
    		Steve
1202.13Move to liveIOSG::BILSBOROUGHJust testing. Please ignore!!! Tue Feb 16 1993 15:5310
    
    Did you move it to live
    
    Try MLA on the element 
    then AM PME enter the element name in hte index arg form and enter ML
    to move it to live
    
    Then do SM CSZ CMF to compile it.
    
    Mike
1202.14ECCGY4::HAIGHOh God.Tue Feb 16 1993 16:534
    >     Did you move it to live
    
    
    		Yes.
1202.15Remember to exit ALL-IN-1AIMTEC::WICKS_AWALES 10 England 9Tue Feb 16 1993 17:289
    Steve,
    
    Make sure you log out of ALL-IN-1 and back in. These 'message files'
    are VMS global sections so you won't see an updated one until
    you reactivate ALL-IN-1.
    
    regards,
    
    Andrew.D.Wicks
1202.16ECCGY4::HAIGHOh God.Fri Feb 19 1993 13:355
    
    	I had restarted ALL-IN-1. In the end I changed the boilerplate.
    
    
    		Steve
1202.17CMF'ing the .A1$MSG file helps tooSIOG::T_REDMONDThoughts of an Idle MindSun Feb 21 1993 15:167
    I trust the CMF option (customize message file) was used from the
    "Manage a Customized System" menu to compile the contents of the
    altered .A1$MSG file into a new global section file?  I do this all the
    time and have never seen a problem. But then again, I am kind of
    strange!
    
    ;-)  Tony