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

set an XML Schema for a directory?
by Robert Koberg 30 Mar '09

30 Mar '09

Hi, I haven't used project mode much, but I just created a new project and imported a directory structure into it. One of the folders contains content files that are supposed to adhere to one XML Schema. I see the 'validate selection with...' which allows me to validate the entire directory -- which is great. However, when I bring up an invalid file I would like to have the editor know which schema to use (the one I validated the dir against) so the editor will give the element/attribute options without having to assign the schema each time. Make sense? Is this possible? best, -Rob

2 2

Format and Indent Problem
by Jeff Sese 02 Mar '09

02 Mar '09

Hi, As I have read on previous posts, oXygen classifies mixed content based on the current contents of an element, is this correct? If so, is it possible for oXygen to classify elements based on the declarations made in the DTD or Schema it is associated to? I know that the work around for this is to specify the pattern of elements that you want to preserve the whitespace in the preferences or to manually insert an xml:space="preserve" attributes for these elements, but if an XML is associated with a DTD or a Schema then you can tell whether whitespace in that element is ignorable or not. Currently what I've been doing is for every project I have to specify in the pattern listing all the mixed content elements that are defined in the DTD/Schema so that when I do a pretty print the whitespace is preserved and this method is very troublesome. Is there anymore workaround for this other than the ones I mentioned above? Or can this be considered as an added feature for a future version of the product? Thanks, Jeff

3 16

Adding export to HTML for the graphical representation of Relax NG Schema
by mozer 05 Jan '09

05 Jan '09

Dear, Is it possible to add a feature to export the graphical representation of Relax NG schema to HTML ? Regards, Xmlizer

2 3

RE: [oXygen-user] html does not allow namespace declaration on the rootelement [SEC=UNCLASSIFIED]
by John.Hockaday＠ga.gov.au 26 Nov '08

26 Nov '08

Hi Xmlizer, I believe that the official reference to XHTML is to a DTD such as: <?xml version="1.0" encoding="iso-8859-1" ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> ... </html> You should be able to use this format. John -----Original Message----- From: oxygen-user-bounces(a)oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of mozer Sent: Thursday, 3 July 2008 2:40 AM To: Oxygen User Subject: [oXygen-user] html does not allow namespace declaration on the rootelement Dear, with the following file <?xml version="1.0" encoding="UTF-8"?> <html xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/1999/xhtml"></html> I have the following error E [Xerces] Attribute "xmlns:xsd" must be declared for element type "html". Can you explain me how to workaround this ? Regards, Xmlizer

2 2

Feature Request for Content Completion with East Asian Text
by Christian Wittern 17 Nov '08

17 Nov '08

Hi there, We are using oXygen mainly to edit Chinese or Japanese text. In this case, words are not separated by whitespace. For a project we are having here, I am setting up snippets that should be inserted using code completion. However, Code Completion fires only after a whitespace character, so we have to input a spurious whitespace character to kick this off, which then has to be deleted again at some point. Hence my feature request: When doing a Code Completion, look at the character before the insertion point and fire if either there is a whitespace, or a character in the Unicode ranges for East Asian characters. This should be fairly easy to implement and have no negative impact on the current functionality. All the best, Christian -- Christian Wittern Institute for Research in Humanities, Kyoto University 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN

3 7

Re: [oXygen-user] Setting up catalogs
by Radu Coravu 04 Nov '08

04 Nov '08

Hi David, We'll probably have this fix available by Oxygen 9.3 (couple of days). When the fix will be available all you will have to do will be to add your catalog to the Oxygen catalogs list and the DITA Maps Manager topic references will be solved through the catalog. Regards, Radu -- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com David Linton wrote: >> I understand that you use URN's in topicref href's and you want when a >> map is opened in the DITA Maps Manager view to see correctly the links >> to the hrefs (solved by catalog) and of course when double clicking a >> link to open in the editor the real location solved by catalog. >> Indeed Oxygen does not yet solve by catalog the topic references >> presented in the DITA Maps Manager but we can work on this. >> Is my understanding correct? >> > > Yes, that's right. > > >> You also speak something about Oxygen ignoring catalog entries at >> validation. What kind of validation are you referring to? >> > > I don't know - that's just the phrase you used in the user guide, where you > distinguished "validation" from "transformation". I figured they were the only two processes > involved, but I guess that was wrong. > > >> Also, how have you modified the DITA-OT toolkit to allow the URN's to be >> resolved at transformation time? >> > > DITA-OT isn't happy with map files which aren't at the top level so I ended up preprocessing all the > links into a temporary directory with some XSL; a side-effect of that process is that topicref hrefs > get resolved before they get to DITA-OT. > > Before I did that, it worked fine to replace the <xslt> ant task in DITA-OT with one that used saxon with the > apache commons resolver. > > rgds > dave > . > > >> I understand that you have an xml catalog which solves the URN's to real >> locations. Can you send us a sample from it? >> > > I use "uriStartString" to save writing out all the URNs, although I'm aware that the URNs > aren't quite compliant with the RFC, but it's not caused any problems so far. > > > > <group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/style/MAIN/dita-ot/"> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:xsl/" rewritePrefix= "xsl/" /> > <rewriteURI uriStartString= "urn:quative.tv:dita:xsl/" rewritePrefix= "xsl/" /> > > <rewriteSystem systemIdStartString= "http://docs.quative.tv/dita/xsl/" rewritePrefix= "xsl/" /> > <rewriteURI uriStartString= "http://docs.quative.tv/dita/xsl/" rewritePrefix= "xsl/" /> > </group> > > <group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/style/MAIN/"> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:extensions/dtd/" rewritePrefix= "dtd/" /> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:apiref/dtd/" rewritePrefix= "dtd/" /> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:javaapiref/dtd/" rewritePrefix= "dtd/" /> > <rewriteSystem systemIdStartString= "urn:quative.tv:dita:dtd/" rewritePrefix= "dtd/" /> > > <rewriteSystem systemIdStartString= "urn:quative.tv:style:" rewritePrefix= "" /> > <rewriteURI uriStartString= "urn:quative.tv:style:" rewritePrefix= "" /> > > <rewriteSystem systemIdStartString= "http://docs.quative.tv/style/" rewritePrefix= "" /> > <rewriteURI uriStartString= "http://docs.quative.tv/style/" rewritePrefix= "" /> > </group> > > <group xml:base="/build/dlinton/tmp/generated/"> > <rewriteURI uriStartString= "urn:quative.tv:docs:generated/" rewritePrefix= "" /> > <rewriteURI uriStartString= "http://docs.quative.tv/generated/" rewritePrefix= "" /> > </group> > > <group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/content/MAIN/cca-ccom/"> > <rewriteURI uriStartString= "urn:quative.tv:docs:cca-ccom/" rewritePrefix= "" /> > <rewriteURI uriStartString= "http://docs.quative.tv/authored/cca-ccom/" rewritePrefix= "" /> > </group> > > <group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/content/MAIN/"> > <rewriteURI uriStartString= "urn:quative.tv:docs:" rewritePrefix= "" /> > <rewriteURI uriStartString= "urn:quative.tv/docs/" rewritePrefix= "" /> > <rewriteURI uriStartString= "http://docs.quative.tv/" rewritePrefix= "" /> > </group> > > > > This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, discussion or disclosure by others is strictly prohibited. If you are not the intended recipient of this email, please contact the sender by return email and delete all copies of this email and its attachments, if any. >

3 4

Fixed-width font
by Florent Georges 13 Oct '08

13 Oct '08

Hi I looked for in the "Preferences" window, but found nothing. Is it possible to tell the editor to use a fixed-width font? Regards, --drkm

6 12

Wildcards in validation scenario associations?
by Jan Nylund 06 Oct '08

06 Oct '08

Hello! I would like to use wildcards to associate all xsl files in a certain folder to be validated starting form another xsl file. (the files are only used as imported from that certain place) Looking on how the project file works, if I associate it manually and save the project file, I get an added "<String xml:space="preserve">validation.scenario.associations</String>" with the actual file path added. If I simply modify the file path to contain for example "*.xsl" it doesn't automatically associate them, so it seems this solution did not work. Am I missing something or is this feature currently not available? Br, Jan -- Jan Nylund Senior System Designer Citec Information Oy Ab

2 1

Scenario editor: doc param and meta-stylesheet scenario
by Florent Georges 03 Oct '08

03 Oct '08

Hi I have the following stylesheet parameter in one of my stylesheets (note its type): <xsl:param name="initial" as="document-node()"/> I don't find how I can set its value in the scenario editor. Is it possible or do I have to create a driver stylesheet getting a filename and parsing it to set this parameter? (really, I'd like to avoid that) As a slide question, this stylesheet is actually a generated stylesheet. But I didn't find a way in the scenario editor to support meta-stylesheet (a double transformation that first generates the stylesheet using the meta-stylesheet, then transform a document using this generated stylesheet.) For now I have each time to launch two scenarios one right after the other. But maybe I just didn't find the right way to achieve that? Best regards, --drkm, looking forward to XProc as a scenario language ;-)

3 3

XPath over sets of files
by Wendell Piez 01 Oct '08

01 Oct '08

Hi, I know about the Find/Replace in Files option on the context menu in the Project View. Run a string (or regular expression) search through a set of files collected in a folder in your project. Cool. How about an XPath option that would work the same way? Currently I usually write myself a little Schematron to locate particular nodes, which isn't a big deal. But it would be nice not to have to when the search can be expressed simply in a one-line XPath. Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================

4 6