Re: UTF-8 support for colrm(1)

Stephane Chazelas wrote: |2016-01-11 16:10:28 +0100, Steffen Nurpmeso: |[...] |> And your diff includes |> |> +.Pp |> +For compatibility with |> +.St -p1003.1-2008 |> +.Xr fold 1 , |> +if a double-width character is followed by two backspace

Re: UTF-8 support for colrm(1)

2016-01-11 16:10:28 +0100, Steffen Nurpmeso: [...] > And your diff includes > > +.Pp > +For compatibility with > +.St -p1003.1-2008 > +.Xr fold 1 , > +if a double-width character is followed by two backspace characters > +instead of the usual one, both are regarded as belonging to

Re: UTF-8 support for colrm(1)

2016-01-11 15:50:55 +, Stephane Chazelas: [...] > $ printf '|\uFF21\b\b|\n' > || > $ printf '|\uFF21\b|\n' > | | > > in both xterm and gnome-terminal. As in, you need two backspace > characters to delete that character. With only one, the cursor > moves back one column, and if you write

Re: UTF-8 support for colrm(1)

Hallo Ingo, i CC: the POSIX list since that is an interesting conclusion of yours! Ingo Schwarze wrote: |Ingo Schwarze wrote on Wed, Dec 23, 2015 at 07:44:05PM +0100: |>>> For example, colrm(1). |> So, remember this rule: |> |>

Re: UTF-8 support for colrm(1)

Hi, Ingo Schwarze wrote on Wed, Dec 23, 2015 at 07:44:05PM +0100: > Steffen Nurpmeso wrote on Wed, Dec 23, 2015 at 11:45:36AM +0100: >> Ingo Schwarze wrote: >>> For example, colrm(1). [Regarding one of the various bugs in FreeBSD:] >>> 4. The backspace character (U+0008)

Re: UTF-8 support for colrm(1)

Hi Steffen, Steffen Nurpmeso wrote on Wed, Dec 23, 2015 at 11:45:36AM +0100: > Ingo Schwarze wrote: >> For example, colrm(1). >> >> 4. The backspace character (U+0008) backs up by one display position >>rather than by one character. That causes miscounting when >>

Re: UTF-8 support for colrm(1)

Ingo Schwarze wrote: |Steffen Nurpmeso wrote on Wed, Dec 23, 2015 at 11:45:36AM +0100: |> Ingo Schwarze wrote: |>> For example, colrm(1). |>> |>> 4. The backspace character (U+0008) backs up by one display position |>>rather than by one character.

Re: UTF-8 support for colrm(1)

Hello Ingo, Ingo Schwarze wrote: |For example, colrm(1). |4. The backspace character (U+0008) backs up by one display position | rather than by one character. That causes miscounting when | backspace follows a zero-width or double-width character. this however is

UTF-8 support for colrm(1)

Hi, the most important small base system utilities fixed with respect to the most important UTF-8 issues (or at least having patches on tech@), i still didn't encounter a single case where a function written for one utility could be reused in another. So before tackling larger beasts like shells