From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: docbook2mdoc: Fix a logic bug causing tree corruption: When parsing an
Date: Tue, 9 Apr 2019 08:35:59 -0500 (EST) [thread overview]
Message-ID: <e3fd893e1f348cb1@fantadrom.bsd.lv> (raw)
Log Message:
-----------
Fix a logic bug causing tree corruption:
When parsing an internal subset declaration,
text does not extend beyond closing square brackets.
Modified Files:
--------------
docbook2mdoc:
parse.c
Revision Data
-------------
Index: parse.c
===================================================================
RCS file: /home/cvs/mdocml/docbook2mdoc/parse.c,v
retrieving revision 1.27
retrieving revision 1.28
diff -Lparse.c -Lparse.c -u -p -r1.27 -r1.28
--- parse.c
+++ parse.c
@@ -976,7 +976,9 @@ parse_string(struct parse *p, char *b, s
/* Process text up to the next tag, entity, or EOL. */
} else {
- advance(p, b, rlen, &pend, "<&", refill);
+ advance(p, b, rlen, &pend,
+ p->ncur == NODE_DOCTYPE ? "<&]" : "<&",
+ refill);
xml_char(p, b + poff, pend - poff);
}
}
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2019-04-09 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3fd893e1f348cb1@fantadrom.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.bsd.lv \
/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.
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 NNTP newsgroup(s).