Menu
▾
▴
[docbook-checkins] CVS: defguide5/en/refpages/elements/imageobjectco example.1.xml,NONE,1.1 db.imageobjectco.xml,1.3,1.4
|
From: Norman W. <nw...@us...> - 2006-01-29 15:33:19
|
Update of /cvsroot/docbook/defguide5/en/refpages/elements/imageobjectco In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv32148/imageobjectco Modified Files: db.imageobjectco.xml Added Files: example.1.xml Log Message: Fix bug #1358844: allow multiple imageobjects inside an imageobjectco --- NEW FILE --- <article xmlns='http://docbook.org/ns/docbook' xmlns:xlink="http://www.w3.org/1999/xlink"> <title>Example mediaobject</title> <para>The Sun Microsystems offices in Burlington, MA are located on Network Drive, just off Route 3.</para> <mediaobject> <imageobjectco> <areaspec units="calspair"> <area xml:id="myoffice" coords="5500,5627 5940,4984" xlink:href="http://www.sun.com/"/> <areaset xml:id="rt3" xlink:href="http://www.smartraveler.com/scripts/bostraffic.asp?index=5&city=bos&cityname=Boston"> <area coords="1880,9968 2560,8875"/> <area coords="2134,9421 2814,8328"/> <area coords="2388,8875 3068,7781"/> <area coords="2642,8328 3322,7235"/> <area coords="2897,7781 3577,6688"/> <area coords="3151,7235 3831,6141"/> <area coords="3405,6688 4085,5595"/> <area coords="3659,6141 4339,5048"/> <area coords="3913,5595 4593,4502"/> <area coords="4167,5048 4847,3955"/> <area coords="4421,4502 5101,3408"/> <area coords="4676,3955 5356,2862"/> <area coords="4930,3408 5610,2315"/> <area coords="5184,2862 5864,1768"/> <area coords="5438,2315 6118,1222"/> <area coords="5692,1768 6372, 675"/> <area coords="5946,1222 6626, 129"/> </areaset> </areaspec> <imageobject> <imagedata fileref="figures/officemap.png"/> </imageobject> </imageobjectco> </mediaobject> </article> Index: db.imageobjectco.xml =================================================================== RCS file: /cvsroot/docbook/defguide5/en/refpages/elements/imageobjectco/db.imageobjectco.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -U2 -r1.3 -r1.4 --- db.imageobjectco.xml 7 Jul 2005 16:41:00 -0000 1.3 +++ db.imageobjectco.xml 29 Jan 2006 15:32:53 -0000 1.4 @@ -24,35 +24,51 @@ -<para><tag>Callout</tag>s, such as numbered bullets, are an annotation mechanism. In an -online system, these bullets are frequently <quote>hot,</quote> and clicking on -them navigates to the corresponding annotation. +<para>The use of <tag>callout</tag>s, such as numbered bullets, +provide an annotation mechanism. In an online system, these bullets +are frequently <quote>hot</quote> and clicking on them navigates to +the corresponding annotation. </para> -<para>A <tag>ImageObjectCO</tag> is a wrapper around an <tag>AreaSpec</tag> and -an <tag>ImageObject</tag>. An <tag>AreaSpec</tag> identifies the locations -(coordinates) -on the image where the <tag>Callout</tag>s occur. -The <tag>ImageObjectCO</tag> may also contain the list of annotations in -a <tag>CalloutList</tag>, although the <tag>CalloutList</tag> may also + +<para>An <tag>imageobjectco</tag> is a wrapper around an +<tag>areaspec</tag> and a set of alternative <tag>imageobject</tag>s. +More than one <tag>imageobject</tag> may be provided (just as more than +one media object may occur inside <tag>mediaobject</tag>), but they must +share exactly the same callout coordinates and exactly one must be selected +by the processing system. (Use multiple <tag>imageobjectco</tag> elements +inside a <tag>mediaobject</tag> to provide alternatives with different +callout coordinates.)</para> + +<para>An <tag>areaspec</tag> identifies the locations (coordinates) on +the image where the <tag>callout</tag>s occur. The +<tag>imageobjectco</tag> may also contain the list of annotations in a +<tag>calloutlist</tag>, although the <tag>calloutlist</tag> may also occur outside of the wrapper, elsewhere in the document. </para> <refsection><title>Processing expectations</title> + <para><?tdg gentext='format.block'?> It may not be rendered at all, depending on its placement -within the <tag>MediaObject</tag> that contains it and +within the <tag>mediaobject</tag> that contains it and the constraints on the publishing system. For a more detailed description -of the semantics involved, see <tag>MediaObject</tag>. +of the semantics involved, see <tag>mediaobject</tag>. </para> -<para>The mandatory processing expectations of a <tag>ImageObjectCO</tag> are -minimal: a system is expected to render the image, if possible, and the -callout list, if present. -</para> -<para>In online environments, the processing system may be able to instantiate -the linking relationships between the callout marks on the image and -the annotations. For example, an <acronym>HTML</acronym> presentation system might use the -coordinate information to construct a client-side image map. -Some processing systems may even be able to go a step further and generate -the callout marks automatically from the coordinate information. -But this level of sophistication is not mandatory. + +<para>The mandatory processing expectations of a +<tag>imageobjectco</tag> are minimal: a processor is expected to render +the image, if possible, and the <tag>calloutlist</tag>, if present. +If more than one <tag>imageobject</tag> is present, exactly one must +be selected. A processor should select the first object that it can, +although it is free to choose any of the objects according to +implementation-dependent mechanisms.</para> + +<para>In online environments, the processing system may be able to +instantiate the linking relationships between the callout marks on the +image and the annotations. For example, an <acronym>HTML</acronym> +presentation system might use the coordinate information to construct +a client-side image map. Some processing systems may even be able to +go a step further and generate the callout marks automatically from +the coordinate information. But this level of sophistication is not +mandatory. </para> </refsection> @@ -66,5 +82,15 @@ <?tdg-seealso?> -<!-- FIXME: add examples --> +<refsection condition='ref.examples'> +<title>Examples</title> + +<programlisting><xi:include href='example.1.xml' parse='text'/></programlisting> + +<anchor xml:id='ex.os.imageobjectco.1' role='HACK-ex.out.start'/> +<xi:include href='example.1.xml' xpointer='/1/2'/> +<xi:include href='example.1.xml' xpointer='/1/3'/> +<anchor xml:id='ex.oe.imageobjectco.1' role='HACK-ex.out.end'/> + +</refsection> </refentry> |