Re: [xml2rfc] rfc2629-xhtml.ent warning

[Julian Reschke <[e-mail]>]

On 16.05.2023 16:23, Jay Daley wrote:
>
>
>> On 16 May 2023, at 14:37, Julian Reschke <[e-mail]> wrote:
>>
>> On 16.05.2023 15:19, Jay Daley wrote:
>>>
>>>> On 16 May 2023, at 14:12, Robert Moskowitz <[e-mail]> wrote:
>>>>
>>>> It has been a few weeks since my last run of xml2rfc, and that was
>>>> on what I had installed on my old Fedora 35 notebook, now on my
>>>> updated Fedora 38 system...
>>>>
>>>> So this morning I got (4 times):
>>>>
>>>> Warning:
>>>> /home/rgm/data/htt/Projects/Critical/drafts/rfc2629-xhtml.ent is no
>>>> longer needed as the special processing of non-ASCII characters has
>>>> been superseded by direct support for non-ASCII characters in RFCXML.
>>>>
>>>>
>>>> The only use of rfc2629 in my xml is:
>>>>
>>>> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
>>>> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
>>>>
>>>> So obviously there has been a change that I did not catch.  No
>>>> comments from the rfc editor on working with my drafts a couple
>>>> months back for rfcs 9373 & 9374 that had these lines.
>>>>
>>>> So what is the current for !DOCTYPE and xml-stylesheet?
>>>
>>> A DOCTYPE is not recommended because the grammar is specified in
>>> Compact RelaxNG not any other schema format.   The recommended method
>>> to associate the schema with the XML is
>>>
>>> <?xml-model href="rfc7991bis.rnc"?>
>>>
>>> Note, this will require you to have rfc7991bis.rnc in your build path.
>>>
>>> This is fully explained in the authors documentation here:
>>>
>>> https://authors.ietf.org/en/templates-and-schemas
>>>
>>> That same page also links to the "official" templates that can be
>>> used as starting points.
>>>
>>> Finally, the authors documentation also lists various XML editors and
>>> how the interact with the schema
>>>
>>> https://authors.ietf.org/en/drafting-in-xml
>>>
>>> Jay
>>
>> Jay,
>>
>> I don't think this is helpful.
>>
>> Robert's DOCTYPE declaration is used to define named character entities.
>> RelaxNG doesn't help with these at all.
>
> I was trying to address two things at once, but yes I can see that I
> only confused things.
>
> The page I pointed to explains this correctly
> https://authors.ietf.org/en/templates-and-schemas#character-entities
> <https://authors.ietf.org/en/templates-and-schemas#character-entities>
>
>>
>> The warning message from xml2rfc is completely misleading, as it
>> conflates entity declarations with validation.
>
> No it’s correct, the full rfc2629-xhtml.ent file is no longer required
> for exactly the reason explained in the warning.

The warning is misleading. It was never required.

This is an XML question, not an RFCXML question.

If you want named entities, you need to declare them. Either in an
external resource, or in the internal subset. Or, instead, given an
editor with proper Unicode support, you can type them directly (which,
depending on the code point, may or may not be a good idea).

This is true for all versions of x2mlrfc (the tool) and RFCXML (the
language). It has nothing to do with whether you use DTDs or RelaxNG for
validation, or whether you validate at all.

And yes, RFCXML since version 3 supports *outputting* non-ASCII
characters in HTML and TXT. But this has nothing to do with the way they
are *inserted* into the XML file.

Best regards, Julian