clean:
- @rm -f ${XML_BASENAMES:%=%.html}
- @rm -f ${XML_BASENAMES:%=%.pdf}
- @rm -f ./*.log
- @rm -f ./*.out
- @rm -f ./*~
+ rm -f ${XML_BASENAMES:%=%.html}
+ rm -f ${XML_BASENAMES:%=%.pdf} $(FIGS:%.fig=%.pdf) $(ORTE_DOC_SOURCES)
+ rm -f ./*.log
+ rm -f ./*.out
+ rm -f ./*~
%.pdf: %.fig
fig2dev -L pdf $^ $@
<?xml version="1.0" encoding="UTF-8"?>
-<section id="orte-api">
+<chapter id="orte-api">
<title>ORTE API</title>
<section><!--sect1-->
&orte_defines_api;
</section><!--/sect3-->
-</section>
+</chapter>
<?xml version="1.0" encoding="UTF-8"?>
-<section id="orte-examples">
+<chapter id="orte-examples">
<title>ORTE Examples</title>
<para>
</para>
</section>
-</section>
+</chapter>
<?xml version="1.0" encoding="UTF-8"?>
-<section id="orte-internals">
- <title>ORTE Implementation Issues</title>
+<chapter id="orte-internals">
+ <title>ORTE Internals</title>
<para>
ORTE is network middleware for distributed, real-time application development
</mediaobject>
</figure>
-</section>
+</chapter>
<section id="orte-intro">
<title>Introduction</title>
+ <para>The Open Real-Time Ethernet (ORTE) is open source implementation of
+ RTPS communication protocol. RTPS is new application layer protocol
+ targeted to real-time communication area, which is build on the top of
+ standard UDP stack. Since there are many TCP/IP stack implementations
+ under many operating systems and RTPS protocol does not have any other
+ special HW/SW requirements, it should be easily ported to many HW/SW
+ target platforms. Because it uses only UDP protocol, it retains control of
+ timing and reliability.</para>
+
+
<para id="ORTE" xreflabel="ORTE">
- The Open Real-Time Ethernet (ORTE) is
- open source implementation of RTPS communication protocol. This protocol
- is being to submit to IETF as an informational RFC and has been adopted
- by the IDA group.
+ RTPS protocol is being to submit to IETF as an informational RFC
+ and has been adopted by the IDA group.
</para>
-</section>
\ No newline at end of file
+</section>
<?xml version="1.0" encoding="UTF-8"?>
-<section id="orte-tests">
+<chapter id="orte-tests">
<title>ORTE Tests</title>
<para>
protocol. Results of these test indicate that ORTE is fully
interoperable with implementation provided by another vendor.
</para>
-</section>
-
+</chapter>
<?xml version="1.0" encoding="UTF-8"?>
-<section id="orte-usage">
+<chapter id="orte-usage">
<title>ORTE Usage Information</title>
<section id="orte-installation">
&orte_ortespy;
</section>
-</section>
+</chapter>
-<!ENTITY orte SYSTEM "ortedoc.xml">
<!--<!ENTITY % ortepath "">-->
<!ENTITY orte_summary SYSTEM "orte/orte_summary.xml">
<!ENTITY orte_attributes_img "%ortepath;/img/orte_attributes">
<!ENTITY orte_internal_architecture_img "%ortepath;/img/orte_internal_architecture">
<!ENTITY orte_rtps_communication_img "%ortepath;/img/orte_rtps_communication">
-
-
+++ /dev/null
-<?xml version='1.0'?>
-<chapter>
- <title>Open Real-Time Ethernet</title>
-
- <para>The Open Real-Time Ethernet (ORTE) is open source implementation of
- RTPS communication protocol. RTPS is new application layer protocol
- targeted to real-time communication area, which is build on the top of
- standard UDP stack. Since there are many TCP/IP stack implementations
- under many operating systems and RTPS protocol does not have any other
- special HW/SW requirements, it should be easily ported to many HW/SW
- target platforms. Because it uses only UDP protocol, it retains control of
- timing and reliability.</para>
-
- <section>
- <title>ORTE Summary</title>
-
- &orte_summary;
- </section>
-
- <section id="orte-description">
- <title>ORTE Description</title>
-
- &orte_intro;
- &orte_ps_model;
- &orte_rtps_model;
- </section>
-
- &orte_internals;
- &orte_examples;
- &orte_tests;
- &orte_usage;
- &orte_api;
-
-</chapter>
-->
<bookinfo>
- <title>ORTE - Open Real-Time Ethernet</title>
+ <title>ORTE – Open Real-Time Ethernet</title>
<!-- <authorgroup>
<author>
<firstname>Petr</firstname>
</legalnotice>-->
</bookinfo>
-&orte;
+<chapter id="orte-description">
+ <title>ORTE Description</title>
+
+ &orte_intro;
+ &orte_ps_model;
+ &orte_rtps_model;
+</chapter>
+
+ &orte_internals;
+ &orte_examples;
+ &orte_tests;
+ &orte_usage;
+ &orte_api;
+
<!-- Add other entries here -->
</book>