OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook] Why does <menuchoice> support multiple <guimenuitem> elements?

David O'Brien <daobrien@redhat.com> writes:
> If a GUIMenuItem is terminal, shouldn't there be only one? Our writers
> regularly include >1 inside <menuchoice> but we don't get any
> validation errors. What did I miss?

The line between descriptive markup and modeling is a bit blurry.
DocBook definitely dips its toes into modeling here and there, but it
isnât especially prescriptive where it doesnât have to be.

Iâm inclined to agree that you shouldnât put more than one guimenuitem
in a menu choice, but someone somewhere probably has a use case that
says they need to do it.

You can create a local customization that imposes tighter constraints.
If you do that, all of your documents will still be valid DocBook. If
DocBook is too constrained and you need to relax constraints, then your
documents wonât be valid DocBook and that may cause problems (technical
or political) for you. Thatâs one motivation for not being overly

                                        Be seeing you,

Norman Tovey-Walsh <ndw@nwalsh.com>

> As long as a word remains unspoken, you are its master; once you utter
> it, you are its slave.--Solomon Ibn Gabirol

Attachment: signature.asc
Description: PGP signature

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]