unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Neal Lester <neal@3dsafety.com>
Cc: 4067@debbugs.gnu.org
Subject: bug#4067: nxml-mode missed invalid element in document
Date: Thu, 21 Jan 2021 17:33:51 +0100	[thread overview]
Message-ID: <87pn1y6yhc.fsf@gnus.org> (raw)
In-Reply-To: <1249584279.9834.5.camel@magical> (Neal Lester's message of "Thu,  06 Aug 2009 11:44:39 -0700")

Neal Lester <neal@3dsafety.com> writes:

> In my rnc schema file, I have an element "paragraph" defined as:
>
> paragraph = element import:paragraph { palette?, (text | (english,
> relevance?)) }
>
> palette = attribute palette { text }
>
> english = element import:english { text }
>
> relevance = element import:relevance { always | (if_exposure |
> not_exposure | if_exposure_code | code_equal_or_less_than |
> code_equal_or_greater_than | in_state | employees_in_state |
> max_employees_in_state | if_exposure_universe | not_exposure_universe |
> or | and | eiffel | is_required | not_is_required | not_in_state )+ }
>
> In my document I had empty "paragraph" elements but nxml-mode did not
> identify the document as invalid.

(I'm going through old bug reports that unfortunately got no response at
the time.)

To ensure that we're looking at the same problem, do you have a complete
test case, starting from "emacs -Q"?  That is, the rnc schema file and
the XML file that nxml mode does the wrong thing with?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-01-21 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 18:44 bug#4067: nxml-mode missed invalid element in document Neal Lester
2021-01-21 16:33 ` Lars Ingebrigtsen [this message]
     [not found]   ` <CAH=g7+n7dqkP6imYzqGGD_KRzRuqTFWq+Ukmi34Op240XN+4gA@mail.gmail.com>
2021-01-25 23:47     ` Lars Ingebrigtsen
     [not found]       ` <CAH=g7+m5ohb0FgjY2RKfa0OYJU4yj5GAQEDgFxeZ-KUaVmG5ZA@mail.gmail.com>
2021-01-27  1:24         ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pn1y6yhc.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=4067@debbugs.gnu.org \
    --cc=neal@3dsafety.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).