Issues with standards and tools
From Wikistandards
Some tools according to the following table include or lack in standards. This table is just a first start of an inventory - please feel free to add information by clicking on the edit tag above.
[edit] Identified problems
- Right to left standards (now left to individual implementers, with technical guidelines from Unicode)
- Top to bottom standards (should exist like left to right / right to left)
- Ruby text in Microsoft and ITF -- in other systems
- Some languages no fonts
- Some languages no rendering
- Some languages no encoding (missing characters)
- Aligment differences in TMX with translation tools.
- Standard for documentation - example: manuals in order to avoid problems during the translation process.
- NLP tools in general lack standards, but concept to broad for standards.
- Standard for doing simplified language. Business related language rules.
- Product properties server lacks formal standard to describe them.
- Linguistic analysis tools: standards are very young - not adopted by existing software.
- Terminology tools: full implementation of standards missing. Some have TBX - mostly limited or not perfect. TMF should be used.
- Problems because of user interfaces to complicated.
- xml:tm two companies are implementing it at the moment - many cat tools are not optimized for xml authoring
- CAT-tools should look at W3C ITS - translateable/non translateable tags.
- No appropriate standard to manage a full ontological based system. And of course support in tools.
- Wordcount standard: still not supported by industry. (Wordcount based on XLIFF)
- Webservice definition service needed for example for Wordcount, Terminology extraction etc.
- Spellchecking: no defined standard for performing spellchecking and performing tasks that are connected to spellchecking.
- XLIFF and TMX are not fully implemented in tools.
