Re: [xml2rfc] assuming that period (.) ends a sentence is sometimes wrong

[Carsten Bormann <[e-mail]>]

On 2021-03-01, at 13:57, Julian Reschke <[e-mail]> wrote:
> 
> Am 01.03.2021 um 13:46 schrieb Carsten Bormann:
>> On 2021-03-01, at 13:16, Julian Reschke <[e-mail]> wrote:
>>> 
>>> It means that a sequence of whitespace characters can be collapsed to a
>>> single space character.
>> 
>> That is XSLT normalize-space.
> 
> XPATH, to be pedantic.
> 
> It's not exactly the same thing in that leading / trailing space in
> content can be significant (at least if you consider it to apply to text
> child nodes of <t>). For instance,
> 
>  <t>see <xref target="foo"/></t>
> 
> is not equivalent to
> 
>  <t>see<xref target="foo"/></t>
> 
> At this point I'm not sure anymore what we're discussing here.

I’m sorry, I’m trying to elicit what you think xml:space=preserve does (or doesn’t that =default does, actually).  It does not mesh with what I learned about XML.

> If your point is that RFC 7991bis should be clearer about what XML calls
> the "default whitespace handling mode", I agree.

Well, what *DOES* XML call the default whitespace handling mode?

https://www.w3.org/TR/2008/REC-xml-20081126/#sec-white-space

> The value "default" signals that applications' default white-space processing modes are acceptable for this element; the value "preserve" indicates the intent that applications preserve all the white space.


(This is in a context of:

> In editing XML documents, it is often convenient to use "white space" (spaces, tabs, and blank lines) to set apart the markup for greater readability. Such white space is typically not intended for inclusion in the delivered version of the document. On the other hand, "significant" white space that should be preserved in the delivered version is common, for example in poetry and source code.

The intent certainly is not to get rid of all whitespace.  There is no talk about the whitespace normalization you have in mind, either.)

Grüße, Carsten