Re: synchronous and asynchronous grout (was: Novel use of .char)

[Deri]

On Thursday, 19 December 2024 00:34:49 GMT G. Branden Robinson wrote:
> For _input_ to GNU troff, maybe, if I can get it done.  I'd love that.
> 
> Except for one person (who doesn't contribute and no longer even
> participates on the mailing list), I don't know of anyone who's
> expressed interest in grout being a UTF-8 file format.
> 
> Is that something you want?  What should the consequences of invalid or
> incomplete UTF-8 sequences be?
> 
> Regards,
> Branden

Hi Branden,

I don't mind, I just thought you considered readability of the grout file 
important [1], currently lots of \[uXXXX] and \(XX are harder to read than 
UTF-8. It could be a setting in the DESC file so you don't need to change 
output drivers in one go.

I would have hoped that troff would barf at illegal UTF-8 sequences rather 
than pass them on through grout!

Cheers

Deri

[1] This was your stated reason for not committing "stringhex" from my branch, 
even though I told you I had a version of pdf.tmac which did not pollute the 
grout file with hex, instead you decided to introduce a substandard solution 
during my sabbatical. When I told you that one particular document was now 
taking over 13 minutes to produce, you did say you would need to do something 
about it.