On Sat, 7 Sep 2013, Geoffrey Sneddon wrote:
[...] this seems ... cubersome ... to implement in a conformance
checker. Which reminds me, does
# Conformance checkers must report at least one parse error
# condition to the user if one or more parse error conditions exist
On Thu, 5 Sep 2013, Geoffrey Sneddon wrote:
The phrasing content section states:
Text nodes and attribute values must consist of Unicode characters,
must not contain U+ characters, must not contain permanently
undefined Unicode characters (noncharacters), and must not contain
On 06/09/2013 04:05, Kang-Hao (Kenny) Lu wrote:
(2013/09/06 6:08), Geoffrey Sneddon wrote:
The phrasing content section states:
Text nodes and attribute values must consist of Unicode characters,
must not contain U+ characters, must not contain permanently
undefined Unicode characters
(2013/09/06 6:08), Geoffrey Sneddon wrote:
The phrasing content section states:
Text nodes and attribute values must consist of Unicode characters,
must not contain U+ characters, must not contain permanently
undefined Unicode characters (noncharacters), and must not contain
control
