September 2010 - oXygen-user - www.oxygenxml.com

Questions about links
by Stephen Matlock 09 Sep '10

09 Sep '10

1. I have the following <p> tag with a linked PDF: <p> Please open the following document: <xref href="https://fileserver.com/documents/BXMLGuide.pdf">The Beginner's Guide to All Things XML</xref>. </p> (The URI for this is different in the actual document). I can use this very same URI and open this document. This link works in other documents. But when I transform this DITA content using the Legacy PDF transform, the link, while underlined in blue and apparently "clickable," does not actually open the document. 2. I have the following tag for an entry later in the document: See <xref href="C_setup_my_account.dita#setupmyaccount">Set Up Your Account</xref> for more information I can open this link within Oxygen - it opens the 'peer' file just fine. It's part of the same DITAMAP and when I transform to PDF, this topic is part of the PDF. But the link, while Blue Italic, is not clickable. 3. I remember (I think) that when I transformed to PDF using the Legacy OT transform that it also put the page number as part of the link for a link within the same document. Is this still possible?

1 1

Re: [oXygen-user] WebHelp output: graphics put in subfolder [CAUSE FOUND]
by Yves Barbion 07 Sep '10

07 Sep '10

Hi Radu I have found the cause of the problem: some topics have a link to a topic which is "outside the scope of the input dita/map directory", for example: <related-links status = "new"> <link href="../layout.xml#aw1140092"> <linktext>Layout.</linktext> </link></related-links></task> The DITA OT then gives me this warning: [pipeline] [DOTJ036W][WARN] The file "C:\temp\oxygen_webhelp_test\DITA\layout.xml" referenced by "C:\temp\oxygen_webhelp_test\DITA\prototype\to_create_a_task_topic.xml" is outside the scope of the input dita/map directory. If you do not want to see the warning message,please use the Ant parameter 'outer.control', and set the value as "quiet".Or,you can move the referenced file The graphics are then put in a subfolder. I will send Support a small prototype. Thank you in advance for your help. Kind regards -- Yves Barbion www.scripto.nu

3 2

Controlling details of xref creation in DITA editing
by Eliot Kimber 06 Sep '10

06 Sep '10

For DITA documents, if I create a new xref using the cross reference dialog, the resulting xref element includes the title of the target as literal next. I never want this but I didn't see a preference to control this behavior. Is there one? Thanks, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.reallysi.com www.rsuitecms.com

2 2

Turn Off Mouseover Help in Elements Pane?
by Brian Rice 06 Sep '10

06 Sep '10

I'm using oXygen 11.2 on XP sp 3. The schema I'm working with has some rather extensive annotations which, when displayed as mouse-over help in the elements pane, obscure my view of the other elements and get in the way. I've searched through the the Preferences menus looking for a way to turn this off, if possible. Or at least lengthen the time before it appears. I haven't found it if it's there nor could I find this in the archives. Is there some way to at best turn off this feature or lengthen the time delay before it shows up? Thanks, -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

2 1

WebHelp output: graphics put in subfolder
by Yves Barbion 06 Sep '10

06 Sep '10

Hi group (and Radu) I've got my ditamap and my topics in a folder named "doc"; my images are in a subfolder named "graphics". When I use oXygen XML Editor to generate webhelp from my ditamap, I see that the link to my images is broken, because oXygen XML Editor seems to copy my images to a subfolder: "out/doc/graphics" (where it should be "out/graphics". Is anyone else seeing this? Thanks -- Yves Barbion www.scripto.nu

2 1

Xproc, XQuery and XForms workshops at TEI MM2010, Zadar, Croatia
by Christian Wittern 05 Sep '10

05 Sep '10

Dear Oxygen users, This is to alert you to the fact that a number of workshops of potential interest to you are held this November in Zadar, Croatia as part of the TEI members meeting and conference TEI MM 2010: * Pipeline-processing of TEI-XML documents with XProc (Norm Walsh) [Nov. 8 and Nov 9 til noon] * Introduction to XQuery as a tool for TEI users (C. M. Sperberg-McQueen) [Nov. 8 and Nov 9 til noon] * Building interactive XML tools with XForms (C. M. Sperberg-McQueen) [Nov. 9 afternoon and Nov. 10] In addition, there are workshops on ODD (a common layer of abstraction for defining schemas in the RelaxNG, XML Schema and DTD languages) and other TEI related topics *Early bird registration with a 20% discount off the regular price ends on Sept. 8!!* Register for the workshops at the TEI webshop (http://tei-shop.org) Further discounts are available for TEI members and subscribers. Here is more information about these workshops, but see also http://ling.unizd.hr/~tei2010/workshops/index.en.html * Pipeline-processing of TEI-XML documents with XProc (Norm Walsh) This hands-on workshop will explain XProc: An XML Pipeline Language in detail. We'll begin with a complete introduction to the language and its features, followed by examples and hands-on exercises to explore its features. Participants are encouraged to bring sample documents and processing applications for workshop discussion. Participants should be familiar with XML and comfortable with XML technologies such as XSLT and XInclude. Prior exposure to XProc isn't a requirement. In order to run the exercises,participants will need a laptop with Java installed. Norman Walsh is a Lead Engineer at MarkLogic Corporation where he works with the Application Services team. Norm is also an active participant in a number of standards efforts worldwide: he is chair of the XML Processing Model Working Group at the W3C where he is also co-chair of the XML Core Working Group. At OASIS, he is chair of the DocBook Technical Committee. With more than a decade of industry experience, Norm is well known for his work on DocBook and a wide range of open source projects. He is the author of _DocBook 5: The Definitive Guide_. * Introduction to XQuery as a tool for TEI users (C. M. Sperberg-McQueen) This tutorial will give participants a solid introduction to XQuery, a query and transformation language for XML documents. XQuery can be used to translate XML-tagged data into HTML, to modify the tagging of data, and (of course) to search large bodies of XML material. Many XML processing tasks which are possible but inconvenient in Java, C, or Python are much more convenient in XQuery. Hands-on exercises will give students experience actually writing queries for the interrogation and transformation of XML-tagged data. Participants should have good knowledge of XML syntax and XPath 1.0; knowledge of XSLT 1.0 is helpful but not a prerequisite. Familiarity with basic programming concepts (input, output, types, flow of control will be helpful (or alternatively, the ability to confront new concepts without fear). * Building interactive XML tools with XForms (C. M. Sperberg-McQueen) This workshop introduces XForms as a technology for building special-purposes XML editors with limited functionality and correspondingly simple user interfaces. XForms is built on the model / view / controller idiom, in which the 'model' is a set of XML documents, the 'view' is specified using XHTML and XForms widgets, and the 'controller' takes the form of declarative links between widgets and elements or attributes in the XML documents. With XForms, projects can develop vocabulary- and task-specific editors which require less training and provide better task-specific support than full XML editors; it is thus easier to allow domain experts to examine and modify XML encoding, and routine tasks can be performed more quickly and reliably. Hands-on exercises will be provided. Topics include: design goals of XForms; the XForms processing model; padded-cell editors; XForms widgets; datatypes; auto-calculation; validation in the client; selective display; dynamic labels and multi-lingual interfaces; tabbed interfaces for multi-part forms; deployment issues. Participants should have some knowledge of XHTML markup and XPath and be comfortable editing XML documents; programming experience is not required. Michael Sperberg-McQueen is an independent consultant specializing in problems of long-term preservation and access for scholarly, scientific, public, and cultural-heritage information. He was one of the co-editors of TEI P1, P2, and P3, of the W3C XML 1.0 specification, and of the W3C XML Schema Definition Language (XSD) 1.1 specification. Christian Wittern, Chair, International Program Committee, TEI MM 2010 -- Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN

1 0

puzzling multi-schema behavior
by Gary Gapinski 03 Sep '10

03 Sep '10

Using <oXygen/> XML Editor 11.2, build 2010080212. Load http://scap.nist.gov/use-case/cyberscope/cyberscope-auto-feed-example-20100…. An explicit validation results in several Xerces errors in xAL.xsd and xNL.xsd. Is this due to actual errors in the schemata, or due to <oXygen/> validation settings? Regards, Gary

3 2

SearchJS transformation?
by Yves Barbion 02 Sep '10

02 Sep '10

Hi group (and Radu) I have just discovered the TocJS transformation, which gives me a nice "Contents" pane in my HTML output. Are there any plans for a "SearchJS" transformation which works in a similar way? This would give us a "webhelp-ish" output of a DITA map. Thanks. -- Yves Barbion www.scripto.nu

3 6

Preventing oXygen XML Author/Editor from overwriting commonltr.css?
by Yves Barbion 01 Sep '10

01 Sep '10

Hi group I generate XHTML from my ditamap. In this process, the commonltr.css file in the OXYGEN_INSTALL_DIR\frameworks\dita\DITA-OT\resource\ folder gets copied to the output directory. However, I'd like to use a customized commonltr.css file in the output folder, but keep the original commonltr.css file in the OXYGEN_INSTALL_DIR\frameworks\dita\DITA-OT\resource\ folder. Is there an elegant way to do this? When I regenerate output, I see that the commonltr.css file in the output folder is overwritten. Thanks. -- Yves Barbion www.scripto.nu

2 2