- oXygen-user - www.oxygenxml.com

Webhelp: Integrating Google Translation?
by Franz-Josef Knelangen 27 Apr '18

27 Apr '18

Hi there, did anyone create a plug-in that integrates Google Translation with Webhelp? ePublisher’s “Reverb” does this, and it’s kind of nice to provide some kind of content representation of the information you present in your reader’s mother tongue w/o having to provide a real translation. Greetings, Franz-Josef ________________________________ AKG Software Consulting GmbH Franz-Josef Knelangen Uhlandstraße 12 79423 Heitersheim Germany Tel.: +49 (0)7634 5612-611 Fax: +49 (0)7634 5612-300 E-Mail: fjk(a)akgsoftware.de Internet: www.akgsoftware.de<http://www.akgsoftware.de> Geschäftsführer: Dipl.-Ing. Artur K. Günther, Dipl.-Ing. Arno Brüggemann, Dipl.-Ing. (FH) Bernhard Feser, Dipl.-Ing. Jens Günther Sitz der Gesellschaft: Heitersheim, HRB 310383 (Amtsgericht Freiburg)

2 1

[Ann] New maintenance build available for oXygen 20.0 (2018042410)
by Adrian Buza 26 Apr '18

26 Apr '18

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

A maven plugin to keep your Oxygen .xpr poject file sorted
by cmarchand＠oxiane.com 26 Apr '18

26 Apr '18

When oXygen project files are commited in SCM, and many developers create various scenarios, merging xpr file can be a nightmare. Editions Lefebvre-Sarrut has released a maven plugin that keep your project file entries sorted, and simplifies the merge - you still have to resolve conflicts, but that's much easier. https://github.com/ELSGestion/oxygen-pjt-beautifier-maven-plugin Best, Christophe

1 0

Validation error of unknown origin
by Bernhard Kleine 25 Apr '18

25 Apr '18

Hi, (Oxygen 19.1) This organisation raises errors for the <para> entries after <sect3>. The error is : element "para" not allowed here; expected the element end-tag or element "bibliography", "glossary", "index", "sect3", "simplesect", "toc" or "xi:include" The one before sect3 is not touched, but those after. Could you please explain the rules why these <para> after a <sect3> are not allowed? Thanks a lot 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 1

<Variables> in DITA documentation
by Franz-Josef Knelangen 25 Apr '18

25 Apr '18

Hi there, In our documentation we use something like <installation folder> or <project folder> and put these into file paths, f. e. <project folder>\pipe\sewer.s3db If I surround this with <filepath> markup, oXygen changes the 1st angle bracket of “<project folder>” to “<project folder>” to save the structure. In Author mode, you don’t realize this, only when trying to Search&Replace <installation folder> with <program folder> you don’t find all occurences and wonder why. I see that this has to be changed by oXygen. Is there some advice / best practice to deal with this kind of source text? At the moment, I can only think of putting this “variable” in a <varname> element inside <filepath> without writing the angle brackets and defining a CSS rule for /filepath/varname to surround it with brackets in the output. Any other ideas? TIA and Greetings from Germany, Franz-Josef ________________________________ AKG Software Consulting GmbH Franz-Josef Knelangen Uhlandstraße 12 79423 Heitersheim Germany Tel.: +49 (0)7634 5612-611 Fax: +49 (0)7634 5612-300 E-Mail: fjk(a)akgsoftware.de Internet: www.akgsoftware.de<http://www.akgsoftware.de> Geschäftsführer: Dipl.-Ing. Artur K. Günther, Dipl.-Ing. Arno Brüggemann, Dipl.-Ing. (FH) Bernhard Feser, Dipl.-Ing. Jens Günther Sitz der Gesellschaft: Heitersheim, HRB 310383 (Amtsgericht Freiburg)

3 2

[ANN] oxex - An oXygen project file to simplify common tasks in eXist app development
by Joe Wicentowski 21 Apr '18

21 Apr '18

Hi all, For anyone who commonly uses oXygen to work on code or data that you keep on the filesystem and upload to eXist, I posted an oXygen project file with some associated files to GitHub; once you open the project file, your External Tools menu will be populated with some tools that aid in tasks like uploading from the filesystem to the database, deploying an app to the database, etc. It assumes some conventions that are common in the eXist community for app development, such as assuming that files are uploaded to a sub-collection of /db/apps, using ant for packaging and deployment of .xar packages, etc. I adapted this from a project that I developed for my colleagues at work to speed some common tasks. Occasionally when I've shown this system to others they asked if I could release it for more general use. This is that effort. I'd welcome feedback and suggestions here or in the issue tracker. Joe

1 1

Tight Integration Makes for a Seamless Workflow Cycle
by Rik Page 16 Apr '18

16 Apr '18

Join Oxygen (Syncro Soft) and XDocs (Bluestream) for a free co-hosted webinar where we will show how tight integration between two leading systems can bring tangible benefits to organisations throughout the entire content lifecycle. Time and Date: Wed, May 16, 2018 6:00 PM - 7:00 PM EEST Synopsis Technical content goes through distinct phases: creation, review, release management, and publishing with the cycle repeated for the next release. At each of these key phases, tight integration between Bluestream's XDocs Component Content Management System (CCMS) and Oxygen XML products from Syncro Soft brings unrivalled control and functionality. Register at: https://register.gotowebinar.com/register/2795153561362610177 Rik Rik Page Director of Sales and Marketing rikp(a)bluestream.com +44 (0)79 8013 0260 skype: rik.page www.bluestream.com <http://www.bluestream.com/> --- This email has been checked for viruses by AVG. http://www.avg.com

1 0

DITA & Author 17.1: Displaying topic titles in Editor view
by Kristen James Eberlein 12 Apr '18

12 Apr '18

My client is using oXygen XML Author 17.1 and the SDL Authoring Bridge. While topic titles are displayed when a DITA map is open in the DITA Maps Manager view, they are not displayed in the Editor view. Is there a configuration option to enable this? I seem to remember one, but it might be in later versions of oXygen. Many thanks. -- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype)

2 2

Update element on save?
by David Levy 12 Apr '18

12 Apr '18

The current discussion "When a <fig> is inserted, it should contain a <title> element" prompts me to ask what I'm sure is a trivial question. I am using Oxygen to edit XML in text mode. I would like an XML element <dateUpdated> to be updated automatically on save. I am aware of the of the ${date(pattern)} editor variable, but don't know how to trigger an action on the save event or indeed what type of code can be run once the event is detected. The online example <https://www.oxygenxml.com/doc/versions/20.0/ug-editorEclipse/topics/api_faq…> seemed to be in a DITA context and require the Plugins SDK, neither of which I'm familiar with. With thanks, David Levy

3 3

Configuration: When a <fig> is inserted, it should contain a <title> element
by Kristen James Eberlein 12 Apr '18

12 Apr '18

How can I configure this in oXygen Author 17.1? I am using a framework. Thanks. -- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype)

3 5