- oXygen-user - www.oxygenxml.com

Cannot seem to get the "Open Maps in editor with resolved topic" working
by Nathan 11 Feb '14

11 Feb '14

Hi, I am developing a framework which is extending the existing DITA framework. The new framework is distributed via our source control and so it needs to be pointed to via the "Preferences > Document Type Association > Location > Custom". I am finding that when I open a ditamap using this extended framework (and yes, the correct associations have been made in the "Association rules"), I cannot seem to get the "Open Maps in editor with resolved topic" option working. I have checked that the file is not locked and that I am able to do other operations (like create reusable content etc). What am I doing wrong? Any help would be greatly appreciated. Thanks, Nathan

1 0

Using the existing Lucene index
by Nathan 10 Feb '14

10 Feb '14

Hi, I am not sure if this should go in the SDK mailing list or in this one, so I thought I would start here. I was wondering if there is a way to find out what all are indexed by the Lucene indexing operation when using Open/Find Resource? Where am I going with this? I am trying to build some customizations which would: - Find out all the ditamaps that the active document is being used in - I understand I can walk down the ditamap tree and find this out but if anything in this regard is already stored in the index, I would be very interested in getting it from there - Find all references and conrefs which are pointing to a particular selection (this is more so for inline conrefs rather than conreffed file) - I did read somewhere that this is not being indexed, but I thought it better to ask. If there is any existing way to do any of the operations above, I am would be really eager to know. Thanks, Nathan

2 1

unsibscribe
by Khaled Aly 08 Feb '14

08 Feb '14

unsibscribe

1 0

issue with replace in multiple files
by Peter Stadler 05 Feb '14

05 Feb '14

Dear list, I’m facing an issue with the current oXygen 15.2 for Mac (10.9.1, German locale) and wonder whether it’s me or Oxygen: When doing a search/replace on multiple XML files oxygen stalls (progress dialog remains on one file forever) on specific files. These files have in common that they contain characters from higher Unicode ranges (musical symbols) and when opened oXygen prompts for „bidirectional modus“. Worst thing though, when canceling the operation the file at which oxygen stalled will be empty. Hope my report is meaningful and will help to solve the issue, Best Peter -- Peter Stadler Carl-Maria-von-Weber-Gesamtausgabe Arbeitsstelle Detmold Gartenstr. 20 D-32756 Detmold Tel. +49 5231 975-665 Fax: +49 5231 975-668 stadler at weber-gesamtausgabe.de www.weber-gesamtausgabe.de

2 1

Distributing profiling attributes and profiling condition sets within a framework
by Nathan 05 Feb '14

05 Feb '14

Hi, I would like to distribute profiling attributes and profiling condition sets but preferably do so via a framework instead of the project option. Is there any way to do this? To define the use case, I would like to deploy a default baseline setup which could be updated via source control without the need for a merge if authors customize their own projects. If it is not possible to distribute profiling conditions via framework, would it be possible to use xlink to do this at the project level. I would be eager to know what others are doing in this regard. Thanks! Nathan

4 4

[ann] oXygen XML Editor 15.2
by George Cristian Bina 04 Feb '14

04 Feb '14

Hi all, I am happy to announce that a new version of oXygen XML Editor, Author and Developer is available from our website http://www.oxygenxml.com You can find the release notes and details about the new additions at http://www.oxygenxml.com/whatisnew15.2.html Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

3 3

Difference between xs:redefine and xs:override in XML schema 1.1
by Olumide 03 Feb '14

03 Feb '14

Hello List, Would someone kindly explain the difference between <xs::redefine> and <xs::override> in XML schema 1.1. I've got two books on XML Schema in front of me and I still can't tell the difference. The only thing that I'm sure of is that both are pervasive and that <xs::redefine> is deprecated. Regards, - Olumide

2 1

[Ann] New maintenance build available for oXygen 15.2 (2014013017)
by Oxygen XML Editor Support 03 Feb '14

03 Feb '14

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

Working with Subject Scheme Maps as Nested Lists
by Eliot Kimber 31 Jan '14

31 Jan '14

I'm experimenting with using subject scheme maps to capture outlines of subjects as part of some training planning I'm doing. To facilitate this I've whipped up a little CSS style sheet that renders the subject definitions as a bulleted list items. However, I don't get any collapse/expand handles in the edit view--I would really like to be able to expand and collapse the list in the main editor window (rather than using the outline view). Is there a way to do this through the CSS? Here is the CSS as I've got it so far: /* CSS to show a subject scheme map as nested lists*/ subjectdef { list-style-type: disc; display: block; } subjectdef > topicmeta { display: list-item; margin-left: 12pt; margin-top: 12pt; } subjectdef > subjectdef > topicmeta { display: list-item; margin-left: 24pt; } subjectdef > subjectdef > subjectdef > topicmeta { display: list-item; margin-left: 36pt; } subjectdef > subjectdef > subjectdef > subjectdef > topicmeta { display: list-item; margin-left: 48pt; } subjectdef > subjectdef > subjectdef > subjectdef > subjectdef > topicmeta { display: list-item; margin-left: 60pt; } shortdesc { display: block; margin-top: 1em; margin-left: 12pt; } /* End of CSS */ Thanks, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com <http://contrext.com/> -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

3 6

Fwd: Toggling @keyref with Tags Display Mode
by Wendell Piez 28 Jan '14

28 Jan '14

I'm always forgetting to reply to list ... ---------- Forwarded message ---------- From: Wendell Piez <wapiez(a)wendellpiez.com> Date: Tue, Jan 28, 2014 at 9:53 AM Subject: Re: [oXygen-user] Toggling @keyref with Tags Display Mode To: Roger Sheen <infotexture(a)gmail.com> Hi Roger, To bind this behavior to "No Tags Mode" raises all kinds of questions regarding exactly which behaviors are toggled when. Keep in mind that Tags Display functionality applies to all document types, not just DITA. Much simpler, and cleaner layering, is to deploy another CSS stylesheet alongside the generic one, with whatever customizations you want. oXygen lets you have as many CSS displays to choose from as you wish to configure. Users can switch between them with a pull-down menu. You can do this yourself. Your new CSS can import the old one and simply override where necessary. I can imagine other solutions, such as designating an attribute flag in the document that toggles display behavior. Using oXygen's forms widgetry, one could present this as a radio button widget (for example) and let the user toggle from inside the document. But this would mean both extending DITA to support it, and arguably crossing an architectural line, since the document is now being asked to carry display semantics specifically for the editing environment. And this raises questions for document interchange, etc. etc. I'm sure there are other ideas I haven't thought of. :-) Cheers, Wendell On Tue, Jan 28, 2014 at 7:33 AM, Roger Sheen <infotexture(a)gmail.com> wrote: > While working on Author mode CSS customizations today, I was looking for > a way to remove the @keyref values that are automatically displayed > before *keyword* elements when editing DITA topics. > > The content in this project makes heavy use of keywords, and many > authors find the extra text distracting. > > I found the relevant rule on line 1053 of the default `topic.css` file > and added an override in my custom CSS to remove `"[" attr(keyref) "]"` > from the inserted content (but still display the link). > > This solution works, but I was thinking it might be better if this could > be toggled along with the *Tags display mode*. When set to *No Tags*, it > would be nice if these values were hidden. I would expect them to be > displayed in other modes that progressively disclose additional visual > cues. > > Any thoughts? > > Regards, > > Roger > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^ -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

2 1