- oXygen-user - www.oxygenxml.com

[Ann] New maintenance build available for oXygen 17.1 (2015121117)
by Oxygen XML Editor Support (Adrian Buza) 17 Dec '15

17 Dec '15

Dear oXygen users, We announce the release of a new maintenance build (2015121117) for oXygen 17.1 (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#2015121117 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

FTP from inside XProc in oXygen?
by Wendell Piez 15 Dec '15

15 Dec '15

Fellow oXygen connoisseurs, I have attached an FTP site to my Data Source Explorer, which makes me happy, as it is easy to upload results of my XProc Transformation Scenario to my site just by copying from the Project view. What I wonder is whether this operation could not be simplified even further. This process in particular is an XProc pipeline, which generates some results and creates others by moving static resources in the file system. (So p:store and p:zip are involved, it's not just binding pipeline results.) If I could configure either or both the Transformation Scenario or the XProc itself to write to my (authenticated) FTP server, I would be overjoyed. I would welcome any hints or ideas. Thanks! Cheers, Wendell -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

3 2

How to include smaller files into a "master document" in Oxygen?
by Jean-Luc Chevillard 11 Dec '15

11 Dec '15

Greetings! I am currently editing several XML files which are the chapters of a Tamil thesaurus, and each file is dangerously close to the size limit connected with the script specificity. ("support for RTL languages" has to be activated, for proper display, and I have already increased the default size beyond which RTL language support is automatically deactivated) I would appreciate pointers on the best methods for dealing with the larger entity, i.e. the sum of the chapters. Can I create a MASTER document in Oxygen in which the chapters are INCLUDED (by mentionning their names) for the sake of processing the sum of the chapters? (I currently run XSLT transformations on separate chapters for making indices? How to do that for the sum of the chapters?) Thanks for any pointers to the appropriate section inside the Oxygen documentation (provided that it is possible to do that in Oxygen ...). If the "RTL language" limit was not there, I would have used a single file but that does not seem to be possible. -- Jean-Luc Chevillard (Paris-Pondicherry-Hamburg) "https://univ-paris-diderot.academia.edu/JeanLucChevillard"

3 6

xd:doc documentation generation and maven
by cmarchand＠oxiane.com 11 Dec '15

11 Dec '15

Hello, is there a way to automate a XSL documentation generation - ideally from a maven project.. ? Is there an entry in Oxygen API to generate such a documentation that a maven plugin - or any other tool - could reuse ? Well, the purpose is to generate a xsl-library documentation from continuous integration, so it can be done in a jenkins plugin (which is simpler than in a maven plugin). Any hint ? Best regards, Christophe

5 5

Any way to control output of Schematron validation?
by Maloney, Christopher (NIH/NLM/NCBI) [C] 09 Dec '15

09 Dec '15

We are using schematron validation in oXygen, with a custom element in our output messages. I'm finding that this causes the output messages to be unusable, because they are displayed on only one line, and that line is taken up by the custom element, and all of it's various namespace declarations. I'm attaching a screenshot -- not sure if it will get through the mailman. Is there any way to configure oxygen to show the text value of these messages? It would be much more useful. As it is, the user has to hover the mouse over the message, or r-click and do "show messages", and even then, the message is dominated by this element, because of all the (unused) namespace declarations on it. Thanks! -- Chris Maloney NIH/NLM/NCBI (Contractor) Building 45, 4AN36D-12 301-594-2842

6 10

Oxygen XML Blog Post: Overview of DITA Reuse Strategies
by Radu Coravu 02 Dec '15

02 Dec '15

Hi everybody, Just finished my latest blog post. It's an overview about all possibilities of reusing content with DITA: > http://blog.oxygenxml.com/2015/11/dita-reuse-strategies-short-tutorial.html Hope you'll enjoy it. If you have any feedback, it is as usual welcomed. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

[oXygen XML Editor Blog] - Sharing Application Settings
by oXygen XML Editor Blog 26 Nov '15

26 Nov '15

oXygen XML Editor Blog /////////////////////////////////////////// Sharing Application Settings Posted: 24 Nov 2015 11:44 PM PST http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/ijz2ztr8NGQ/sharing-… There are varios ways in the Oxygen standalone version through which a team of writers can share and use a set of common settings. Below I will try to list each of these possibilities along with useful links: Save the settings at project level and have all users use the same project "projectName.xpr" file in the Project view when editing. Most of the Oxygen Preference pages have a switch radio button which allows you to pass the settings to Project level and save them in the current project configuration file opened in the Project view. If you commit that Project configuration file to a version control system like GIT or SVN, all writers can open and use that project when working with the repository content. For example, when we work on the Oxygen User's Manual using our common GitHub repository, we all open in the Project view the "userguide.xpr" project which comes with various fixed options (eg: enabling automatic spell checking):https://github.com/oxygenxml/userguide You can find out more details about sharing projects here: https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/sharing-proje…. Create and then provide a default options XML document to others. When placed in a specific place in the Oxygen installation or referenced via a specific property in the application startup script, this default options XML document will be used by the application to provide default values for certain settings. You can find out more about how default options work here:https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/default-…. Have others manually import an options XML document which you exported from Oxygen:https://www.oxygenxml.com/doc/versions/17.1/ug-editor/#topics/import…. An Oxygen plugin could use our Java API to impose fixed options when the application starts using the API method: PluginWorkspaceProvider.getPluginWorkspace().setGlobalObjectProperty(key, value). In our Maven-based SDK we have a sample plugin called ImposeOptions which imposes a fixed set of options when the application starts. If you want to share document type configurations (for editing certain XML vocabulary) you can find more details in this older blog post: http://blog.oxygenxml.com/2015/08/document-type-extension-sharing.html. -- 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

[Ann] New maintenance build available for oXygen 17.1 (2015111718)
by Oxygen XML Editor Support (Adrian Buza) 20 Nov '15

20 Nov '15

Dear oXygen users, We announce the release of a new maintenance build (2015111718) for oXygen 17.1 (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#2015111718 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

[oXygen XML Editor Blog] - Possibilities to obtain PDF from DITA
by oXygen XML Editor Blog 18 Nov '15

18 Nov '15

oXygen XML Editor Blog /////////////////////////////////////////// Possibilities to obtain PDF from DITA Posted: 16 Nov 2015 01:07 PM PST http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/sXZMCVP56Pc/possibil… Lately while attending Tekom 2015 and DITA OT Day 2015 I happened to come across two more DITA to PDF solutions that I did not know about so I tried to compile below a list of all DITA to PDF possibilities that I know of, along with some details: Legacy DITA to PDF editing solution. It is no longer distribute with DITA OT 2.x and is probably not compatible anymore with it. Default DITA to PDF solution embedded in the DITA Open Toolkit distribution. Besides Apache FOP you can also use RenderX XEP or Antenna House for publishing. It's customization can be done either via a plugin or via a PDF customization folder: https://www.oxygenxml.com/doc/versions/17.1/ug-editor/index.html#topics/dit…. DITA to PDF using CSS. This open source DITA OT plugin was developed by Oxygen as an alternative to the default PDF publishing. It allows styling the DITA content using CSS and publishing to PDF using either Prince XML or Antenna House. Antenna House DITA OT plugin for producing PDF from DITA using Antenna House. There is also a DITA specialization plugin which allows you to set specific formatting attributes directly to DITA elements. The TopLeaf XML Publisher commercial product allows you to produce various outputs like PDF and EPUB from XML content. The application also has a visual PDF layout formatter, it comes also with a DITA OT plugin and has installation instructions for Oxygen:http://www.turnkey.com.au/tksweb/xmtp/webhelp_out/oxygen/install.html. Miramo, again a commercial solution which recently started developing support for DITA using a DITA OT plugin. Possibly user based DITA to PDF publishing will be free and server based production will require buying a license. Like TopLeaf, it also has a visual PDF layout designer. Adobe FrameMaker can also publish to PDF using its own solution. Now the question would be, why there are so many solutions available? In my opinion all these solutions are available because the default DITA to PDF output still requires quite a lot of XSLT skills in order to customize. Jarno Elovirta's PDF plugin generator covers some of the mainstream possible customizations but not all. What do you think? -- 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

4 3

Automatic Validation - in text mode, in Eclipse release of oXygen
by Echlin, Robert 09 Nov '15

09 Nov '15

Hi I have developed some schematron rules to apply to DITA content for our staff. We use the IXIASOFT CMS Client, which means that we are using oXygen inside of Eclipse. When I open a file in Author Mode, the schematron rules are applied automatically. Red and yellow underlines flag the items considered invalid by the Schematron rules. When I switch to editing the file in Text mode, the Schematron rules are not applied automatically. I have to manually run validation. We are behind in the IXIASOFT releases, so we are using Eclipse 3.5.2 and oXygen 16.1. Is there a setting I can change to fix this? Is this fixed in oXygen 17.1? Is it fixed in newer versions of Eclipse? All my very best, Rob -- Rob Echlin, Documentation Systems Architect, Wind River Office: 613-270-5796, Cell: 613-266-8311, Skype: rob.echlin.wr

2 5