July 2012 - oXygen-user - www.oxygenxml.com

BaseX Support in oXygen?
by Hannes Bauer 14 Nov '12

14 Nov '12

Dear developer team, oXygen is our favorite XML editor - but it seems to lack good support for our favorite XML database BaseX. While I cannot find any reference to "BaseX" in the dialog windows of oXygen, I have found some information in the BaseX documentation, describing how to open documents via WebDAV or execute queries via XQuery (http://docs.basex.org/wiki/Integrating_oXygen) But those two variants don't seem to complement each other. I would be very interested... a) if you plan a better integration of BaseX in your system? b) what's currently the easiest way to access all BaseX databases and documents from within oXygen? In other words, do I always have to use "File" -> "Open URL..." to get all database resources listed? Thanks a lot in advance, Hannes PS: I've tried to send this mail quite a while ago, but apparently it didn't make it to the list, so this is the second run.. Sorry for persistiing.

3 7

Behavior regarding conkeyref before keydef
by KAATMAN Matthew 02 Aug '12

02 Aug '12

Hey Everyone, This is a fairly explainable situation and not causing major problems but I'm curious if there is a way to get around it. Here's the scenario: 1. I have a map with a conkeyref in the mainbooktitle. Then in the front matter I define the keydef: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN" "bookmap/dtd/bookmap.dtd"> <bookmap format="ditamap" id="bookmap_User_Manual_Previ_Color"> <booktitle> <mainbooktitle><ph conkeyref="productinfo/prodname"/></mainbooktitle> </booktitle> <frontmatter> <keydef format="dita" href="user/ProductVariables.xml" keys="productinfo" processing-role="resource-only" type="topic"/> When I first load this map in Oxygen it loads the map title before it reads the keydef which results in a warning: System ID: C:\dita\products\vitek2systems\EN\Vitek2Systems_User_Manual.ditamap Severity: warning Description: [Document]:Could not resolve the target for key reference "productinfo/prodname" Screenshot: http://i.imgur.com/bXnnE.png If I open the map and make any change (Hit space, hit backspace, hit save) it then reads the title correctly. Is there another place I can define my keydef to avoid this? Or any other workaround? Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

4 4

Re: [oXygen-user] Find/Replace in Files: unable to find pretty-printed word combinations
by Sorin Ristache 01 Aug '12

01 Aug '12

Hi, We added the support for spanning multiple lines with a regular expression in Find/Replace in Files in Oxygen 14.0. So if you use an older version of Oxygen the regular expression that contains (\s+) will find only the matches that span one line, that is it will not match the end-of-line character. You did not specify your Oxygen version but I think it is older than 14.0. I checked in Oxygen 13.2 and this feature was not present, it is a new feature of version 14.0. If you do not use version 14.0 please upgrade. Regards, Sorin Yves Barbion wrote: > Hi Sorin > > I have checked all the options in the Find/Replace in Files dialog box > and I have also included a screen shot in the attached ZIP file. > > Thank you in advance for your assistance. > > Yves Barbion > www.scripto.nu > > > > On 31-07-2012 12:47, Sorin Ristache wrote: >> Hi, >> >> Please check all the values in the Find/Replace in Files dialog box: >> scope should be "Current DITA map hierarchy", file filter should be >> *.dita (or *.xml), etc. If all values are correct in the dialog box >> please send a sample DITA topic file that should be found by the find >> action but is not found and also specify the search string that you used. >> >> >> Regards, >> Sorin >> >> >> Yves Barbion wrote: >>> Hi Sorin >>> >>> Thank you for your prompt reply, but I'm afraid we're not quite there >>> yet. When I search for "time(\s+)zone" (without the quotes), oXygen >>> does not find it. A similar example is this: >>> >>> <p status="changed">The body of the <keyword >>> >>> conref="_conref_library.xml#topic_qjt_sdx_1f/keyword_wms_s2x_1f"/> >>> consists of >>> the following zones:</p> >>> >>> When I search for "consists of(\s+)the following" or >>> "consists(\s+)of(\s+)the(\s+)following" with the Regular Expression >>> option selected, oXygen will only find the occurrences where there is >>> only a single space between the words. >>> >>> Any other ideas? >>> >>> Thanks. >>> >>> Yves

3 4

Bug Report: Oxygen thinks DocBook <reference> is DITA <reference>
by Barton Wright 01 Aug '12

01 Aug '12

Hello to Oxygen Support, with thanks for such an excellent product. There is a small bug in a reproducible corner case, where Oxygen gets confused by a DocBook 4 <reference> element used at the top level of a file, and tries to validate the file in the DITA context. I’m attaching a zip file containing example files. This was tested with Oxygen 14, but I’ve seen this behavior in previous releases. Steps to reproduce: 1. Create a new DocBook 4 file from the article template in Oxygen. 2. In the new file, replace “DOCTYPE article” with “DOCTYPE reference”, and change both instances of 4.5 to 4.4 (to match the standard we still use). 3. In the new file, replace the entire <article> contents with the contents of the <reference> example from the DocBook Definitive Guide at http://docbook.org/tdg/en/html/reference.html. 4. Add a <referenceinfo> element above the <title> element, containing one <corpauthor> element that contains any string. 5. A file as described above is in the attached zip file as def-guide-reference-example-1.xml. 6. This file validates as a DocBook file in Oxygen, as expected, as well as in XXE (XMLMind XML Editor) and with xmllint. But wait, there’s more: 7. Now create two more new DocBook 4.4 files as described above. Change to “DOCTYPE refentry” and replace the <article> contents with the two <refentry> elements from the first example. 8. Two files as described here are in the zip file as awk.xml and gnu-as.xml. 9. Now replace the <refentry> elements in the main file with XInclude references to the two <refentry> files. A file as described here is in the zip file as def-guide-reference-example-2.xml. 10. This second example validates fine in XXE and with xmllint, both of which can resolve XIncludes in DocBook 4 files. 11. As expected, this file fails to validate in Oxygen because Oxygen cannot natively resolve XIncludes in DocBook 4 files. (We are used to this fact of life, and wish it were otherwise.) But that’s not the problem. Notice the validation failure messages, which begin as follows: [cid:image001.png@01CD6E3C.66BF2B30] 12. Even if you edit this second example to add Oxygen’s xinclude.mod support, the file is still considered to be in the DITA context. 13. Further, copy a valid <refentry> element back into the file so that it has one <refentry> local to the file and two XIncluded <refentry> pages, and validation still fails with the message shown above. 14. Comment out the XIncludes, and Oxygen validation returns to the DocBook context. Conclusion: there is something about the combination of a <reference> top-level element and an <xi:include> element that makes Oxygen ignore the DOCTYPE declaration and instead treat the file as a DITA file. Note again that XXE and xmllint* have no problem with this combination. We grudgingly accept the fact that Oxygen does not support XIncludes in DocBook 4 files unless the xinclude.mod kludge is used. But Oxygen should never consider an otherwise valid DocBook-declared file as a DITA file, despite the use of the <reference> element in both standards. *Our xmllint validation command is: xmllint --xinclude --catalogs --timing --noout --noent –postvalid filename.xml You can ignore a message that SGML_CATALOG_FILES is not set, or just set that to =/etc/xml/catalog. (Tested on Cygwin 1.7 and Linux Mint 11.)

3 4

Find/Replace in Files: unable to find pretty-printed word combinations
by Yves Barbion 31 Jul '12

31 Jul '12

Hi group I'm using Find/Replace in Files in oXygen XML Editor 13 to quickly find a word in all DITA topics referenced in a DITA map. Sometimes, however, I see that a given word combination cannot be found, even though I'm sure that the word combination is used in one of my topics. When I open the topic and look at the text in plain text view, I see that the word combination is split by a line break because the text is indented ("pretty print"), for example: <title><keyword conref="_conref_library.xml#topic_qjt_sdx_1f/keyword_wms_s2x_1f"/> time zones</title> When I look for "time zones" using Find/Replace in Files, oXygen cannot find it. Is there a simple way to fix this? Thanks. -- Yves Barbion www.scripto.nu

2 3

Saxon and strange behaviour of xsl:sort with lang
by Jirka Kosek 26 Jul '12

26 Jul '12

Hi, I have hit strange behaviour when invoking Saxon from oXygen. It seems that lang attribute is not honoured when used on xsl:sort while collation works properly. Plese see following transformation: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="2.0"> <xsl:variable name="data" select="('Zdena', 'Chvojí', 'Cimbál', 'Čočka')"/> <xsl:template name="main"> <xsl:for-each select="$data"> <xsl:sort select="." lang="cs"/> <xsl:value-of select="."/> <xsl:text>, </xsl:text> </xsl:for-each> <xsl:text>
</xsl:text> <xsl:for-each select="$data"> <xsl:sort select="." collation="http://saxon.sf.net/collation?lang=cs"/> <xsl:value-of select="."/> <xsl:text>, </xsl:text> </xsl:for-each> </xsl:template> </xsl:stylesheet> It should produce the following result (at it produces it when Saxon is invoked from command-line): Cimbál, Čočka, Chvojí, Zdena, Cimbál, Čočka, Chvojí, Zdena, But when run from oXygen output is wrong, lang="cs" is not honoured: Chvojí, Cimbál, Čočka, Zdena, Cimbál, Čočka, Chvojí, Zdena, Is there anything in Saxon integration which interferes with lang? Or perhaps JVM issue? Thanks for englightenment, Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka(a)kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------

3 5

"Create non existing component" in the light bulb list
by Florent Georges 17 Jul '12

17 Jul '12

Hi, If in a stylesheet, I write down in an XPath expression a call to a function that does not exist yet (I do that all the time, using a function before actually writing it...), there is a light bulb on the left column, with some helper features. But the list does not include a "Create the function XYZ" as it is usually in Java IDEs for instance. Could be a good idea to improve that list? Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

2 2

List not updated when duplicating a scenario
by Florent Georges 17 Jul '12

17 Jul '12

Hi, Using oXygen 14.0, I have a stylesheet, I press "Configure Transform Scenarios", I have one XSLT scenario and I press "Duplicate", I change the name and I press "Ok". Even though the "Associated scenarios" list is properly updated with the new scenario, the main list does not show the new scenario. Hope that helps. Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

2 1

Add comment... + deleted text in track changes
by David Cramer 15 Jul '12

15 Jul '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, The "Add comment.." feature is handy when collaborating with another person who is also editing the document source with oXygen. In addition to asking questions of my collaborator, I like using it in conjunction with oXygen's track changes to indicate why I made certain changes. However, I notice that you cannot add a comment to a deletion. So sometimes I have to be creative (e.g. associate the comment with some "space" chars immediately before the deletion). It would be cool if I could associate my comment with the actual deletion. This isn't a must have, just a minor enhancement to some already nice functionality. Thanks, David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQAZdHAAoJEMHeSXG7afUhz4YH/327pn++Pa6gmETXoPwcDoMs PSvhQLE/pYZeie8J+R0Sgu2a5z4wBMkPcuxgS7PnLE6H+wBhLEdYERGZY3xbpJqK BjowHZVplu91BHrqlQ3SbqLMZm3+Fe/tSjiAYfWYab/yaLxYrpEssHyJ3cJ4Aq3/ u8zOsa6XMRGlMxdt/ewyjaIDPMaG/0rPp4+YT5m9OExJ1MhK5uEz0PxJinmM/EGX jrMAYIjcuL1ZUs2rWXZh3nRiB8Q2XiBBvK0dmDehxwmQoh/8qPG3+MIep3L2fsaF KvqD8x0j8gVZxGP4M3+4f+9uQH4SHmRUZI/XF+mREuluHYCyUm+l9wS5PwtJl8s= =NCrz -----END PGP SIGNATURE-----

2 5

font size in oxygen 13.2?
by Roderik Dernison 13 Jul '12

13 Jul '12

Hi, How can I enlarge the font size in Oxygen 13.2, in the author mode? I've tried Crtrl +, but that doesn't have any effect. Kind regards, Roderik Dernison ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ----------------------------------------------------------

4 5