Hello!
I've just joined this list, so I apologize if this has been discussed before.
Today in #freebsd on FreeNode, I've asked whether there was any
particular reason why UTF-8 wasn't the default in FreeBSD yet.
What followed was a small discussion regarding this, and it seems that
there's a good
On 20 July 2016 at 16:07, Baptiste Daroussin wrote:
> On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote:
>> On 20 Jul 2016, at 9:13, Tim Čas wrote:
>>
>> > So, without further ado:
>> > 1) What are the reasons that UTF-8 isn't the default yet
On 20 July 2016 at 20:33, Don Lewis wrote:
> wc(1) has problems with its multibyte support pointed out by Coverity
> as I recall.
Not sure how critical that issue is (e.g. byte counts [`-c`], line
counts [`-l`], and such should still work as intended; whether word
counts work or not depends on wh
On 20 July 2016 at 22:23, Don Lewis wrote:
> It passes a fixed-length non-NUL terminated buffer (returned by read(2))
> to mbrtowc(). In addition to the lack of termination, the buffer could
> also contain a partial character at its beginning or end if the contents
> are UTF-8.
>
> The Coverity I
s otherwise not
broken --- well, at least where Coverity reported the issue.
On 21 July 2016 at 00:14, Tim Čas wrote:
> On 20 July 2016 at 22:23, Don Lewis wrote:
>> It passes a fixed-length non-NUL terminated buffer (returned by read(2))
>> to mbrtowc(). In addition to the lack
