Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-07 Thread Paul Eggert
On 12/7/19 5:56 AM, Bruno Haible wrote: > So, we should write > L’Oréal and L’chaim with U+2019 > and OʼHara, OʼConnor with U+02BC. I wouldn’t use U+02BC MODIFIER LETTER APOSTROPHE in the Anglicized form of Irish names. The Irish-language spelling is of course quite different, but even then I

Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-07 Thread Pádraig Brady
On 07/12/2019 04:10, Bruno Haible wrote: 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

Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-07 Thread Bruno Haible
Pádraig Brady wrote: >It’s awkward for word regex to use right quote (\u2019) >Itʼs best to use apostrophe modifier (\u02BC) Unicode.org recommends: * U+2019 is the preferred character for a punctuation apostrophe, * U+02BC is a glottal stop, used by many languages as a letter of

Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-06 Thread Bruno Haible
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

Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-06 Thread Paul Eggert
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

Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-06 Thread Wes Hurd
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

Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-06 Thread Florian Weimer
* 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

Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-05 Thread Paul Eggert
On 12/5/19 7:12 AM, Wes Hurd wrote: Smart quotes are dangerous for programmers and technical users Sure, but *all* quotes are dangerous for programmers and technical users. :-) If you don’t want smart quotes, you can set LC_ALL=C in your environment.

Re: GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-05 Thread 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 output. > > Originally

GNUlib unicode encoding causes smart quotes to be displayed in program's output

2019-12-05 Thread Wes Hurd
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 output. Originally noticed with wget -