John L

I happen to know the people who wrote the IDNA specs and they would prefer that UTS46 die. Its fuzzy mappings cause problems when you go from U -> A...

@jribbens Sorry, I wasn't being very clear. IDNA2008 deliberately took the preliminary mapping out of the spec. (See RFC 5895.) Mapping operations are very language dependent, e.g., case folding in...

@jribbens This may be too far into the weeds, but I'd rather some way you can set a mapping at the beginning of your program and then have all `.encode('idna')`use...

In RFC9315 and RFC9194 the space is correct. I don't see how the tool is supposed to guess what the author meant. Seems like a thing for linting, not doing...

In 9315 the text is: `However, the zero- or one-touch approach` with the line break before "or" so the space is correct. As I said, this is not something software...

Assuming you don't plan to print it out, why is this a problem?

Looks to me like the fix is to combine repeated items, e.g. [Section 1, Paragraph 3](https://ietf-wg-ohai.github.io/oblivious-http/index/draft-ietf-ohai-ohttp.html#section-1-3); [Section 2, Paragraph 1](https://ietf-wg-ohai.github.io/oblivious-http/index/draft-ietf-ohai-ohttp.html#section-2-1); [Section 2, Paragraph 3](https://ietf-wg-ohai.github.io/oblivious-http/index/draft-ietf-ohai-ohttp.html#section-2-3); [Section 2, Paragraph 3](https://ietf-wg-ohai.github.io/oblivious-http/index/draft-ietf-ohai-ohttp.html#section-2-3); [Section 2,...

> FWIW; the index should not be part of the prepped document. On the contrary, the point of prepping is to get a document ready to render and the index...

I'm planning to add a section to the as-implemented doc that describes changes that have been proposed but not made (yet). I'm at a conference in Europe this week, will...

@cabo we have made way too many ad-hoc changes to the grammar and I am not interested in making any more until we have a process beyond "some person wants...