- oXygen-user - www.oxygenxml.com

"content is not allowed in prolog" using Oxygen for MXML files
by Joshua Noble 01 Jun '06

01 Jun '06

I'm trying to use Oxygen to edit MXML files (Macromedia Flex). Everything works fine except that this error always appears: content is not allowed in prolog. What's up with this? Here's the line it chokes on: <?xml version="1.0" encoding="utf-8"?> This is the way all Flex files start and there don't seem to be any problems there. Anybody know what's up? -- Joshua Noble jnoble(a)mindseye.com 617-350-0339 x 33 aim: METProfessor -----------------

6 5

Help on XForms validation and auto-completion
by Paul Everitt 29 May '06

29 May '06

First, my apologies: I know that this has been discussed elsewhere, and I know most of the pieces, but I can't seem to get the entire assembly working. I'm thus appealing for help. Here's my goal: I'm trying to author XHTML+XForms documents. I would like to validate them and preferably have autocompletion. At this stage, I'm not interested in custom XSD schemas in my XForms instances. I followed the help here: http://www.oxygenxml.com/pipermail/oxygen-user/2005-July/000518.html http://groups.yahoo.com/group/rng-users/message/432 ...and I have XHTML 2 validation/completion working. I *thought* that XHTML2 would give me XForms and XML Events. Alas, here's the xhtml2.rng snippet: <x:h2>XForms module</x:h2> <x:p>To-Do: work out integration of XForms</x:p>  So no dice. I then went on a day-long Google hunt, learning more about namespace routing languages etc. than I could possibly have wanted to know. I tried numerous iterations of numerous schemas for numerous specs. Next, I reviewed the oXygen mailing list archives and forum and found this: http://www.oxygenxml.com/forum/ftopic1769.html However, the example there didn't work for me. Meaning, I could put <xf:fake/> in my docs and it would still validate. I'd really be interested to hear that someone got XForms plus any flavor of XHTML working in oXygen. By working, I mean correct validation and autocompletion. I don't particularly care if it is XHTML 1 or 2, RNG or XSD or NRL, or what version of the spec is used. If anybody has a tarball containing an example document and the pile of schema docs it needed, I would be thrilled. All in all, either this stuff is hard or I'm pretty dumb. --Paul

3 7

RE: [docbook-apps] Olinking and Chunked HTML Transformations
by Ray Miller 02 May '06

02 May '06

>> Yes, it should, and it does why I test it with the html/chunk.xsl stylesheet. Are you using a customization layer with the chunking stylesheet? If so, you have to construct it carefully to get the import sequence right. If you don't, then you get a mix of chunked and non-chunked behavior, and I suspect that is what happened in your target.db file. See: http://www.sagehill.net/docbookxsl/ChunkingCustomization.html If you were following those guidelines, then something else is going on that will require more information. << Commented out all customizations; issues unchanged. For some yet unknown reason when utilizing oXygen (eclipse plugin) on the Linux side, the extended characters €œ<text>€� to not appear surrounding the section text of <xreftext>, Windows side only; will resolve on the oXygen list. Using UTF-8 encoding. The <i> tags persist at the chapter <xref> sections surrounding chapter text. Also <span class="trademark"/> appears in the map within the <ttl> element (just began using the trademark element in a section element). Lastly, when the aforementioned tags are deleted, the olinkdb.xml map validates on the Linux side and subsequent HTML transformations behave as expected. From the Windows side, validation complains “Invalid byte 1 of 1-byte UTF-8 sequence.” Again, this issue is probably best addressed on the oXygen list but any help would be appreciated. Using docbook-rng-5.0b5, docbook-xsl-snapshot (4/30/06), oxygen-7.1.0 (eclipse-3.1.2 plugin), saxon-6.5.5 Ray

2 1

Controlling the style of generated schema documentation
by Christopher Smith 07 Apr '06

07 Apr '06

Hi there, I was wondering if there is a place in the oxygen preferences, or a stylesheet, that is used when generating the schema documentation. I'd like to be able to change the default colors (for instance) used for the generated documentation. I noticed that there is CSS information in the head of the generated documentation, but I was wondering if I can change this for all documentation that I generate, without needed to resort to post- generation editing or scripting. Thanks, -- Chris

2 2

assistance for associating an XML document with a stylesheet?
by Lars Huttar 05 Apr '06

05 Apr '06

Hello, I was leading a course on XML, XSLT and related technologies a few weeks ago, and a question came up that has occurred to me sometimes: Oxygen offers automated assistance for associating an XML document with a DTD or Schema, inserting the appropriate declaration into the XML document. Can it do the same for associating an XML document with a stylesheet? E.g. I would like to insert <?xml-stylesheet type="text/xsl" href="abc.xsl" ?> at the top of the document, but I have a hard time remembering the pseudo-attributes. One way to approach it would be, I type <? and press Ctrl+Space to get some suggested completions, like <?xml and <?xml-stylesheet When I choose xml-stylesheet, I would get suggested pseudoattributes "type" and "href" with appropriate values. Another approach is to enhance the Document / XML Document / Associate menu item to allow associating a stylesheet. Regards, Lars

2 3

macro to insert element
by Shawn McKenzie 30 Mar '06

30 Mar '06

I am wondering if it is possible to define macros to insert elements. For instance, I would like to be able to have authors easily insert something like <keyword conref="../common/vars.xml#prod"/> all at once without them having to insert the element, insert the attribute and then type the value of the attribute. Any way to automate this with oXygen?

2 1

Re: [oXygen-user] Help Search highlighting
by Sorin Ristache 29 Mar '06

29 Mar '06

Hello Lars, Finally we succeeded to find a workaround for the JavaHelp search highlight problem. We had to make modifications to the HTML files displayed in the help viewer before they are indexed because the JavaHelp indexer computes wrong indexes. We inserted already a fixup step in the automated pipeline which produces the help archive. You can download a corrected version of the help archive for <oXygen/> 7.1 here: http://www.oxygenxml.com/update/helpFixed7.1/help.zip Just replace [oXygen-install-folder]/lib/help.zip with the downloaded file and restart <oXygen/> to see the search matches highlighted correctly. Best regards, Sorin http://www.oxygenxml.com/ Lars Huttar wrote: > Sorin Ristache wrote: > >> Hello, >> >> We know about the wrong highlights and we were not able to find a fix >> until now. We think it is caused by bugs in the Swing view used by the >> JavaHelp system to display HTML content because <oXygen/> does not >> implement a custom search mechanism. It provides the search control of >> the JavaHelp system. The problem is worse if you run <oXygen/> with a >> Java 1.4 virtual machine: the highlights do not match the word >> correctly even at the beginning of the page on the right. That means >> the Swing view works better in later versions of the Sun's JVM >> (1.5.0_x) but some bugs still exist. We still try to find a solution. >> >> Starting with version 7.2 the Help will be presented in a separate >> window, with usual platform-dependent decorations (on Windows, by >> default a window has minimize, maximize and close buttons) and a >> separate taskbar button. It will behave as a normal window, with the >> only restriction that closing the main frame of the application will >> close also the Help window. It is already implemented in the >> development stream but there is a problem with the focus when F1 is >> pressed in a type of dockable views, bringing the main frame on top of >> the help window at a very short time after F1 is pressed and the help >> window is displayed. We work on this too. >> >> >> Best regards, >> Sorin > > Thanks again for your responsiveness. I'll say again that this is one of > the big reasons why I stay with Oxygen. > Lars

1 1

Re: xQuery comments not supported?
by David Sewell 29 Mar '06

29 Mar '06

Exclamation points also cause problems for XQuery syntax highlighting on oXygen 7.1. Try: (: this comment and the next line are highlighted properly :) declare variable $foo := "foo"; (: the next lines are highlighted with comment color! :) for $n in 1 to 3 return $n Remove the '!' from the comment restores the correct highlighting. -- David Sewell, Editorial and Technical Manager Electronic Imprint, The University of Virginia Press PO Box 400318, Charlottesville, VA 22904-4318 USA Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903 Email: dsewell(a)virginia.edu Tel: +1 434 924 9973 Web: http://www.ei.virginia.edu/

2 1

Help Search highlighting
by Lars Huttar 28 Mar '06

28 Mar '06

Hello, Seeing once again your responsiveness to bug reports prompted me to report one that has been a minor irritation for quite a while. In the Help window (User Manual), I click on the Search icon. Then I type a word in the Find text field, e.g. "associate", and press Return. A list of chapters where matches are found is shown below the Find field, and the content of one of them is shown on the right. In the content pane, the searched-for keyword is highlighted. At first, this highlighting works fine, but as we get lower down in the chapter, it begins to deviate from the search terms. Near the middle of a long chapter, the highlights are not even close to the word "associate", so it's hard to find the search terms. (There's also no "next occurrence" button.) This is happening to me in Oxygen 7.1, but I remember this behavior since at least v6. I'm using Windows XP; my coworker with Mac OSX sees the same behavior. While I'm on the topic, I'd like to put in a couple of other UI requests for the Help window... - The usual title bar icons (minimize, maximize, restore) are missing. - The Help window is always on top, yet is not modal (you can still type in the main Oxygen window). Seems to me always-on-top goes with being modal. My preference would be that the Help window does not have to stay on top. Thanks, Lars

2 1

xQuery comments not supported?
by Jonas Lundberg 28 Mar '06

28 Mar '06

In xQuery, I frequently use comments like the following: (: http://localhost:8080/cocoon/ladda_in?id=cocoon&page=index/webdesign&locati… :) If I do that in oXygen, syntax highlighting does not work. Is there a good reason for this? (I have now evaluated oXygen for xQuery for a while. It seems oXygen *almost* supports working with xQyery) Best regards Hans

2 1