- oXygen-user - www.oxygenxml.com

perforce?
by Shawn McKenzie 09 Jun '06

09 Jun '06

It is nice that the new version supports subversion. Any chance of Perforce integration in the future?

2 1

RelaxNG validation without DTD-compatibility
by Chris Lilley 09 Jun '06

09 Jun '06

Hello oxygen-user, I was looking through the oXygen preferences and could not see a way to perform RelaxNG validation in non-DTD-compatible mode. DTD-compatible mode is the default for Jing, but it cuts out a bunch of useful things that RelaxNG can do. Specifically, the SVG Tiny 1.2 RNG depends on these features for enabling xml:id support - if an element has just an id attribute, that attribute is of type ID; if it has just xml:id, that is of type ID;if it has both then xml:id is of type ID and id is not. On the command line, it would be Jing -i. How do I use Jing this way in oXygen? If its not possible, could it be added? I'm using the newly released oXygen 7.2. I tried toggling 'Check ID/IDREF' in the prefs under RELAX NG but this did not seem to change things. -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG

2 2

TEST 2
by Mihai Ionescu 09 Jun '06

09 Jun '06

Test

1 0

TEST 2
by Mihai Ionescu 09 Jun '06

09 Jun '06

1 0

TEST
by Mihai Ionescu 09 Jun '06

09 Jun '06

1 0

Re: "content is not allowed in prolog" using Oxygen
by Oliver Meyer 02 Jun '06

02 Jun '06

Hi Joshua, I receive a digest and read the mail using outlook. In my view the byte sequence EF BB BF precedeces the first character of your XML file. That is the BOM for UTF-8 (http://www.unicode.org/faq/utf_bom.html#BOM) and that content is correct XML (sec. 4.3.3 of XML Spec: ... entities encoded in UTF-8 MAY begin with the Byte Order Mark ... ) Usually Oxygen handles encoding very well, so maybe you use some other editor in your processing chain that is not that standard conform and adds another BOM. I had similar problems using Ultraedit. HTH Oliver > -----Ursprüngliche Nachricht----- > Message: 1 > Date: Thu, 01 Jun 2006 11:49:34 -0400 > From: Joshua Noble <jnoble(a)mindseye.com> > Subject: [oXygen-user] "content is not allowed in prolog" using Oxygen > for MXML files > To: oxygen-user(a)oxygenxml.com > Message-ID: <447F0C8E.8080101(a)mindseye.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > 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?

1 0

"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