Leonard Rosenthol

Yes, the restriction is intentional and was primarily an attempt to move from "raw" ISO 639-1 to BCP-47.

@t-merz it's entirely about backwards compatibility, since 32K-1 (and earlier) only supported two byte escape codes.

>Is the string in question Hello World, Hello\nWorld, or Hello \n \n \n\n\nWorld? All of those are perfectly acceptable choices. That PDF appears to be invalid - it is killing...

Thanks @MatthiasValvekens Using the `-fixed` version, it opens and displays just fine in Acrobat but only displays a blank page in Apple Preview, PDF Expert and FoxIt (Mac)

> If we can tighten that up, then I'm all for it: e.g., we could only allow a stream to terminate after an operator. Perhaps a better statement might be...

>The fact that many implementations support splits at other locations (e.g. between operands) is then just permissive behaviour. Or more likely, simply a result of implementation. For example, if an...

>another example I can think of is a comment that is not terminated by an EOL in the first stream - does it then span into the next stream until...

> Circling back, though, I think the essence of this issue is that the text of Table 31 makes the combining operation sound like it happens at the lexical or...

>I'm confused, are you saying that the rendering of a PDF file may differ by implementation in the way that is being discussed here? Absolutely! Many aspects of the PDF...

>I think Matthias Valvelkens provided all the necessary evidence to the contrary above. Really? I think he actually backed me up with his statement: > So, if this file were...