Export to GitHub

akomantoso - issue #11

How do we deal with "descriptiveness" in non English contexts?


Posted on Oct 30, 2007 by Grumpy Cat

AKOMA NTOSO, I am quoting, aims <<to be “self-explanatory”, that is to be able to provide all information for their use and meaning through a simple examination>>

How do we deal with "descriptiveness" in non English contexts?

Needless to say that issue about maintenance and cost for possible adaption of tools should be carefully considered.

Thanks

Flavio

Comment #1

Posted on Nov 17, 2007 by Happy Giraffe

This issue was already discussed and resolved in 2006 (on a couch in Cape Town, with Paola playing piano to cover our voices): we will not support multilinguism at the XML level, because this would create too many problems for XSLT.

Rather, we decided to have multilinguism at the content level, relying on UTF-8 for all content, and at the documentation level (by having the documentation translated in all appropriate languages) and at the presentation level (by having stylesheets able to present foreign text with the local layouts).

Comment #2

Posted on Nov 17, 2007 by Grumpy Cat

Fabio, this time you do remember well at least the context :-)

One, option that we did discuss, honestly I cannot remember where and who was playing what, was to use "name" to assign to an XML element a "translated" term/word e.g. in French etc.

If I am not wrong, this would not impact on the XSLT etc. and would provide a certain degree of "descriptiveness" in French or Portuguese.

Would it work?

Flavio

Flavio

Status: WontFix

Labels:
Type-Enhancement Priority-Medium