| Hi Graziella, hi Graham !
Since the days of V2.0 we had the discussion what is supported, what is
possible in respect to secondary languages.
The list of "supported" languages in a given country are those languages that
are handled by their C-component. However, this is typically just a short list
of languages, that is supposed to cover 95% of all customer situations.
Whatever isn't covered by this C-component needs to be handled as project, and
the the support (if desired by the customer) is to be done like for other
individual customer projects, with the chance to involve other groups, like a
country LEG, the country Customer Support Centre or our Localization Centre.
This has been the intention of the whole process from the very beginning, but
some groups in Digital had difficulties accepting this model. But I think it's
important that we don't give away business that we could easily generate.
Now back to this case:
We just verified that the Italien C-component does support the US language
component. However, you need to verify that this C-component was ordered in the
first place (it should have been for legal reasons but...). You can do this
by checking the files in OA$LIB_SHARE. In particular WPLDATES*.*.
The naming convention for this file is
WPLDATES_(2-character countrycode)_(supported language).MSG
So in theory you should have a WPLDATES_IT_ITALIAN.MSG and a
WPLDATES_IT_ENGLISH.MSG (actually also a German one). If this is the case then
you just order Italian as an additional language, choose Additional Language
installation and ... presto.
If you have a US C-component (indicated by _US_ in the filename), send me a
mail or give me a call. We are currently preparing a document that covers
exactly this. It's a side effect from building the C-components for the V3
variants, but should be applicable to V2.4 as well (with some adjustments of
course).
best regards
Richard
|