| I'm confused:
<<< In Australia we use the US language but US_GB dialect
In which case, you don't use the US language, you use British, the
US_GB dialect is just a cheap trick we perpetrated in V3.0 to avoid
building a separate British kit.
If they have installed GB as you say, then they ought to have got the
British dictionaries.
Whatever has happened, probably the simplest plan would be to install
the correct language as a second language, although you might need a
second language licence temporarily, and then remove the wrong one.
After that, you'd need to make th second language into the primary
language.
Chris (IOSG::HALLC) documented how to do this in here somewhere
recently.
Graham
|
| Hi Graham,
>In which case, you don't use the US language, you use British, the
>US_GB dialect is just a cheap trick we perpetrated in V3.0 to avoid
>building a separate British kit.
In Oz we are a bit different in that we install the US language and
market component and the US_GB dialect. That's how all our customers
go about installing the Aussie flavoured version of IOS.
Would an install update do the trick ? In that we can run the
VMSINSTAL procedure and choose to update the installation and choose
the correct dialect ? This would overwrite the incorrect files etc.
and give us the Aussie flavoured version of IOS.
Regards,
Sunil
|