[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [groff] [PATCH] new requests to case-transform string register value
Re: [groff] [PATCH] new requests to case-transform string register values
Thu, 04 Jul 2019 22:58:10 +0200
G. Branden Robinson wrote in <20190703154957.27lxnueucvu2cr5v@localhost.\
|A recurring theme in my man page clean-up work has been my violent
|antipathy for shouting capitals in their texts. While I don't _like_
|being shouted at for reasons other than true emergency, the real problem
|with the capitalization convention in man pages is that it happens at
|the input source, destroying information (case distinctions) that is
|unrecoverable by the typesetting system later.
|Here is the last time we discussed the issue:
|The consensus seemed to be that pushing case-transformation
|functionality down into language would be worth trying.
|So, here's an implementation. Comments welcome.
|I expect some bikeshedding on the names of the requests. I'm not wedded
|to the ones I have; my main criterion is:
|* The new request names should collate adjacently in the existing
| request namespace. E.g., "stringup" and "stringdn" are a much better
| pair than "upstring" and "dnstring". If someone is looking for one of
| them, it's not going to be long before they wonder what/where the
| other one is.
I am totally out still and for some time to come, but from looking
at the code all i know and can do is to wonder how far you come
with that 7-bit ASCII only toupper()/tolower().
--End of <email@example.com>
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)