Lenient mode and DocBook V5

Hi,

it seems that DocBook V5 schema is written in a way which permanently 
turns XXE into lenient mode (which is of course not very handy for real 
editing).

The cause of this are info and indexterm elements. I can understand why 
info cause lenient mode. If you have element with required title such 
chapter, you can write it down like

<chapter>
   <title>

or

<chapter>
   <info>
     <title>

I can see ambiguity here and this is not problem for me, because I 
actually use customized version of DocBook which allows only former way 
of specifying title.

What I actually do not get is problem with indexterms. Because indexterm 
can be child of almost any element in DocBook it means that lenient mode 
is present on almost all DocBook elements. But why lenient mode must be 
used for elements that contain indexterm?

DocBook schema defines three content models for indexterm which are then 
combined together to single pattern used in places suitable for 

[?] XXE customization -- problems with two independent plugins

Hello, Hussein!

First at all, thank you and your company for cool editor!

Concerns my problems.
Suppose, I want to create two XXE-plugins - cfg1 & cfg2.
Each plugin will made small modification in standard menu
and toolbar. Any end-user should be able install both plugins
simultaneously or separately from each other.

I think that when both plugin will loaded I can see the
following state of menu:

\DocBook
    ... some items
    --- separator
    \Convert Document ->
    ---
    Group 1... -> menu of first plugin cfg1
    ---
    Group 2... -> menu of first plugin cfg2

But I can see only "Group 1". The same thing with toolbar.

My customization config available in attached archive.
What's wrong?

Thank you,

--

-- 

Re: Lenient mode and DocBook V5

Jirka Kosek wrote:
> 
> it seems that DocBook V5 schema is written in a way which permanently
> turns XXE into lenient mode (which is of course not very handy for real
> editing).

This is a bit severe. This more or less implies that XXE does not
support RELAX NG at all!

XXE has limitations which makes it uncomfortable using some RELAX NG
schemas but despite these limitations (which are fully described in
http://www.xmlmind.com/xmleditor/_distrib/doc/rngsupport/index.html),
XXE should allow to comfortably edit the vast majority of the documents
conforming a RELAX NG schema.

> The cause of this are info and indexterm elements. I can understand why
> info cause lenient mode. If you have element with required title such
> chapter, you can write it down like
> 
> <chapter>
>   <title>
> 
> or
> 
> <chapter>
>   <info>
>     <title>
> 
> I can see ambiguity here and this is not problem for me, because I
> actually use customized version of DocBook which allows only former way

Re: Lenient mode and DocBook V5

Hussein Shafie wrote:

> This is a bit severe. This more or less implies that XXE does not
> support RELAX NG at all!

Do not be so so demanding on you. DocBook RELEX NG schema is really 
complex and uses RELAX NG power to the maximum. Majority of RELAX NG 
schemas are not using features like co-constraints.

> XXE has limitations which makes it uncomfortable using some RELAX NG
> schemas but despite these limitations (which are fully described in
> http://www.xmlmind.com/xmleditor/_distrib/doc/rngsupport/index.html),
> XXE should allow to comfortably edit the vast majority of the documents
> conforming a RELAX NG schema.

I know this document, I read it twice before I submitted my post. And I 
was able to fix some issues on schema level.

> (I'm using XXE V3.2 and DocBook V5b5.)
> 
> Therefore suffice for the user not to choose <title>+<info>' (who needs
> <title>+<info> anyway when the first kind of <info> can contain a <title>?).

Legacy, legacy, legacy...
I noticed this behavior on existing documents, not on newly created.

> XXE already detects this case for class=startofrange and
> class=endofrange, but not for db.indexterm.singular (???).
> 
> In the latter case, I think this is a bug because "Show Content Model"

Re: Lenient mode and DocBook V5

Jirka Kosek wrote:
> 
> BTW, any plans to support embedded Schematron rules for validation?
> DocBook V5 uses them to specify some additional constraints which are
> hard or impossible to define in RELAX NG. I have also RELAX NG +
> Schematron schema for XHTML which is able to catch much more XHTML
> specification violations that W3C validator (see http://relaxed.vse.cz).
> It would be really nice feature to have.

Schematron is definitely on our TODO list. The problem is that, like for
all other features on our TODO list, we cannot tell you when it will be
implemented.

--
XMLmind XML Editor Support List
xmleditor-support <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Re: [XSC] Dictionary

Joe Lippeatt wrote:
> Ooooh, I thought it would be added on the server when the user presses
> "finished" button on the JSP page.

This is not the case. The servlet (which is in fact a JSP of just one
hundred lines long) does not maintain a database of learned words on the
server side (there would be one row/personal dictionary per web user!).

> Then we may choose to create a simple interface that submits new words
> to be saved to a text file.  I see in your documentation that a simple
> text file can be used with your product.  Can a text file be used in
> combination with compiled dictionaries?  

Yes, that's right.

> Our development models
> currently use eng and eng-us, can/how can we add a "customWords.txt"
> file as well?

If "customWords.txt" is static (i.e. just updated by hand from time to
time), the basic idea is to replace the stock English dictionary by a
customized one.

The customized English dictionary would be a composite dictionary.

To create it, simply edit WEB-INF/classes/en/default using a plain text
editor:

---
 <at> multilink: English

Re: [Fwd: [?] XXE customization -- problems with two independent plugins]

Alexey "[Die]Ash" Shakin wrote:
> 
> It's seems that I can read mailing-list xmleditor-support <at> , but
> I can't send email. 

You can send emails to xmleditor-support <at> . I (i.e. xmleditor-support <at> )
have received your original email.

> How to I can fix with issue?

Public mailing-list xmleditor-support <at>  is moderated every 1-2 days.
Therefore, it often occurs that a person sends an email to this mailing
list and does not immediately ``see'' that this has succeeded.

> Anyway. Could you please help me with my problems?

Yes. This will be my next email.

--
XMLmind XML Editor Support List
xmleditor-support <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Re: [?] XXE customization -- problems with two independent plugins

Alexey "[Die]Ash" Shakin wrote:
> Suppose, I want to create two XXE-plugins - cfg1 & cfg2.
> Each plugin will made small modification in standard menu
> and toolbar. Any end-user should be able install both plugins
> simultaneously or separately from each other.
> 
> I think that when both plugin will loaded I can see the
> following state of menu:
> 
> \DocBook
>    ... some items
>    --- separator
>    \Convert Document ->
>    ---
>    Group 1... -> menu of first plugin cfg1
>    ---
>    Group 2... -> menu of first plugin cfg2
> 
> But I can see only "Group 1". The same thing with toolbar.
> 
> My customization config available in attached archive.
> What's wrong?

Nothing is wrong. XXE has just not been designed to allow this.

In cfg1/cfg1.xxe and cfg2/cfg2.xxe, I've replaced <configuration
name="cfg1"...> and <configuration name="cfg2"...> by <configuration
name="DocBook"...>. (File names and directory names cfg1, cfg1.xxe,
cfg2, cfg2.xxe are fine. What's important is the name attribute.)

Article Author prints incorrectly

I'm trying to learn how to use and customize XMLmind.

I created a DocBook Article.  When I specify an <author>
as child of the <title>, it is displayed as if the name
were part of the title, on the same line and in the same
font as the title, with no space.  This is true for both HTML
and PDF output.

The definition of "author" is in docbook/xsl/fo/titlepage.xsl,
which calls "anchor" and then "person.name".

There's a definition for "person.name" in docbook/xsl/common/common.xsl,
which invokes (or should invoke) person.name.first-last.  It looks
like the templates simply output the text, without any formating.

Shouldn't there be some XSL-FO output around the author?

--

-- 
Michael Eager	 eager <at> eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

--
XMLmind XML Editor Support List
xmleditor-support <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Anonymous table objects

Hi,

while trying to css-format a docbook segmentedlist as a table, I
stumbled across the issue that segtitle is not enclosed in a "row"-like
element, therefore making CSS handling harder.

It looks like XXE does not support Anonymous table objects:
http://www.w3.org/TR/REC-CSS2/tables.html#anonymous-boxes

Unless I didn't succeed in making it work?

Otherwise is it planned to add this?

Best regards,

Camille.

--
XMLmind XML Editor Support List
xmleditor-support <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support