- oXygen-user - www.oxygenxml.com

[ANN] Webinar - New DITA Features in oXygen XML Editor 17
by Radu Coravu 09 Jun '15

09 Jun '15

Hi, This Wednesday (Jun 10, 2015 8:00 AM PDT) we are hosting a new free webinar in which we will explore lots of exciting new DITA-related features that were added in Oxygen 17.0. If you are already using DITA with Oxygen, or you are interested in knowing more about it, please register using the following link: > http://www.oxygenxml.com/events/2015/webinar_oxygen_17_dita_support.html We look forward to meeting you! Best regards, Radu Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

[Ann] New maintenance build available for oXygen 17.0 (2015052917)
by Oxygen XML Editor Support (Adrian Buza) 05 Jun '15

05 Jun '15

Dear oXygen users, We announce the release of a new maintenance build (2015052917) for oXygen 17.0 (XML Editor, XML Developer, XML Author). 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#2015052917 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.2020 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0

Free Webinar - Producing PDF, RTF and EPUB using TopLeaf DITA OT plugins from Oxygen
by Radu Coravu 02 Jun '15

02 Jun '15

Hi everybody, If you are interested in alternatives for generating output using the DITA Open Toolkit: This webinar will demonstrate how to create professionally styled output from DITA content generated by the DITA Open Toolkit either via a command line or from Oxygen XML editor. Topics covered include: • A brief overview of TopLeaf • TopLeaf for DITA • TopLeaf DITA integration • TopLeaf rendering methodology • TopLeaf style sheet development tools • Single source publishing to PDF, RTF and eBook More about TopLeaf: TopLeaf is a professional DITA and XML publishing system from Turn-Key Systems. TopLeaf contains built-in features which facilitate the creation of efficient and powerful stylesheets for styling DITA documents. TopLeaf stylesheets can be quickly modified to create output from any DITA document. If this sounds interesting for you: The webinar will be held in English. Date of Webinar: Monday, June 8,2015 – 11:00 AM – 11:30 AM CEST Please register under the following Link: > https://attendee.gotowebinar.com/register/7101232498760530434 After initial registration you’ll automatically receive a confirmation e-mail with the information about the attendance of the webinar. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 1

Validating CSS
by David Birnbaum 27 May '15

27 May '15

Dear Alex (cc oxygen-user list), Thank you for the quick response. I wonder whether it might be possible to use checkboxes instead of a single selection, so that users could combine profiles selectively according to their specific needs. I also wonder, though, about the possibility of associating a CSS profile in <oXygen/> with a specific CSS stylesheet document, that is, at finer granularity than is available through project-level or global preferences. I have a project that uses multiple stylesheets, some that contain just HTML5 selectors and some that mix HTML5 selectors with SVG selectors. I can put those stylesheets in different projects and specify different CSS profiles that way, but they really belong in the same project for other reasons, and in the non-SVG CSS files I'd want to raise an error if, for example, I specify a "width" value as a non-zero number without a unit of measurement, although that wouldn't be an error in an SVG context. This organization would be analogous to having different schemas for different XML documents in the project; here there would be different CSS profiles for different CSS documents in the project. I realize that there are other complications (e.g., validating inline or otherwise embedded CSS within an XML document), though, so I'm not sure how practical this idea would turn out to be. Best, David > Currently there is no solution to this problem. I will ad an issue to > find a solution to such a situation. Perhaps a new entry in the profile > combo that will state "All known profiles". > > I have an HTML5 document (XML syntax) with inline SVG and I'd like to > > associate a single external stylesheet with it that specifies both > > CSS3 and SVG properties. The <oXygen/> documentation at > > > http://www.oxygenxml.com/doc/versions/17.0/ug-author/index.html#topics/pref… > , > > which matches what I see in my configuration options, seems willing to > > allow me to select CSS3 or SVG, but not both simultaneously. Is there > > a way to obtain the sort of validation I'm looking for? I can choose > > CSS3 in the option menu and ignore the error messages for the SVG > > properties, but I'd rather have the benefit of validating both. >

4 3

Validating CSS
by David Birnbaum 25 May '15

25 May '15

Dear <oXygen/> user list, I have an HTML5 document (XML syntax) with inline SVG and I'd like to associate a single external stylesheet with it that specifies both CSS3 and SVG properties. The <oXygen/> documentation at http://www.oxygenxml.com/doc/versions/17.0/ug-author/index.html#topics/pref…, which matches what I see in my configuration options, seems willing to allow me to select CSS3 or SVG, but not both simultaneously. Is there a way to obtain the sort of validation I'm looking for? I can choose CSS3 in the option menu and ignore the error messages for the SVG properties, but I'd rather have the benefit of validating both. Thanks, David

2 1

Custom placeholders for empty elements?
by Richard Forster 22 May '15

22 May '15

Hello List Is there a way of customizing the placeholders shown in Oxygen Author view for empty elements? >From the shelf the system just repeats the tag name on gray background. As soon as I start typing something into the element, the placeholder disappears. What I would like to have is the same behavior but with a custom string/instructions being shown instead of the tagname. Is this possible? Best regards Richard

2 2

About oXygen XML Editor
by About oXygen XML Editor 22 May '15

22 May '15

About oXygen XML Editor /////////////////////////////////////////// Schematron Checks to help Technical Writing Posted: 21 May 2015 03:56 AM PDT http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/eQSoXbR5Vjg/schematr… The Oxygen XML Editor User's Manual is written in DITA. In an older post I described in more detail how we collaborate internally on our User's Guide Project. And we also made available a copy of our User's Manual as a project on GitHub. During these years on working on it, we progressively developed a set of simple rules which were originally kept in a plain text document. The problem is that nobody can really remember all these rules when actually writing. So recently we started to migrate these rules to Schematron and have them reported automatically has validation warnings and errors while editing the topics. And with the release of Oxygen 17 we can now also add quick fixes for each of these problems. So below I will try to tell you what each rule imposes and what it's Schematron implementation looks like. If you want to quickly test these rules on your side, you can add them to the Schematron file which is used by default to validate DITA topics located in: OXYGEN_INSTALL_DIR/frameworks/dita/resources/dita-1.2-for-xslt2-mandatory.sch. Try as much as possible to add at least an indexterm element in each topic. This is useful when the Index page is created for the PDF output or the Index tab is created for the WebHelp output. As this is not a requirement, we wanted to report this issue as an error. The end result looks like this: And the Schematron pattern looks like this:<pattern xmlns:sqf="http://www.schematron-quickfix.com/validator/process"> <rule context="/*"> <assert test="prolog/metadata/keywords/indexterm" role="warn" sqf:fix="addFragment"> It is recommended to add an 'indexterm' in the current '<name/>' element. </assert>  <sqf:fix id="addFragment"> <sqf:description> <sqf:title>Add the 'indexterm' element</sqf:title> </sqf:description> <sqf:add match="(title | titlealts | abstract | shortdesc)[last()]" position="after" use-when="not(prolog)"> <prolog xmlns=""><metadata><keywords><indexterm> </indexterm></keywords> </metadata></prolog> </sqf:add> </sqf:fix> </rule> </pattern> The ID of each topic must be equal to the file name (minus the extension). One of the outputs we produce (I think CHM) had a limitation when building the context mapping between help IDs and actual HTML content so this was an important rule for us, thus an error is reported on this. Also a quick fix is added to auto-correct the topic ID based on the file name. The end result looks like this: and the Schematron pattern is: <sch:pattern> <sch:rule context="/*[1][contains(@class, ' topic/topic ')]"> <sch:let name="reqId" value="replace(tokenize(document-uri(/), '/')[last()], '\.dita', '')"/> <sch:assert test="@id = $reqId" sqf:fix="setId"> Topic ID must be equal to file name. </sch:assert> <sqf:fix id="setId"> <sqf:description> <sqf:title>Set "<sch:value-of select="$reqId"/>" as a topic ID</sqf:title> <sqf:p>The topic ID must be equal to the file name.</sqf:p> </sqf:description> <sqf:replace match="@id" node-type="attribute" target="id" select="$reqId"/> </sqf:fix> </sch:rule> </sch:pattern> Report when plain links or related links to web resources have the same text inside them as the value of the @href attribute. We had cases in which writers would input web links like this:<xref href="http://www.google.com" format="html" scope="external">http://www.google.com</xref>which is redundant because when you set no text to the link, the publishing uses the @href attribute value as the link text. So we wanted to report such cases as warnings and to have a quick fix which removes the link text: The Schematron pattern looks like this:<sch:pattern> <sch:rule context="*[contains(@class, ' topic/xref ') or contains(@class, ' topic/link ')]"> <sch:report test="@scope='external' and @href=text()" sqf:fix="removeText"> Link text is same as @href attribute value. Please remove. </sch:report> <sqf:fix id="removeText"> <sqf:description> <sqf:title>Remove redundant link text, text is same as @href value.</sqf:title> </sqf:description> <sqf:delete match="text()"/> </sqf:fix> </sch:rule> </sch:pattern> Avoid using the @scale attribute on images. We wanted to smooth scale images in an external image editor so it was prohibited to use the @scale attribute on images. The Schematron pattern for this:<pattern> <rule context="*[contains(@class, ' topic/image ')]"> <assert test="not(@scale)"> Dynamically scaled images are not properly displayed, you should scale the image with an image tool and keep it within the recommended with and height limits. </assert> </rule> </pattern> We have an upcoming webinar dedicated to Schematron Quick Fixes. There is a W3C working group for XML Quick Fixes and you calso read the SQF Quick Fix specification if you want to become more familiar with the technology. We also have a GitHub project which tries to combine the notion of a style guide for writing documentation inside a company with a very simple manner of defining checks which can be applied to impose the styleguide rules. I would be interested in your feedback, especially if you have checks that you perform right now on your content and you consider that they might benefit others. -- You are subscribed to email updates from "About oXygen XML Editor." 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

Default zoom factor in oXygen XML Editor 17
by Yves Barbion 21 May '15

21 May '15

Hi group Is there a way to reset or revert to the default zoom factor in oXygen XML Editor 17? In one of the DITA topics I was editing, I zoomed in to, say 150 % (or something). I did so by holding down the CTRL key and using the scroll wheel on my mouse. Every topic I open or create from now on seems to be displayed at this zoom factor. I have tried to reset my "layout" (workspace) and to quit and restart oXygen, but that does not seem to help. I also looked up "zoom" in the oXygen preferences and in the Help file, but I didn't find anything relevant there. Thanks. -- Yves Barbion www.scripto.nu

2 2

Opening dialog boxes from xslt - It works!
by Patrik.Stellmann＠gdv-dl.de 20 May '15

20 May '15

Hi, I lately implemented custom saxon instructions that allow to create a message boxes or option dialogs from within an XSLT script. Since it turned out to be pretty easy to implement and very useful within my framework, I just wanted to share this idea - and the joy over oxygen, that even this is possible. One use-cases would be a transformation that potentially overwrites an existing file and asks the user before doing so (if the file already exists). The code looks like this: <xsl:if test="java:fileExists($myFile)"> <xsl:variable name="userDecision" as="xs:integer"> <gui:option-dialog title="Warning" options= "('Continue', 'Abort')" default="1"> <xsl:text/>The file '<xsl:value-of select= "$myFile"/>' already exists and will be overwritten.<xsl:text/> </gui:option-dialog> </xsl:variable> <xsl:if test="$userDecision = 1"> <xsl:message terminate="yes">Abort on user request </xsl:message> </xsl:if> </xsl:if> To implement such extension instructions you will have to implement your own java library and put it into oxygens lib folder. To do so follow the saxon documentation at http://www.saxonica.com/documentation/#!extensibility/instructions and - much more important - look at the sample of Saxon-SQL, which is included in the open source edition of saxon: http://sourceforge.net/projects/saxon/files/Saxon-HE/) Make sure to use the same version as included into oxygen! To open the actual dialog you can use something like JOptionPane.showOptionDialog( (Frame)PluginWorkspaceProvider.getPluginWorkspace ().getParentFrame(), textString, titleString, (optionList.size() == 2) ? JOptionPane.YES_NO_OPTION : JOptionPane.YES_NO_CANCEL_OPTION, JOptionPane.PLAIN_MESSAGE, null, optionList.toArray(new String[optionList.size()]), defaultOption); (If someone should be interested - I will also gladly share my java code.) There is also an entry in the forum for this: http://www.oxygenxml.com/forum/topic11531.html Regards, Patrik GDV Dienstleistungs-GmbH & Co. KG Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de Sitz und Registergericht: Hamburg HRA 93 894 USt.-IdNr : DE 205183123 Komplementärin: GDV Beteiligungsgesellschaft mbH Sitz und Registergericht: Hamburg HRB 71 153 Geschäftsführer: Dr. Jens Bartenwerfer Michael Bathke Heiko Beermann Volker Sonnenburg ------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet. This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distributionof the material in this e-mail is strictly forbidden.

1 0

Oxygen 17 UI improvements webinar on Wednesday
by Oxygen XML Editor Support (Radu Coravu) 19 May '15

19 May '15

Hi everybody, Just wanted to remind you that on Wednesday (May 20, 2015) we'll be hosting a free webinar with the new UI improvements we added in Oxygen 17: > http://www.oxygenxml.com/events/2015/webinar_oxygen_17_ui_improvements.html So if anybody's interested, please join in. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0