You need to log in before you can comment on or make changes to this bug.
I noticed that the XSLT supplies text to the help docs, specifically the maturity level. For example the XML doc has "ALPHA" and the XSLT outputs "ALPHA -- (i.e., in development, incomplete functionality, little to no documentation)". This language specific addition should be moved to xml document and therefore must come from the doc builder. The XSLT should be language independant.
Assigning to Chris for investigation.
Good point :) I totally missed that. When will the multi language feature be present in the help viewer?
ok I have had time to think about this and talk to bill. Just to be clear the main reason why I added this english text in the xslt is because I did not want to add this string to every xml document manually. Since this is a problem to have monolingual xslt's (which I agree with) and that it does not make sense to have multiple xslt's per language. the responsibility to be multilingual descriptions lands in the doc builder. This leads to additional development for the doc builder, because it currently is handling one language, English. Questions for Darren and Paul: * Is this the direction we want to go? * When should this be a priority? If the answers are "Yes" and "Soon" the following things will have to happen: * modify XML Schema's: to hold additional default strings (this is easy to do). * Doc builder: define how doc builder will handle multilingual text. * Should it be configurable per default string for the user? * Should it be hard coded per language? * Should it be defined by language dbf or another xml doc? * Help View: how will the user (in interface) and/or administrator (by config options) select a language(s).
My first guess is that this is not a priority at all and won't happen until after 2.0 is finalized. Also, I am not sure that the values for the maturity levels should be translated as they may lose meaning in the translation. Often with computer terms, the English word is used in other languages. I would say that the maturity levels should stay as they are, regardless of language being produced, but there could be a description of the terms that should be translated. My $0.02 :>
The part to be translated is the maturity level description, not the level itself.
This will apply to other default descriptions of features found in the xslt. So form paul's reply he believes that multilingual documents will not be in place until post 2.0. Would everyone agree with this?
I would say yes. We could not implement everything in this release because is will never go out.
I also agree that it is post-2.0.
Changed target to FUTURE.
