AnsweredAssumed Answered


Question asked by mark on Nov 5, 2009
Latest reply on Nov 5, 2009 by another_martink
Hi,  I'm tired of Clarity's multi-language support, and I have a better idea.  First, the problems:1. Clarity has all supported languages installed all the time.  I do not want Japanese, Korean, French, German etc in my system, for the following reasons: - the database is larger than it needs to be.
- the upgrade takes longer than it needs to.  I'm typing this while the 12 upgrade oh so slowly updates Dutch.
- All the languages loaded into clarity take up memory all the time.  Again for languages I will never, ever, be interested in. - for those of you using websphere / weblogic, your .ear file is filled with help,resource, and installer files in languages you don't want.       These problems will only ever get worse as CA adds languages.    2. I want to change the translation myself.  This is because the Swedish translation is, quite frankly, shaky, downright comical at its worst.  Plus our various customers have different terminology, which the would of course like to see in Clarity. Problem is that the files containing the translations are scattered over the system, contain massive duplication, and are over-written every time we upgrade.  3. Countries that do not have a translation have to wait for CA to do one.  So, to my idea: languages should be content packs.   The benefit :- you only have the languages you want or need.  - 3rd parties can maintain their own translations, meaning that the countries for which translations have not been done yet can maintain their own.  - Customers can maintain their own containing their own terminology.  Not that complicated to implement, surely?    /mark