Wes Hurd wrote:
> What I meant about smart quotes being dangerous was, if copying the output
> text that contains smart quotes to use somewhere else (especially in code),
> the smart quotes have to be manually replaced which is tedious for the user
> (programmer).
It's quite the opposite: The smar
On 12/6/19 6:52 PM, Wes Hurd wrote:
What I meant about smart quotes being dangerous was, if copying the
output text that contains smart quotes to use somewhere else (especially
in code), the smart quotes have to be manually replaced which is tedious
for the user (programmer).
The user may not e
What I meant about smart quotes being dangerous was, if copying the output
text that contains smart quotes to use somewhere else (especially in code),
the smart quotes have to be manually replaced which is tedious for the user
(programmer).
The user may not even see that smart quotes are being used
* lib/nstrftime.c (width_add, width_add1, width_cpy):
New macros, which generalize ‘add’, ‘add1’, ‘cpy’ by adding
a new WIDTH parameter.
(add, add1, cpy): Use these macros.
(width_add): Do not treat digits == 0 as a special case,
do not pad if padding is ‘-’, and do not use a negative width.
(__str
* Tim Rühsen:
> On 12/5/19 4:12 PM, Wes Hurd wrote:
>> Hi,
>>
>> It seems GNUlib quote encoding goes to Unicode smart quotes, which causes
>> command-line program output to be in smart quotes.
>> Smart quotes are dangerous for programmers and technical users, and should
>> be avoided in program o
Hi Bruno,
On Thursday, 5 December 2019 22:56:08 CET Bruno Haible wrote:
> One suggestion, though:
>
> > lib/xstrtol-error.h | 45 +++
> > lib/xstrtol.h | 20 ---
>
> It is possible to have several modules share the same .h file. F
