1
<page xmlns="http://projectmallard.org/1.0/"
6
<link type="seealso" xref="mal_inline"/>
9
<name>Shaun McCance</name>
10
<email>shaunm@gnome.org</email>
14
<name>Shaun McCance</name>
17
<revision version="0.1" date="2008-02-19" status="incomplete"/>
19
<desc>Use elements and attributes from other namespaces in Mallard
23
<title>External Namespaces</title>
26
<cite date="2008-12-01"><name>Shaun McCance</name></cite>
31
<!-- BEGIN attributes -->
32
<section id="attributes">
34
<title type="link">External Namespace Attributes</title>
36
<title>Attributes</title>
38
<p>All elements in Mallard can have attributes from external namespaces.
39
This can be used to clarify the meaning of an element in a particular
40
context, to provide additional information to processing tools, or to
41
embed richer semantic data in a document.</p>
43
<p>For example, a translation tool might copy
44
<link xref="mal_block_code">code blocks</link> directly into the translated
45
document without presenting them to translators. Some code blocks, however,
46
may contain human-readable comments which should be translated. In order to
47
force translation tools to present these code blocks for translation, authors
48
could use the <code>its:translate</code> attribute from the
49
<link href="http://www.w3.org/TR/its/">Internationalization Tag Set</link>,
50
as in the following:</p>
53
<code xmlns:its="http://www.w3.org/2005/11/its"
54
its:version="1.0" its:translate="yes">
55
// This code block should be translated because it contains this comment.
60
<p>Processing tools should ignore any attributes from external namespaces
61
they do not understand.</p>
63
<!-- END attributes -->
66
<!-- BEGIN elements -->
67
<section id="elements">
69
<title type="link">External Namespace Elements</title>
71
<title>Elements</title>
added
removed
doc/mallard/C/mal_external.page
