- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 29 Mar 2006 14:32:19 +0000
- To: public-i18n-its@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3058 Summary: ITS inheritance mechanism versus other inheritance mechanisms (e.g. DITA): Need for clear distinction Product: ITS Version: WorkingDraft Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: ITS tagset AssignedTo: fsasaki@w3.org ReportedBy: fsasaki@w3.org QAContact: public-i18n-its@w3.org Part of DITA sub TC, discussion of proposal for the xml:lang attribute: [[ -- We're talking about the root topic element. -- If xml:lang is on document element, then the highest level topic element inherits xml:lang. Likewise, <topicref> should inherit from <map> (if no parent overrides xml:lang) or from nearest parent that overrides the xml:lang setting of the root element. -- In case of contradiction between xml:lang setting on <topicref> and xml:lang on <topic>, the <topicref> setting does not apply to the <topic>. In other words, the map does not override any xml:lang on the <topic>. -- Discussion whether xml:lang on map should apply to the topics... -- Discussion of translation workflow... -- Need map file for each target language. -- Proposal must clarify the following: - xml:lang on <map> is applied to the map. - xml:lang on <map> does not affect topics. - if different xml:lang values exist on map and topic, topic setting overrides. - add use cases]] The usefulness of our global rules might be quite limited for DITA, due to DITA's specific inheritance mechanism (see discussion above). We need to make clear for DITA and other markup vocabularies with specific inheritance mechanisms, how ITS fits into the picture. IMO we don't need to adapt to them. However, a detailed example of the relation between inheritance in DITA versus inheritance in ITS would be good. I'd propose Christian to deliver one :)
Received on Wednesday, 29 March 2006 14:32:23 UTC