Dear Dick,
The document type is determined automatically based on a set of mapping
rules. The rules are specified in the definition of the document type, see
Options->Preferences -- Document Type Association
select user role to Developer
click on a document type, DocBook 5 for instance
click on the Edit button
In the document type dialog that appears there is a Rules tab that
contains the rules that when activated will determine that the document
belongs to that document type. A rule can match on the root element
name, namespace, on the file name and on the Public ID.
(As a side note, in the version 9 release we will provide also an
alternative mechanism for determining that a document belongs to a
document type, you will be able to specify a Java class that implements
a specific interface and that has access also to the root element
attributes so it can decide based on some attribute name or value
whether or not the document belongs to the document type.)
It may be possible that your document did not match the rules we defined
for the DocBook document types. You can check those rules and eventually
add more rules to better match your documents.
For a quick view of the customization for DocBook you can create a new
document using File->New then select "From templates" then "DocBook 5 -
Article". Switch to Author mode and you should be able to see
- a DocBook5 entry in the main menu
- a toolbar with the custom actions
- a set of actions in the contextual menu
Note also that the DocBook 5 document type specifies also a CSS and a
schema. However, the values from the document type act as defaults, if
you associate another CSS or a schema inside the XML document then those
from the document will be used.
Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina - http://aboutxml.blogspot.com/
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com
Dick Hamilton wrote:
George,
First of all, thanks for giving us the opportunity to try out the
Oxygen beta. I've heard a lot of good things about Oxygen, but this
is the first time I've tried it and in general I like it a lot.
And the thread about semantic vs. representational content has been
entertaining:). I have a question and a comment:
The question is basic. I'm able to associate my files with the css
and a schema (docbookxi.rnc), and both seem to work fine. But, I have
not been able to figure out how to associate the docbook customization
that has caused all the hoopla. Can you describe how to do that?
The comment is about the "hoopla." Seems like the clear message from
this thread is that no one, default framework will satisfy everyone,
so making customization easy for users is important. I'm glad to see
from your recent email that you're supporting user customization.
I have two suggestions regarding that:
- Make it easy to subset the schema. A lot of organizations use
a custom subset of docbook that only contains the tags they
care about. That capability may already be there (I'm not that
familiar with Oxygen), but if not, it should be.
- I come down on the side of the "semanticists" (is that a word:-)
when it comes to the question of emphasis, so I would encourage
you to change the default DocBook framework to show a selection
of inline elements, rather than bold, italic, and underline. But,
I wouldn't argue against showing the rendering as part of the
selection so folks know what they're getting.
My experience as a writer and manager of writers is that if you
make it easy for writers to find the elements you want them to use,
they will use those elements. However, if you make it hard to find
the elements you want them to use, they will use anything that looks
ok and validates. Therefore, if you want them to use <replaceable>,
<wordasword>, <firstterm>, etc., then those choices need to be easily
accessible or they'll simply choose some convenient element, like
<emphasis>, that has the styling they want.
Dick Hamilton
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
