> On Wed, Apr 01, 2015 at 07:54:27AM +0200, Roberto E. Vargas Caballero wrote:
>>>So my non-ASCII characters look incorrect in your MUA because you're
>>>stuck in an insane locale? Too bad. That pain is self-inflicted.
>>
>> Don't blame me, I'm not the one who created all those funky European
>>
Feel free to submit a setlocale() patch to be added to the
wiki for sbase.
>>So my non-ASCII characters look incorrect in your MUA because you're
>>stuck in an insane locale? Too bad. That pain is self-inflicted.
>
> Don't blame me, I'm not the one who created all those funky European accented
> characters, etc.
All these 'funky' characters predate to the first english
> > On 31 March 2015 at 00:13, Roger wrote:
> > > But anyways, think I made my point.
> >
> On Tue, Mar 31, 2015 at 12:17:48AM +0100, Connor Lane Smith wrote:
> > You did: you only care for whatever encoding you personally need over
> > there in America. Most of us, however, are from Europe, do ne
> On Tue, Mar 31, 2015 at 12:17:48AM +0100, Connor Lane Smith wrote:
>On 31 March 2015 at 00:13, Roger wrote:
>> But anyways, think I made my point.
>
>You did: you only care for whatever encoding you personally need over
>there in America. Most of us, however, are from Europe, do need UTF-8,
>and
>So my non-ASCII characters look incorrect in your MUA because you're
>stuck in an insane locale? Too bad. That pain is self-inflicted.
Don't blame me, I'm not the one who created all those funky European accented
characters, etc.
Just wait for ASCIII.
Really within the English language, there'
> On Tue, Mar 31, 2015 at 01:30:04AM +0200, FRIGN wrote:
>On Mon, 30 Mar 2015 19:09:41 -0400
>Roger wrote:
>
>Hey Roger,
>
>> I thought non-ASCII characters required 16 bits within UTF-8, versus just 8
>> bits for ASCII. Therefore more memory. More memory referencing, requires
>> more
>> proc
On Tue, 31 Mar 2015 09:08:28 -0400
Greg Reagle wrote:
> I am a big fan of the ISO 8601 date format: today would be 2015-03-31.
> It sorts dates properly and goes from largest unit of time to smallest
> (year then month then day). I think it would be fine for the suckless
> tools to support only
Somebody wrote:
> > I agree there should be localized date-formats,
I am a big fan of the ISO 8601 date format: today would be 2015-03-31.
It sorts dates properly and goes from largest unit of time to smallest
(year then month then day). I think it would be fine for the suckless
tools to support
On 30 March 2015 at 20:33, FRIGN wrote:
> On Mon, 30 Mar 2015 19:05:19 +0200
> Markus Wichmann wrote:
>
>> How about simply calling setlocale()? Or was that too simple? If the
>> user has set a non-UTF-8 locale and then uses UTF-8, that's on them!
>
> POSIX locales are an insane concept. Unicode
On Mon, Mar 30, 2015 at 07:09:41PM -0400, Roger wrote:
> I thought non-ASCII characters required 16 bits within UTF-8, versus
> just 8 bits for ASCII.
1. ASCII is a 7-bit encoding that we store in 8-bit bytes.
2. You don't encode non-ASCII with ASCII. That seems to be your logic.
"I thought non
On Mon, 30 Mar 2015 19:09:41 -0400
Roger wrote:
Hey Roger,
> I thought non-ASCII characters required 16 bits within UTF-8, versus just 8
> bits for ASCII. Therefore more memory. More memory referencing, requires
> more
> processing.
I can't take you seriously, sorry. UTF-8 is the future, t
On 31 March 2015 at 00:13, Roger wrote:
> But anyways, think I made my point.
You did: you only care for whatever encoding you personally need over
there in America. Most of us, however, are from Europe, do need UTF-8,
and reckon you can piss off.
cls
> On Mon, Mar 30, 2015 at 04:01:32PM -0700, Eric Pruitt wrote:
>On Mon, Mar 30, 2015 at 06:57:55PM -0400, Roger wrote:
>> >We do however need to use English currency. ?? ain't ASCII.
>>
>> I would presume that was the old deprecated cents sign which was apparently
>> deprecated within the US during
>> Less chars equals less processor and memory usage. ;-)
>
>If you use ASCII-chars only, UTF-8 will be 0 overhead. I repeat: 0 overhead.
I thought non-ASCII characters required 16 bits within UTF-8, versus just 8
bits for ASCII. Therefore more memory. More memory referencing, requires more
pr
On Mon, Mar 30, 2015 at 06:57:55PM -0400, Roger wrote:
> >We do however need to use English currency. ?? ain't ASCII.
>
> I would presume that was the old deprecated cents sign which was apparently
> deprecated within the US during the late 1990's.
It was not, it's the symbol for the pound sterlin
> On Mon, Mar 30, 2015 at 10:32:01PM +0100, Connor Lane Smith wrote:
>On 30 March 2015 at 22:28, Roger wrote:
>> No need for funky apostrophe usage within the English language.
>
>We do however need to use English currency. ?? ain't ASCII.
I would presume that was the old deprecated cents sign wh
On Mon, 30 Mar 2015 17:28:45 -0400
Roger wrote:
> I recently fell back to using only ASCII (or C/POSIX), as I realized I do not
> use any UTF-8 chars, etc. (Eh, Windows now uses UTF-16 by default from what
> I
> hear, and I don't even speak any Asian languages!)
This is the wrong way to go.
On 30 March 2015 at 22:28, Roger wrote:
> No need for funky apostrophe usage within the English language.
We do however need to use English currency. £ ain't ASCII.
cls
> On Mon, Mar 30, 2015 at 08:33:48PM +0200, FRIGN wrote:
>On Mon, 30 Mar 2015 19:05:19 +0200
>Markus Wichmann wrote:
>
>> How about simply calling setlocale()? Or was that too simple? If the
>> user has set a non-UTF-8 locale and then uses UTF-8, that's on them!
>
>POSIX locales are an insane conc
Connor Lane Smith once said:
> On 30/03/2015, FRIGN wrote:
> > In the end, the idea of locales is founded in some deeply-resting issue
> > with self-guilt, assuming there's some African tribe which sorts ö after
> > x.
>
> They're called Swedes.
A long time ago they were an African tribe.
An
On 30/03/2015, FRIGN wrote:
> In the end, the idea of locales is founded in some deeply-resting issue
> with self-guilt, assuming there's some African tribe which sorts ö after
> x.
They're called Swedes.
cls
On Mon, 30 Mar 2015 21:13:11 +0200
Markus Wichmann wrote:
Hey Markus,
> How? I heard that assertion before but never found anyone willing to
> explain that one more.
> (...)
> Unfortunately, your oppinion on that will have to contend with all the
> other ones on the topic. And stuff like this is
On Mon, Mar 30, 2015 at 08:33:48PM +0200, FRIGN wrote:
> On Mon, 30 Mar 2015 19:05:19 +0200
> Markus Wichmann wrote:
>
> > How about simply calling setlocale()? Or was that too simple? If the
> > user has set a non-UTF-8 locale and then uses UTF-8, that's on them!
>
> POSIX locales are an insane
On Mon, Mar 30, 2015, at 02:33 PM, FRIGN wrote:
> POSIX locales are an insane concept.
> The idea of localized differences has its origin in the
> sick minds of the POSIX-authors.
Don't be so diplomatic. How do you really feel?
--
http://www.fastmail.com - Choose from over 50 domains or use yo
On Mon, 30 Mar 2015 19:05:19 +0200
Markus Wichmann wrote:
> How about simply calling setlocale()? Or was that too simple? If the
> user has set a non-UTF-8 locale and then uses UTF-8, that's on them!
POSIX locales are an insane concept. Unicode has already gone a long
way to define sane internat
On Mon, Mar 30, 2015 at 08:50:11AM -0700, Evan Gates wrote:
> The problem is using glibc's regex engine without first calling
> setlocale to ensure a UTF-8 locale. This causes it to remain in the
> C/POSIX locale. This will effect the same problem in all tools that
> use the libc's regex engine (ex
On Sat, Mar 28, 2015 at 2:04 PM, Dimitris Papastamos wrote:
> On Sat, Mar 28, 2015 at 09:48:08PM +0100, isabella parakiss wrote:
>> Please fix
>>
>> $ sed 's/[à]/x/' <<< è
>> x¨
>
> Interestingly, sbase sed linked with musl gives the correct result.
>
> Will look into it.
>
The problem is using g
On Sat, Mar 28, 2015 at 09:48:08PM +0100, isabella parakiss wrote:
> Please fix
>
> $ sed 's/[à]/x/' <<< è
> x¨
Interestingly, sbase sed linked with musl gives the correct result.
Will look into it.
Please fix
$ sed 's/[à]/x/' <<< è
x¨
---
xoxo iza
30 matches
Mail list logo
