- oXygen-user - www.oxygenxml.com

olink verification
by Bernhard Kleine 26 Jul '17

26 Jul '17

The olinking does not work: I have a document and glossar. The links to the glossar are via olink. At some time this has been working, but I do not know what I have changed so that it does work any further. Linking to the Glossartest.xml document or to the xml:id="Glossartest" did not work either. What is wrong? the respective error messages: > [xslt] : Warning! Failure reading > file:/K:/BuchprojektSpringer/xlm/olinkdb.xml Cause: > java.io.FileNotFoundException: K:\BuchprojektSpringer\xlm\olinkdb.xml > (Das System kann die angegebene Datei nicht finden) > [xslt] Olink error: could not open target database 'olinkdb.xml'. > [xslt] Error: unresolved olink: targetdoc/targetptr = > 'Glossartest/glo.Bsx'. I have seen a faintly similar thread about olinking, but that did not help me. BTW Glossartest.xml and newbooktest.xml validate just fine. Regards Bernhard spitzhalde9 D-79853 lenzkirch bernhard.kleine(a)gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

2 3

Fatal error when using refactoring action
by Lionel MOIZEAU 12 Jul '17

12 Jul '17

Hi, When I use a refactoring action such as Insert element, I get the following error ! Description java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace Severity Fatal System ID C:\Program Files\Oxygen XML Editor 19\refactoring\insert-element.xq<file:///C:\Program%20Files\Oxygen%20XML%20Editor%2019\refactoring\insert-element.xq> With the following trace. java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace at net.sf.saxon.query.StaticQueryContext.declareNamespace(StaticQueryContext.java:750) at net.sf.saxon.s9api.XQueryCompiler.declareNamespace(XQueryCompiler.java:365) at ro.sync.exml.xmlrefactory.c.c.d.p(Unknown Source) at ro.sync.exml.xmlrefactory.c.c.d.g(Unknown Source) at ro.sync.exml.xmlrefactory.c.d.k(Unknown Source) at ro.sync.exml.xmlrefactory.c.c.c(Unknown Source) at ro.sync.exml.xmlrefactory.c.c.b(Unknown Source) at ro.sync.exml.xmlrefactory.ui.i.j(Unknown Source) at ro.sync.exml.xmlrefactory.ui.i.k(Unknown Source) at ro.sync.exml.xmlrefactory.ui.i.i(Unknown Source) at ro.sync.exml.xmlrefactory.ui.i$_b.rhe(Unknown Source) at ro.sync.ui.application.nb.run(Unknown Source) I tried to add a <test> element under the <foo> element in a file like this: <?xml version="1.0" encoding="UTF-8"?> <root> <foo/> </root> Can you help me? Best regards, Lionel MOIZEAU Head of Technical Information Department L-Acoustics Tel : +33 1 69 63 23 99 www.l-acoustics.com<http://www.l-acoustics.com/>

3 4

[Ann] New maintenance build available for oXygen 19.0 (2017062918)
by Adrian Buza 05 Jul '17

05 Jul '17

Dear oXygen users, We announce the release of a new maintenance build (2017062918) for oXygen 19.0 (XML Editor, XML Developer, XML Author, XML WebHelp). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2017062918 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian -- Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

Current ditamap editor variable
by Lionel MOIZEAU 05 Jul '17

05 Jul '17

Hi ! Is there a way to get the current ditamap as an editor variable ? By current map I mean the one open in the DITA Maps manager or selected in the Root map dropdown menu [cid:image001.png@01D2F598.961ECA00] It would be very helpful ! Best regards, Lionel MOIZEAU Head of Technical Information Department L-Acoustics Tel : +33 1 69 63 23 99 www.l-acoustics.com<http://www.l-acoustics.com/>

2 2

[oXygen XML Editor Blog] - DITA Linking Strategies
by oXygen XML Editor Blog 01 Jul '17

01 Jul '17

oXygen XML Editor Blog /////////////////////////////////////////// DITA Linking Strategies Posted: 30 Jun 2017 06:11 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/NkzlLkUcD9Q/dita-lin… This small tutorial is based on the "DITA Linking Strategies" presentations I made for the DITA Europe 2016 and DITA North America 2017 conferences. It's a general overview about DITA linking possibilities and best practices. Also, it's meant as a continuation of the DITA Reuse Strategies blog post. According to Wikipedia: "A link, is a reference to data that the reader can directly follow either by clicking, tapping, or hovering." Basically, we should regard linking as yet another form of content reuse, except that instead of presenting the content in place, it re-directs the end user to some other resource. I'll start with describing linking at DITA Map level. Map-Level Linking A DITA Map uses topic references to assemble the content of a publication. <topicref href="installation.dita"> <topicref href="server_installation.dita"/> <topicref href="client_side_installation.dita"/> </topicref> Depending on the output format, the topic reference may be a link in the table of contents for the XHTML-based outputs or it may be interpreted as a content reference for the PDF-based output that generates a single monolith document. So the role of the topicref is dual, it may sometimes be regarded as a link to a topic and sometimes as a content reference. Chunking DITA topic modules should be kept as small as possible, but sometimes the end user may need to read more than one topic to achieve a single task. So, when publishing to HTML-based outputs, you will end up asking yourself this question:Should I prefer larger HTML files or more links in the TOC? And you should always consider these two ideas: Links are disruptive. Ideally, users would not need to jump around in content to read the entire story they are searching for. Small topics that are usually read consecutively by the end user can probably get merged together. For example, if the installation of your product requires installing both a server-side and a client-side component, by using DITA chunking you can choose to have separate DITA topic modules for each of the installation procedures but merge the topics together in the web-based outputs:<map> <title>User Guide</title> <topicref href="installation.dita" chunk="to-content"> <topicref href="server_installation.dita" toc="no"/> <topicref href="client_side_installation.dita" toc="no"/> </topicref> </map> You can read more about chunking in the DITA 1.3 specification. The DITA Style Guide also has a good overview about why it is preferable to write small topics and then merge them together using the chunking mechanism. Topic-Level Linking Links that appear inside topics can be divided into various categories and I'll discuss each of these categories separately. In-Content Links In-content links are links added manually in the topic content:<li>See: <xref href="http://www.../" format="html" scope="external"/></li> You should keep in mind that this kind of link is disruptive to the reading experience because when end users encounter them, they need to decide weather to read further on or to follow the link. On the other hand, this may sometimes be a good thing. For example, one of the installation steps may require the end user to download a certain library from an external website before continuing. You can read more about links in general in the DITA 1.3 specification. The DITA Style Guide, written by Tony Self, also discourages the use of in-content links. Related Links Related links are placed at the end of the DITA topic and they allow the end user to explore additional resources after the current topic has been read.<related-links> <link href="http://tomcat.apache.org/" format="html" scope="external"/> </related-links> To minimize disruption when reading the content in general, the preferred place where to place links is at the end of the generated HTML page. You can read more about related links in the DITA 1.3 specification. Defining Related Links using Relationship Tables Related links do not need to be manually added at the end of each topic. You can define relationship tables in the DITA Map:<reltable> <relrow> <relcell> <topicref href="client_side_installation.dita"/> </relcell> <relcell> <topicref href="server_installation.dita"/> </relcell> </relrow> …….. </reltable> These tables can define associations between two or more topics, associations that automatically contribute to the related links creation in the generated HTML output. Here are some benefits of using relationship tables: A topic should have as few links as possible defined directly within. This makes it easier to reuse the topic in various contexts and keeps it as separate as possible for other parts of the DITA project, decreasing the possibility of broken links. By default, links defined in relationship tables are bi-directional, allowing users to land on any of the topics when searching for solutions and find their way to the related ones. Using a relationship table separates the task of writing topics from the task of finding relationships between topics. You can read more about relationship tables in the DITA 1.3 specification. The DITA Style Guide also recommends using relationship tables. Indirect Links (Key References) All the link samples we've look at so far have been direct links, links that point to the target using the @href attribute. Indirect links require two steps: Define a key in the DITA Map for the target.<keydef keys="client_installation" href="client_side_installation.dita"/> Use the defined key to reference the target resources.<xref keyref="client_installation"/> Here are some of the benefits of indirect linking: Offers the ability to reuse link target text and meta data. If you want to have custom text for a certain link, you can define it directly in the DITA Map:<keydef keys="dita_ot_website" href="http://www.dita-ot.org/" format="html" scope="external"> <topicmeta> <linktext>DITA Open Toolkit Web Site</linktext> </topicmeta> </keydef>and then add key references in all other places:<xref keyref="dita_ot_website"/> Easier conditional linking (including links to topics that sometimes may be missing). If you want your topic to link either to one target or to another depending on the filtering/profiling conditions, instead of adding profiling directly on the link, you can add the profiling conditions directly in the DITA Map: <topicref keys="slicing" href="slicing_vegetables_for_experts.dita" audience="expert"/> <topicref keys="slicing" href="slicing_vegetables_for_novices.dita" audience="novice"/> <keydef keys="slicing" audience="noLink"><topicmeta><keywords> <keyword>Slicing</keyword></keywords></topicmeta> </keydef>and then link to the key from each topic: <xref keyref="slicing"/> Easier link management. A good overview about all the outbound links in your project helps you maintain and control lists of allowed external web sites. With indirect references, you can define all references to external resources in a separate DITA Map. An example of a DITA project using indirect links to achieve separation of links by purpose can be found here: https://github.com/oxygenxml/dita-project-best-practices. Makes it easier to move/rename topics. When you move or rename a topic referenced via indirect links, only the link defined in the DITA Map will break, making it easier to fix broken links. There is an overview about indirect addressing on the DITA XML Org website. The DITA 1.3 specification also has a chapter about indirect links. Auto-Generated Links Until now, I've talked about manually added links, either in the topic or in relationship tables. Using the DITA @collection-type attribute, you can define relationships between parent and child topic references in the DITA Map, relationships that result in automatic links added between them: <topicref href="installation.dita" collection-type="sequence"> <topicref href="server_installation.dita"/> <topicref href="client_side_installation.dita"/> </topicref> There are 3 useful types of @collection-type values: Unordered - Links are generated from parent to children, and from children to parent. Family - Links are generated from parent to children, from children to parent, and from sibling to sibling. Sequence - Links are generated from parent to children, from children to parent, and from child to previous sibling (if applicable) and next sibling (if applicable). You can read more about auto-generated links in the DITA Style Guide. Conditional Links in Distinct Publications You may publish documentation for multiple products from the same DITA content. Also, you may want to have links point to various targets depending on the product for which you want to publish the documentation. Or, you may want to suppress links completely in certain publications. When using direct linking, you will need to profile each link depending on the publication:Find our more about slicing vegetables: <xref href="slicing_vegetables_for_experts.dita" audience="expert"/> <xref href="slicing_vegetables_for_novices.dita" audience="novice"/>.With indirect links, you can define the profiling attributes as DITA Map level: <topicref keys="slicing" href="slicing_vegetables_for_experts.dita" audience="expert"/> <topicref keys="slicing" href="slicing_vegetables_for_novices.dita" audience="novice"/>and thus, simplify the reference made in the topic content:Find our more about slicing vegetables: <xref keyref="slicing/>. Conditional Links in the Same PublicationUsing DITA 1.3 key scopes, you can reuse a topic multiple times in a DITA Map and have each referenced topic contain links to various target topics. For example, if my preparing_vegetables.dita topic has a link:<link keyref="slicing"/>you can define various key scopes in the DITA Map that bind the "slicing" key to various targets: <topichead navtitle="Cooking for Experts" keyscope="expert"> <topicref href="preparing_vegetables.dita" keys="preparing"/> <topicref href="slicing_vegetables_for_experts.dita" keys="slicing"/> </topichead> <topichead navtitle="Cooking for Novices" keyscope="novice"> <topicref href="preparing_vegetables.dita" keys="preparing"/> <topicref href="slicing_vegetables_for_novices.dita" keys="slicing"/> </topichead>This previous blog post contains more details about key scopes. Link Text When linking to an external resource or to a DITA topic or element, the publishing engine will attempt to deduce the link text from the target context. For example, the link to a DITA topic or element that contains a <title> will use that title as the link text. The link to an external resource (for example to http://www.oxygenxml.com) will, by default, use the HTTP location as the link text. You can also customize each link text individually. So, ask yourself this question: Should I leave the link text to be automatically computed or should I set a more friendly text? For internal links to elements that have a title, in general it is more flexible to not set a custom text and let the publishing engine decide one for you. For external links, you should usually specify your custom link text. Should I Link or Should I Reuse? Suppose you want to bring a certain paragraph, note, or section to the end user's attention. If that particular target element is not very large, you should always reuse it (using a content reference) instead of linking to it. Conclusions As with all large projects, managing links in a growing DITA project can be problematic, so you need to become organized. As an overview of what we've discussed so far, I suggest the following best practices: Linking is a form of reuse so: Reuse small pieces of content instead of linking to them Avoid too much linking (linking is disruptive) Use indirect links. It will allow you to reuse link text and make profiling/filtering easier while giving you a better overview of the outbound links for your project. If you want to experiment with the various linking strategies I discussed above, you can find some samples here: https://www.oxygenxml.com/forum/files/linking-strategies-samples.zip. -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

[oXygen XML Editor Blog] - Checking terminology when editing in Oxygen XML Editor
by oXygen XML Editor Blog 17 Jun '17

17 Jun '17

oXygen XML Editor Blog /////////////////////////////////////////// Checking terminology when editing in Oxygen XML Editor Posted: 15 Jun 2017 11:28 PM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/OPQOXtUW3J8/checking… In this blog post I will try to give a general overview about the current possibilities you have available to impose your own language checking rules when working with Oxygen XML Editor. Builtin support Oxygen comes bundled with the popular Hunspell spell checker and besides the regular bundled dictionaries for English, German, Spanish and French it allows you to install new dictionaries, either for other languages or custom dictionaries (for example dictionaries of medical terms) which you can build separately: https://www.oxygenxml.com/doc/versions/19.0/ug-editor/topics/spell-dictiona…. Besides the spell checker, Oxygen also has support for Auto-correct and you can add your own Auto-correct pairs to Oxygen. Commercial alternatives Acrolinx is a very popular commercial tool for checking content for consistency and terminology. The plugins Acrolinx developed for Oxygen standalone, Oxygen Eclipse plugin and Oxygen Web Author allow you to run the Acrolinx checker directly from inside the application. HyperSTE is yet another popular commercial tool for checking content and terminology. They also have a plugin for Oxygen standalone. Open source alternatives LanguageTools is an Open Source proofreading program for English, French, German, Polish, and more than 20 other languages . There is an open source plugin for Oxygen available on GitHub. The DITA Open Toolkit terminology checker plugin from Doctales contains Schematron rules checking that various words adhere to the terminology dictionaries which are custom built using DITA. Building your own terminology checker The fastest and simplest way to build a simple terminology checker is by using Schematron rules. The Doctales plugin is a good example for this. At some point, as the terminology dictionary keeps growing you may encounter delays and slow downs when editing the documents and validating it using the custom Schematron rules. So an alternative to this is by using our Author SDK to build your own Oxygen plugin which can use our API to check the content and then add highlights. The LanguageTools open source plugin may be a good starting example for this. -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

[oXygen XML Editor Blog] - Batch converting HTML to XHTML
by oXygen XML Editor Blog 13 Jun '17

13 Jun '17

oXygen XML Editor Blog /////////////////////////////////////////// Batch converting HTML to XHTML Posted: 12 Jun 2017 02:03 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/aF0B0Z1Zw1I/batch-co… Let's say you have a bunch of possible not-wellformed HTML documents already created and you want to process them using XSLT. For example you may want to migrate the HTML to DITA using the predefined XHTML to DITA Topic transformation scenario available in Oxygen. So you need to create valid XML wellformed XHTML documents from the existing HTML documents and you need to do this in a batch processing automated fashion. There are lots of open source projects which deliver processors which can convert HTML to its wellformed XHTML equivalent. For this blog post we'll use HTML Tidy. Here are a couple of steps to automate this process: Create a new folder on your hard drive (for example I created one on my Desktop: C:\Users\radu_coravu\Desktop\tidy) and download there the HTML Tidy executable specific for your platform: http://binaries.html-tidy.org/. In the same folder with the Tidy executable create an ANT build file called build.xml having the following content: <project basedir="." name="TidyUpHTMLtoXHTML" default="main"> <basename property="filename" file="${file}"/> <target name="main"> <exec command="tidy.exe -o ${output.dir}/${filename} ${file}"/> </target> </project> Link in the Oxygen Project view the entire folder where the original HTML documents are located. Right click the folder, choose Transform->Configure Transformation Scenarios... and create a new transformation scenario of type ANT Scenario. Modify the following properties in the transformation scenario: Change the scenario name to something relevant like HTML to XHTML. Change the Working Directory to point to the folder where the ANT build file is located, in my case: C:\Users\radu_coravu\Desktop\tidy. Change the Build file to point to your custom build.xml, in my case: C:\Users\radu_coravu\Desktop\tidy\build.xml. In the Parameters tab add a parameter called file with value ${cf} and a parameter called output.dir with value the path to the output folder where the equivalent XHTML files will be stored, in my case I set it to: C:\Users\radu_coravu\Desktop\testOutputXHTML. Apply the newly transformation scenario on the entire folder containing the HTML documents. At the end in the output folder you will find the XHTML equivalents of the original HTML files, XHTML documents which can later be processed using XML technologies like XSLT or XQuery. -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0

Saxon config file resources/fileExtension not supported
by Florent Georges 02 Jun '17

02 Jun '17

Hi, Not a big deal, but the element resources/fileExtension seems not to be supported when editing a Saxon config file. Some details there: http://saxon.markmail.org/thread/mdgdftkssbhbsjzr I just created a new file in oXygen, choosing "Saxon Config File". Regards, -- Florent Georges H2O Consulting http://h2o.consulting/

2 1

Chemistry PDF: build fails Cannot convert string "" to xs:decimal: no digits in value;
by Yves Barbion 27 Apr '17

27 Apr '17

Hi I'm trying to create a PDF from DITA content, using Chemistry but my build fails. I get this error message: BUILD FAILED C:\Program Files\Oxygen XML Author 19\frameworks\dita\DITA-OT2.x\build.xml:45: The following error occurred while executing this line: C:\Program Files\Oxygen XML Author 19\frameworks\dita\DITA-OT2.x\plugins\com.oxygenxml.pdf.css\build.xml:194: The following error occurred while executing this line: C:\Program Files\Oxygen XML Author 19\frameworks\dita\DITA-OT2.x\plugins\com.oxygenxml.pdf.css\build.xml:132: Fatal error during transformation using C:\Program Files\Oxygen XML Author 19\frameworks\dita\DITA-OT2.x\plugins\com.oxygenxml.pdf.css\xsl\post-process.xsl: Cannot convert string "" to xs:decimal: no digits in value; SystemID: file:/C:/Program%20Files/Oxygen%20XML%20Author%2019/frameworks/dita/DITA-OT2.x/plugins/com.oxygenxml.pdf.css/xsl/post-process-tables.xsl; Line#: 100; Column#: 80 Any ideas? Thanks Yves

2 1

[oXygen XML Editor Blog] - DITA Inheritance Hierarchy
by oXygen XML Editor Blog 25 Apr '17

25 Apr '17

oXygen XML Editor Blog /////////////////////////////////////////// DITA Inheritance Hierarchy Posted: 24 Apr 2017 02:20 PM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/_uE1DzO51sg/dita-inh… The DITA standard is based on this concept of inheritance which allows extending or restricting the vocabulary while allowing the XML content to still be regarded as valid DITA. Even in the DITA standard there are various element which are specializations of others (for example "b" is a specialization of ph"). The XSLT styesheets which are used for publishing match all DITA elements by the value of their @class attribute so knowing how elements may extend each other may be useful when customizing the DITA XSLTs. A DITA inheritance hierarchy list for the base DITA specification is presented below. Would you consider it useful if a future version of Oxygen would have some kind of a tool to show such hierarchies even for custom DITA specializations? topic/copyryear topic/foreign mathml-d/mathml svg-d/svg-container topic/author topic/example topic/unknown topic/titlealts topic/linktext topic/category topic/data relmgmt-d/change-request-reference relmgmt-d/change-person relmgmt-d/change-request-id relmgmt-d/change-request-system relmgmt-d/change-completed relmgmt-d/change-started ut-d/sort-as relmgmt-d/change-item relmgmt-d/change-organization relmgmt-d/change-summary concept/data glossentry/glossPartOfSpeech glossentry/glossProperty glossentry/glossStatus relmgmt-d/change-revisionid topic/longdescref topic/audience topic/abstract concept/abstract glossentry/glossdef topic/related-links topic/body task/taskbody concept/conbody glossentry/glossBody troubleshooting/troublebody reference/refbody topic/ph hi-d/overline hi-d/line-through hi-d/sub pr-d/sep equation-d/equation-inline pr-d/repsep equation-d/equation-number hi-d/tt task/cmd pr-d/synph sw-d/userinput ut-d/coords pr-d/oper hi-d/sup pr-d/var sw-d/msgph pr-d/codeph ui-d/uicontrol hi-d/i hi-d/u sw-d/filepath sw-d/systemoutput pr-d/delim hi-d/b ui-d/menucascade topic/object topic/fig ut-d/imagemap pr-d/syntaxdiagram equation-d/equation-figure topic/featnum topic/lines topic/brand topic/state topic/source topic/link topic/vrm topic/sli topic/navtitle topic/figgroup pr-d/synblk pr-d/fragment ut-d/area pr-d/groupcomp pr-d/groupseq pr-d/groupchoice topic/note hazard-d/hazardstatement concept/note glossentry/glossScopeNote glossentry/glossUsage topic/ol task/substeps task/steps topic/stentry task/choption reference/propvalue reference/propvaluehd reference/propdeschd reference/propdesc reference/proptype reference/proptypehd task/choptionhd task/chdesc task/chdeschd topic/dlentry pr-d/plentry topic/vrmlist topic/entry topic/fn pr-d/synnote topic/xref mathml-d/mathmlref svg-d/svgref concept/xref glossentry/glossAlternateFor pr-d/synnoteref pr-d/fragref pr-d/coderef topic/component topic/series topic/bodydiv reference/refbodydiv troubleshooting/troubleSolution concept/conbodydiv topic/data-about topic/tgroup topic/keywords topic/boolean topic/critdates topic/strow task/chrow reference/property topic/simpletable reference/properties task/choicetable topic/linklist topic/revised topic/table topic/dt pr-d/pt topic/image hazard-d/hazardsymbol concept/image glossentry/glossSymbol topic/ul hazard-d/messagepanel task/choices task/steps-unordered topic/p concept/p glossentry/glossSurfaceForm troubleshooting/responsibleParty topic/q topic/linkinfo topic/dd pr-d/pd topic/lq topic/prodinfo topic/dl pr-d/parml topic/prolog topic/indextermref topic/copyright topic/div equation-d/equation-block topic/sthead task/chhead reference/prophead topic/tbody topic/searchtitle topic/colspec topic/created topic/tm topic/text topic/cite topic/li hazard-d/howtoavoid task/step task/substep hazard-d/consequence hazard-d/typeofhazard task/choice task/stepsection topic/permissions topic/no-topic-nesting topic/dlhead topic/prodname topic/index-base indexing-d/index-sort-as indexing-d/index-see indexing-d/index-see-also topic/indexterm topic/copyrholder topic/longquoteref topic/required-cleanup topic/ddhd topic/sl topic/draft-comment topic/section task/postreq task/result troubleshooting/remedy task/tasktroubleshooting concept/section glossentry/glossAlt task/context troubleshooting/cause task/steps-informal reference/refsyn task/prereq troubleshooting/condition topic/pre sw-d/msgblock pr-d/codeblock ui-d/screen topic/topic troubleshooting/troubleshooting concept/concept glossgroup/glossgroup glossentry/glossentry reference/reference task/task topic/platform topic/alt topic/keyword ui-d/shortcut markup-d/markupname xml-d/parameterentity xml-d/xmlatt xml-d/numcharref xml-d/xmlpi xml-d/textentity xml-d/xmlnsname xml-d/xmlelement pr-d/parmname pr-d/option sw-d/cmdname ui-d/wintitle ut-d/shape sw-d/varname pr-d/apiname pr-d/kwd sw-d/msgnum topic/thead topic/publisher topic/desc topic/term abbrev-d/abbreviated-form topic/title concept/title glossentry/glossShortForm glossentry/glossAbbreviation glossentry/glossSynonym glossentry/glossterm glossentry/glossAcronym topic/itemgroup task/steptroubleshooting task/tutorialinfo task/info task/stepxmp task/stepresult topic/row topic/linkpool topic/param topic/shortdesc topic/resourceid topic/dthd topic/metadata relmgmt-d/change-historylist topic/othermeta topic/prognum topic/sectiondiv -- You are subscribed to email updates from "oXygen XML Editor Blog." To stop receiving these emails, you may unsubscribe now: https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51Jnl… Email delivery powered by Google. Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

1 0