- oXygen-user - www.oxygenxml.com

Re: [oXygen-user] Schema documentation from specific root element
by Adrian Buza 21 May '10

21 May '10

Hi, We already have the clean schema feature request added to our issue tracking tool. It will be implemented in the long term so it's going to take a while. I've added your vote for it. Regards, Adrian Adrian Buza Oxygen XML Editor support Ingo Freitag wrote: > Hi, > > thank you for your quick answer. > > The best solution would be something complete automatic, but it is also possible, that I remove the other root elements before. > > But one problem is, that the schema uses global types (simple and complex) very intensive, which means for me to manually remove all those elements as well. > This is a huge work. > > I already read in former posts, that you were asked to add a function to 'clean' a schema from unused types and other elements. > In my case such a function would do the trick very well :) So my vote to implement it as soon as possible. > > Best regards, > > Ingo > > -----Original Message----- > From: Adrian Buza [mailto:adrian@sync.ro] > Sent: Thursday, May 20, 2010 10:47 AM > To: Ingo Freitag > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific root element > > Hello, > > The schema documentation tool is not contextual, it generates the > documentation for the entire schema so I'm afraid you cannot simply > generate the documentation starting from a given root element. > > But there may be a few options that could help you break it down into > smaller parts. > For example if you generate HTML you can split the output in multiple > files by component(in the Output tab). Other than that there are the > generic filters from the Settings tab, but I'm not sure if they're > useful to you in this case. > > There's also the possibility to trim the schema and remove the unwanted > root elements before generating the documentation, but I'm guessing you > were looking for something automatic to do this. > > Regards, > Adrian Buza > Oxygen XML Editor support > > Ingo Freitag wrote: > >> Hi, >> >> I have a very huge schema file with several root elements included. >> Now I want to create a documentation out of one of those root elements only. >> >> Is this somehow possible? >> Of course all linked and referenced types shall also be included in the documentation. >> >> Ingo >> >> >> >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user >> >> > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user >

1 0

Use DITA 1.1 instead of 1.2?
by Yves Barbion 21 May '10

21 May '10

Hi again group I see that oXygen already supports DITA 1.2, which is great! However, this can be a problem in "mixed editor" environments as long as the other editors don't support DITA 1.2 yet. Is there an easy way in oXygen to make sure that the authors don't use the elements and attributes of the DITA 1.2 standard, for example <hazardstatement>, for the time being? Thanks -- Yves Barbion www.scripto.nu

2 1

Re: [oXygen-user] Schema documentation from specific root element
by Mark Baker 20 May '10

20 May '10

I think it should be noted that there is a big difference between schema documentation and doctype documentation. * A schema may define 0, 1, or many root elements, and therefore 0, 1, or many document types. Multiple document types defined by the same schema may have nothing in common with each other. * A document type may contain elements defined in one or more schemas, and even allow content that is not governed by any schema. For instance, a particular document type may allow the use of MathML or SVG within the document. The documentation of any one schema, therefore, would not constitute documentation for the entire document type. * A document type may reuse a complex type defined in a schema at different points in a document type while assigning substantially different document semantics to that type in each of the locations in which it is used. Schema documentation tools necessarily follow the structure of schemas. They describe the structure of the schemas themselves, but the structures of the document types defined by the schemas may be much more complex and varied than the structures of the schemas themselves (or vice versa -- a complex schema may define a simple document type). Generating schema documentation from one root element of a schema, therefore, is not at all equivalent to creating document type documentation for documents that have that root element. We produce a lot of document type references. We have two different document type reference composition and build processes for different types of document. (Data oriented document types and text oriented document types are significantly different in their documentation needs.) Schema documentation, generated by standard schema documentation tools, as good as some of them are, would not come close to meeting our user's needs. I think you may need to figure out if what you really need is document type documentation, rather than schema documentation. If so, you will need a different process to create it. Mark > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Ingo Freitag > Sent: May 20, 2010 12:07 PM > To: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific > root element > > Hi, > > thank you for your quick answer. > > The best solution would be something complete automatic, but > it is also possible, that I remove the other root elements before. > > But one problem is, that the schema uses global types (simple > and complex) very intensive, which means for me to manually > remove all those elements as well. > This is a huge work. > > I already read in former posts, that you were asked to add a > function to 'clean' a schema from unused types and other elements. > In my case such a function would do the trick very well :) So > my vote to implement it as soon as possible. > > Best regards, > > Ingo > > -----Original Message----- > From: Adrian Buza [mailto:adrian@sync.ro] > Sent: Thursday, May 20, 2010 10:47 AM > To: Ingo Freitag > Cc: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Schema documentation from specific > root element > > Hello, > > The schema documentation tool is not contextual, it generates > the documentation for the entire schema so I'm afraid you > cannot simply generate the documentation starting from a > given root element. > > But there may be a few options that could help you break it > down into smaller parts. > For example if you generate HTML you can split the output in > multiple files by component(in the Output tab). Other than > that there are the generic filters from the Settings tab, but > I'm not sure if they're useful to you in this case. > > There's also the possibility to trim the schema and remove > the unwanted root elements before generating the > documentation, but I'm guessing you were looking for > something automatic to do this. > > Regards, > Adrian Buza > Oxygen XML Editor support > > Ingo Freitag wrote: > > Hi, > > > > I have a very huge schema file with several root elements included. > > Now I want to create a documentation out of one of those > root elements only. > > > > Is this somehow possible? > > Of course all linked and referenced types shall also be > included in the documentation. > > > > Ingo

1 0

Re: [oXygen-user] Schema documentation from specific root element
by Adrian Buza 20 May '10

20 May '10

Hello, The schema documentation tool is not contextual, it generates the documentation for the entire schema so I'm afraid you cannot simply generate the documentation starting from a given root element. But there may be a few options that could help you break it down into smaller parts. For example if you generate HTML you can split the output in multiple files by component(in the Output tab). Other than that there are the generic filters from the Settings tab, but I'm not sure if they're useful to you in this case. There's also the possibility to trim the schema and remove the unwanted root elements before generating the documentation, but I'm guessing you were looking for something automatic to do this. Regards, Adrian Buza Oxygen XML Editor support Ingo Freitag wrote: > Hi, > > I have a very huge schema file with several root elements included. > Now I want to create a documentation out of one of those root elements only. > > Is this somehow possible? > Of course all linked and referenced types shall also be included in the documentation. > > Ingo > > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user >

2 1

Easiest way to add a header row to a table in a DITA topic?
by Yves Barbion 20 May '10

20 May '10

Hi group What's the easiest way to add a header row to a table in a DITA topic? Cheers -- Yves Barbion www.scripto.nu

2 1

Schema documentation from specific root element
by Ingo Freitag 20 May '10

20 May '10

Hi, I have a very huge schema file with several root elements included. Now I want to create a documentation out of one of those root elements only. Is this somehow possible? Of course all linked and referenced types shall also be included in the documentation. Ingo

1 0

Author : Number of characters
by Rogie Isabelle 12 May '10

12 May '10

Hi, Is it possible to know simply the number of characters in a xml file? I use Author version 10.2 on Mac OS X. Best Regards, _______________________________________ Isabelle Rogie Database Chief project Wolters Kluwer France

4 6

Looking to hire programmer for content-completion customization
by Тома Тасовац 12 May '10

12 May '10

Hi, I am looking for a programmer who is well-versed in Oxygen and various XML technologies to enable server queries for attribute value completion in Oxygen under certain, clearly defined conditions. e.g. <w lemma="" ana="">word</w> -- lemma and ana attributes need to be completed based on what the server returns when queried. The recommended procedure for this type of work would be like this: > If you want to search and show the custom attribute values on request when "Ctrl-Space" gets called in the attribute value (which is the way in which Oxygen content completion works) this can be done through the Oxygen Author SDK API: > > http://www.oxygenxml.com/developer.html#XML_Editor_Authoring_SDK > > In order to do this you usually have to define an external document type association for your XML file types in the Document Type Association preferences page. The document type association contains association rules for your XML documents, document templates, XML catalogs + in the "Extensions" tab you can contribute with a Content completion handler which implements the SchemaManagerFilter class. This class contains a method called: > > List<CIValue> filterAttributeValues(List<CIValue> attributeValues, WhatPossibleValuesHasAttributeContext context); > > which can be used to propose additional attribute values in a certain context. I have written a detailed specification of what I need, together with a sample XML file from which one can test server queries and responses. If you are interested in this type of work, please email me off the list and I will get in touch. All best, Toma ————————————————————— Toma Tasovac Center for Digital Humanities (Belgrade, Serbia) http://humanistika.org • http://transpoetika.org

1 0

bug-fixes in <oXygen/> XML Editor 11.2, build 2010031611
by Mark 10 May '10

10 May '10

Some time ago, I wrote mentioning that my java scripts would not run in <oXygen/> XML Editor 11.2, build 2010031611 and was given the workaround to save my script tags in two rather than one tag: <script src=....></script> as opposed to <script src=.../>. I was told this was a regressive bug and would be fixed. At the same time, I was given an URL to check for bug fixes. Unfortunately, my email files have been destroyed and I no longer have that reference. Has this bug been fixed? If so, where can I download it? Thanks, Mark

2 1

Couldn't find hyphenation pattern en_US
by jsbien＠mimuw.edu.pl 07 May '10

07 May '10

I experiment with transforming TEI to PDF using the file http://tei.oucs.ox.ac.uk/ENRICH/gBank/gBank.xml?style=raw The first error I get is --8<---------------cut here---------------start------------->8--- SystemID: /home/jsbien/ENRICH/all/gBank.xml Engine name: Saxon-B 9.1.0.7 Severity: error Description: The process 'FOP' ended with code: 1. The error was: 2010-05-04 14:32:51 org.apache.fop.hyphenation.Hyphenator getHyphenationTree SEVERE: Couldn't find hyphenation pattern en_US --8<---------------cut here---------------end--------------->8--- The problem seems independent of the current locale. What is the remedy? Best regards JSB -- , dr hab. Janusz S. Bien, prof. UW - Uniwersytet Warszawski (Katedra Lingwistyki Formalnej) Prof. Janusz S. Bien - Warsaw University (Department of Formal Linguistics) jsbien(a)uw.edu.pl, jsbien(a)mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/

2 3