May 2013 - oXygen-user - www.oxygenxml.com

[ANN] Syncro Soft at Congility – Content Agility 2013 - 26-27 June - Gatwick (London) UK
by Sarah Draper 09 May '13

09 May '13

Hello, We are happy to announce that we are Sponsors of Congility - Content Agility 2013. This is a unique event which brings together Content Strategy, Structured Content and Component CMS all under one roof. About Congility Congility (formerly X-Pubs) delivers pragmatic, focused events, on and offline, for Managers, Team Leaders and Content Professionals. Content has agility when it is meaningful, optimized for business and user goals, reusable, portable and accessible. Congility is more diverse and accessible to attendees of various backgrounds than ever before. Content Agility 2013 will cover more than just tools and technologies. Attendees will be able to extend their knowledge of the world of dynamic, future-proof delivery across multiple audience and device profiles. Learn how to better create, manage and deliver content, enhance user experience and customer satisfaction by visiting our stand. Use our special registration code SYS2013 to receive up to 20% discount, subject to the date of booking - visit www.congility.com This offer cannot be used in conjunction with any other offers. We look forward to meeting you there! Syncro Soft Ltd www.oxygenxml.com support(a)oxygenxml.com channelsales(a)oxygenxml.com +44 (0)7890 371908 =============================

1 0

Re: [oXygen-user] Live XSLT/XProc message output?
by Jostein Austvik Jacobsen 08 May '13

08 May '13

Ok great, thanks. Jostein On 8 May 2013 09:40, Mircea Enachescu <mircea(a)sync.ro> wrote: > Hello Jostein, > > The requested feature is still under our attention since we had more > requests for this. > We plan to add this feature in the future but I cannot make a commitment > for the exact release version. > > Regards, > Mircea. > > > On 06.05.2013 10:09, Jostein Austvik Jacobsen wrote: > > Have you had any more requests for this? I still don't have a way to > determine the progress/state of my XProc scripts. Is there maybe a hacky > way of enabling live logging to the console? > > > Jostein > > > On 10 September 2012 14:27, Mircea Enachescu <mircea(a)oxygenxml.com> wrote: > >> Hello Jostein, >> >> Thank you for this suggestion, we will take it into account for our >> future releases. >> >> Regards, >> Mircea. >> >> -- >> Enachescu Mircea >> Syncro Soft | oXygen XML >> >> Tel: +1-650-352-1250 ext.212 >> Fax: +40-251-461482support@oxygenxml.comhttp://www.oxygenxml.com >> >> >> On 10.09.2012 11:34, Jostein Austvik Jacobsen wrote: >> >> When running XProc scripts and/or XSLT transformations, the cx:message >> and xsl:message outputs appear only after the script/transformation is >> complete. I would like to view the messages while the script/transformation >> is running since they can take quite some time to run and the messages >> indicates the progress. Is it possible to enable some kind of "live message >> output mode"? >> >> Jostein >> >> >> _______________________________________________ >> oXygen-user mailing listoXygen-user@oxygenxml.comhttp://www.oxygenxml.com/mailman/listinfo/oxygen-user >> >> >> -- >> Enachescu Mircea, Product Architect >> Syncro Soft | oXygen XML >> >> Tel: +1-650-352-1250 ext.212 >> Fax: +40-251-461482support@oxygenxml.comhttp://www.oxygenxml.com >> >> >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user >> >> > > -- > Enachescu Mircea, Product Architect > Syncro Soft | oXygen XML > > Tel: +1-650-352-1250 ext.212 > Fax: +40-251-461482support@oxygenxml.comhttp://www.oxygenxml.com > >

1 0

Unable to get DITA Docs to Validate: Can't Figure out Why Not
by Eliot Kimber 07 May '13

07 May '13

I'm helping a colleague set up an Oxygen environment. For reasons I can't determine, it is failing to resolve any DITA-related DTDs. I did find that the master frameworks catalog did not have a reference to the frameworks/dita/catalog.xml. I added that reference, verified that it was correct and that it eventually got me to the catalog-dita.xml catalog, but even after restarting Oxygen, it is still unable to validate any DITA documents. I compared the various catalog-related settings to my own environment and couldn't see any obvious differences. Any idea what I might have overlooked? It appears that when Oxygen was initially installed DITA was not selected as a framework, but all the DITA-related settings appear to otherwise be in place. Other than the entry in the master catalog, is there some other setting I might have overlooked? Thanks, Eliot -- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/

2 1

Live XSLT/XProc message output?
by Jostein Austvik Jacobsen 06 May '13

06 May '13

When running XProc scripts and/or XSLT transformations, the cx:message and xsl:message outputs appear only after the script/transformation is complete. I would like to view the messages while the script/transformation is running since they can take quite some time to run and the messages indicates the progress. Is it possible to enable some kind of "live message output mode"? Jostein

2 2

content completion not working for idref with XIncludes
by Bob Stayton 02 May '13

02 May '13

I'm trying to create a set of modular documents using XInclude to assemble them (using a custom XSD). During editing, it is vital that IDREFs resolve to an ID value to ensure data integrity. To make that easier, I want Content Completion to work when inserting an attribute value of type IDREF. I have followed the directions in Oxygen Help to set this up. I am able to validate each module individually and the master file, regardless of where the id values reside, showing that the ID values are available during the validation step. But I cannot get the Content Completion to work for the IDREFs. When I enter an attribute of type IDREF and hit Ctrl-Space, there is no list, not even ID values from the current module. Details: Oxygen 14.2 Text mode Custom xsd schema using xs:ID and xs:IDREF attribute types. Enabled Master File Support for the project. Project set up with top-level file listed under Master Files in the Project view. Validation scenario created and assigned to all files has its "URL of the file to validate" set to the Master file. What's missing that allows the IDs be validated but the Content Completion fail to work? Bob Stayton Sagehill Enterprises bobs(a)sagehill.net

2 1

Opening SVG on Mac
by Reaves, Timothy 02 May '13

02 May '13

Would you please added this to the supported doc types, so I do not need to keep manually selecting what to open an SVG with?

2 3

XML colors
by Reaves, Timothy 02 May '13

02 May '13

I prefer a black background, so have changed my colors accordingly. Now, in my XML documents, things like '+' are black on black, and I can seem to find no way to change this. Is this a bug, or am I overlooking something?

2 2

Difference between incomplete and incorrect
by Mark Baker 02 May '13

02 May '13

I'm writing a book in DocBook. It is the first time I have used oXygen to write in a schema that I did not create myself, and I am therefore relying a lot more than I normally do on the cues that the editor gives me. One of those cues are the validation errors. The problem is, they are all signaled with RED. That makes sense if you have entered something illegal, but most of the time they appear because you have begun to create a complex structure and that structure is currently incomplete. From an author's point of view, that's not an error, I just haven't finished yet. Where oXygen can generate the whole structure, it does, so no error is shown, but there are many cases where it can't because what is required is one of one or more options. In these cases, the structured does not become legal until the author adds additional elements. The thing is, RED means stop, but the author, in this case should continue. RED means you did something wrong, but in these cases, the author simply hasn't finished yet. I find the editor is constantly slowing me down by throwing up these errors that I have to analyse each time to determine if I need to go on or if I need to back up. When I design a schema, I try to avoid creating these kinds of structures, for just this reason, but sometimes they cannot be avoided. My question is, is there a way, and do folks think it is desirable, to present a different cue for incomplete structures than for erroneous ones. At minimum, use a different color, such as yellow, for incomplete. Ideally, find some way to indicate that the author is on the right track and needs to continue. Thoughts? Mark

6 7