On 6/26/18, Michael Enright wrote:
> On Mon, Jun 25, 2018 at 11:33 AM, Lee wrote:
>> I'm still trying to figure utf-8 out, but it seems to me that 0x0 -
>> 0xff is part of the utf-8 encoding.
>
> I don't see how you arrived at this.
I screwed up trying to do hex in my head. For whatever reason
On 6/26/18, Thomas Wolff wrote:
> This encoding scheme is wrong; where did you get it from? Maybe it's the
> obsolete UTF-8...
http://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt
I thought I saw something about utf-8 being able to handle a 31 bit
value.. is that also obsolete/wrong?
how abou
On Mon, Jun 25, 2018 at 11:33 AM, Lee wrote:
> I'm still trying to figure utf-8 out, but it seems to me that 0x0 -
> 0xff is part of the utf-8 encoding.
I don't see how you arrived at this. An initial byte of 0xFF is not
the initial byte of any valid UTF-8 byte sequence. And it doesn't
conform wi
Am 25.06.2018 um 20:33 schrieb Lee:
On 6/24/18, L A Walsh wrote:
Lee wrote:
So... keep it simple, set
LANG=en_US.UTF-8
and use vi or something else that comes with cygwin to create the file
and I'll have a file with UTF-8 character encoding - correct?
---
The first 127 chara
On 6/24/18, L A Walsh wrote:
> Lee wrote:
>> So... keep it simple, set
>> LANG=en_US.UTF-8
>> and use vi or something else that comes with cygwin to create the file
>> and I'll have a file with UTF-8 character encoding - correct?
> ---
> The first 12
Lee wrote:
So... keep it simple, set
LANG=en_US.UTF-8
and use vi or something else that comes with cygwin to create the file
and I'll have a file with UTF-8 character encoding - correct?
---
The first 127 characters of UTF-8 are identical to the
first 127 characters of ASCII
Greetings, Lee!
> On 6/20/18, Andrey Repin wrote:
>> Greetings, Lee!
>>
>>> I'm looking at
>>> https://cygwin.com/packaging-hint-files.html#pvr.hint
>>> and it starts off with
>>> Use UTF-8 character encoding.
>>
>>
On 6/20/18, Andrey Repin wrote:
> Greetings, Lee!
>
>> I'm looking at
>> https://cygwin.com/packaging-hint-files.html#pvr.hint
>> and it starts off with
>> Use UTF-8 character encoding.
>
>> How do I do that and how do I check that I actually did use
On Thu, 21 Jun 2018 12:12:39, Houder wrote:
> On Wed, 20 Jun 2018 14:09:59, Lee wrote:
> > I'm looking at
> > https://cygwin.com/packaging-hint-files.html#pvr.hint
> > and it starts off with
> > Use UTF-8 character encoding.
> >
> > How do I do tha
On Wed, 20 Jun 2018 14:09:59, Lee wrote:
> I'm looking at
> https://cygwin.com/packaging-hint-files.html#pvr.hint
> and it starts off with
> Use UTF-8 character encoding.
>
> How do I do that and how do I check that I actually did use UTF-8
> character encoding _
Greetings, Lee!
> I'm looking at
> https://cygwin.com/packaging-hint-files.html#pvr.hint
> and it starts off with
> Use UTF-8 character encoding.
> How do I do that and how do I check that I actually did use UTF-8
> character encoding _without_ using file?
https:/
Am 20.06.2018 um 20:09 schrieb Lee:
> I'm looking at
> https://cygwin.com/packaging-hint-files.html#pvr.hint
> and it starts off with
> Use UTF-8 character encoding.
>
> How do I do that and how do I check that I actually did use UTF-8
> character encoding _wit
I'm looking at
https://cygwin.com/packaging-hint-files.html#pvr.hint
and it starts off with
Use UTF-8 character encoding.
How do I do that and how do I check that I actually did use UTF-8
character encoding _without_ using file?
for whatever it's worth:
$ file unicode.html
unicode.
13 matches
Mail list logo
