added <div>s for text
diff --git a/projectplan.xml b/projectplan.xml
index 457f201..36f64e2 100644
--- a/projectplan.xml
+++ b/projectplan.xml
@@ -1,22 +1,22 @@
<?xml version='1.0'?>
-<plan xmlns="http://www.eclipse.org/project/plan" xmlns:ns1="http://www.w3.org/1999/xhtml"
+<plan xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml"
name="Visual Editor for XML" plan-format="1.0">
<release projectid="mylyn.docx.vex" version="1.0"/>
<introduction>
- <ns1:div>The Visual Editor for XML is a set of plug-ins that provide
+ <html:div>The Visual Editor for XML is a set of plug-ins that provide
WYSIWYM editing ability for XML files, regardless of the XML
involved. Vex uses CSS stylesheets to provide the formatting for the
presentation layer. All that is needed is a stylesheet and an
appropriate XML file to edit. It hides the XML tags from the users,
allows them to have a word processor like experience but store the
- information in the native XML format.</ns1:div>
- <ns1:div/>
- <ns1:div>Vex is based off of a contribution from the original Vex
+ information in the native XML format.</html:div>
+ <html:div/>
+ <html:div>Vex is based off of a contribution from the original Vex
project created by John Krasnay and hosted at sourceforge.net. In the
year 2008 this code was donated to Eclipse and has been an Eclipse
Web Tools Incubator component. In 2011, the project moved under the
- hoods of the Mylyn Docs project.</ns1:div>
- <ns1:div/>
+ hoods of the Mylyn Docs project.</html:div>
+ <html:div/>
</introduction>
<release_deliverables/>
<release_milestones>
@@ -30,62 +30,64 @@
<milestone date="2012-12" milestone="1.1.0"/>
</release_milestones>
<target_environments>
- <ns1:div>
- <ns1:ul>
- <ns1:li>Java 5 or later.</ns1:li>
- <ns1:li>Eclipse 3.5 or a later release of the Eclipse 3
- line.</ns1:li>
- <ns1:li><ns1:i>Eclipse 4 already seems to work, will be fully
- supported in the future.</ns1:i></ns1:li>
- </ns1:ul>
- </ns1:div>
+ <html:div>
+ <html:ul>
+ <html:li>Java 5 or later.</html:li>
+ <html:li>Eclipse 3.5 or a later release of the Eclipse 3
+ line.</html:li>
+ <html:li><html:i>Eclipse 4 already seems to work, will be fully
+ supported in the future.</html:i></html:li>
+ </html:ul>
+ </html:div>
<internationalization>
- <ns1:div>Only English translation files, however all strings are
- externalized for translation in a future release.</ns1:div>
+ <html:div>Only English translation files, however all strings are
+ externalized for translation in a future release.</html:div>
</internationalization>
</target_environments>
<compatibility_with_previous_releases>
- <ns1:div>Versions prior to 1.0.0 M8 used other package names
+ <html:div>Versions prior to 1.0.0 M8 used other package names
(org.eclipse.wtp.vex.*). Older plug-in descriptors and customizations
have to be converted manually to use the new package names
- (org.eclipse.vex.*).</ns1:div>
+ (org.eclipse.vex.*).</html:div>
</compatibility_with_previous_releases>
<themes_and_priorities>
<theme name="Full support of the XML infoset">
<committed>
- <ns1:ul>
- <ns1:li>Comments</ns1:li>
- <ns1:li>Processing Instructions</ns1:li>
- </ns1:ul>
+ <html:ul>
+ <html:li>Comments</html:li>
+ <html:li>Processing Instructions</html:li>
+ </html:ul>
</committed>
</theme>
<theme name="Support for common XML specifications">
<committed>
- <ns1:ul>
- <ns1:li>XML Inclusions</ns1:li>
- </ns1:ul>
+ <html:ul>
+ <html:li>XML Inclusions</html:li>
+ </html:ul>
</committed>
</theme>
<theme name="Support for common XML document types">
<committed>
- Support for
- <ns1:ul>
- <ns1:li>Docbook</ns1:li>
- <ns1:li>DITA</ns1:li>
- <ns1:li>XHTML</ns1:li>
- </ns1:ul>
+ <html:div>Support for</html:div>
+ <html:ul>
+ <html:li>Docbook</html:li>
+ <html:li>DITA</html:li>
+ <html:li>XHTML</html:li>
+ </html:ul>
</committed>
<proposed>
- Support for
- <ns1:ul>
- <ns1:li>PI-Mod</ns1:li>
- </ns1:ul>
+ <html:div>Support for</html:div>
+ <html:ul>
+ <html:li>PI-Mod</html:li>
+ </html:ul>
</proposed>
</theme>
<theme name="API stabilization">
- <committed>The VexWidget should be usable as standalone widget for
- structured text (not necessarily XML). An example will be provided,
- which uses the VexWidget for editing WikiText..</committed>
+ <committed>
+ <html:div>The VexWidget should be usable as standalone widget for
+ structured text (not necessarily XML). An example will be provided,
+ which uses the VexWidget for editing WikiText.</html:div>
+ </committed>
</theme>
<theme name="Building a community"/>
</themes_and_priorities>
