Re: roff_getstr() and input characters

[Kristaps Dzonsons <kristaps@bsd.lv>]

>> The reason I want to air it with you (I know it works: I've tested it 
>> across all manuals) is because it also removes the check for isprint(), 
>> using strcspn() instead.  As you can see, the rej filter is only for 
>> '\b', which we must prohibit else we boff output encoding; '\t' for 
>> non-literals (warning); and '\\' for the specials check.
>>
>> I argue for lifting the ASCII-constraint because (1) there's nothing in 
>> mdoc/groff/etc that disallows non-ASCII (e.g., Latin-1) characters and 
>> (2) it makes the code much cleaner.
>>
>> Thoughts?
>>
> 
> i don;t really know what you mean, to be honest. you'll have to dumb
> down your question a bit, i'm afraid...

Jason, right now, mandoc spits out a warning for any non-printable ASCII 
character.

This patch lifts this restriction, instead warning only about tabs and 
the "backspace" character.

We'd spoken about this before, but seeing it in action, I'm no longer 
sure.  The killer points are that -Tps will throw away all non-ASCII 
characters as it can't calculate their glyph widths, and -Thtml 
stipulates UTF-8 encoding, so anything but UTF-8 input will be gobbledygock.

In effect, once one uses a non-ASCII encoding, the rendered output will 
be irregular across output modes and, more importantly, user environment 
(terminals, etc.).  This is, in my opinion, a Bad Thing (tm).

Thoughts?

Kristaps
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv