Joel Baker <[EMAIL PROTECTED]> writes:
> Thus, unless you're using "high characters" not defined in US-ASCII, all
> of the following three statements are true:
>
> 1) It is a valid US-ASCII file
> 2) It is a valid ISO-8859-1 file
More generally, it's valid (and will appear identical) in any of th
Joel Baker <[EMAIL PROTECTED]> writes:
> Thus, unless you're using "high characters" not defined in US-ASCII, all
> of the following three statements are true:
>
> 1) It is a valid US-ASCII file
> 2) It is a valid ISO-8859-1 file
More generally, it's valid (and will appear identical) in any of th
Hi, Stephen Gran wrote:
> Just a quick question about encoding changelog in utf-8. My normal
> locale is iso-8859-1 (en_US or so, I guess), and `file changelog`
> returns 'ASCII text'.
Note that "file" doesn't look at the whole file, so it may miss non-ASCII
characters if they're not at the begi
This one time, at band camp, Joel Baker said:
> US-ASCII only defines characters from 0x00 through 0x7F (0 - 127); it is a
> formal subset of both ISO-8859-1 (Latin-1) and UTF-8. Or, more precisely,
> both Latin-1 and UTF-8 are proper supersets of US-ASCII, largely to prevent
> being gratuitously b
On Mon, Aug 04, 2003 at 01:15:07PM -0400, Stephen Gran wrote:
> Hello all,
>
> Just a quick question about encoding changelog in utf-8. My normal
> locale is iso-8859-1 (en_US or so, I guess), and `file changelog`
> returns 'ASCII text'. I tried
> `iconv -f ISO-8859-1 -t utf8 changelog -o chang
Hi, Stephen Gran wrote:
> Just a quick question about encoding changelog in utf-8. My normal
> locale is iso-8859-1 (en_US or so, I guess), and `file changelog`
> returns 'ASCII text'.
Note that "file" doesn't look at the whole file, so it may miss non-ASCII
characters if they're not at the begi
This one time, at band camp, Joel Baker said:
> US-ASCII only defines characters from 0x00 through 0x7F (0 - 127); it is a
> formal subset of both ISO-8859-1 (Latin-1) and UTF-8. Or, more precisely,
> both Latin-1 and UTF-8 are proper supersets of US-ASCII, largely to prevent
> being gratuitously b
On Mon, Aug 04, 2003 at 01:15:07PM -0400, Stephen Gran wrote:
> Hello all,
>
> Just a quick question about encoding changelog in utf-8. My normal
> locale is iso-8859-1 (en_US or so, I guess), and `file changelog`
> returns 'ASCII text'. I tried
> `iconv -f ISO-8859-1 -t utf8 changelog -o chang
On Mon, Aug 04, 2003 at 01:15:07PM -0400, Stephen Gran wrote:
> Just a quick question about encoding changelog in utf-8. My normal
> locale is iso-8859-1 (en_US or so, I guess), and `file changelog`
> returns 'ASCII text'. I tried
> `iconv -f ISO-8859-1 -t utf8 changelog -o changelog.new`, but t
This one time, at band camp, Mike Hommey said:
> On Monday 04 August 2003 19:15, Stephen Gran wrote:
> [snip]
> > As you can probably tell, I am not that familiar with the issues around
> > utf-8, but my impression was that it is a superset of ASCII, so if I
> > only use ASCII characters, it should
On Monday 04 August 2003 19:15, Stephen Gran wrote:
[snip]
> As you can probably tell, I am not that familiar with the issues around
> utf-8, but my impression was that it is a superset of ASCII, so if I
> only use ASCII characters, it should be fine.
You are perfectly right.
--
"I have sampled
Hello all,
Just a quick question about encoding changelog in utf-8. My normal
locale is iso-8859-1 (en_US or so, I guess), and `file changelog`
returns 'ASCII text'. I tried
`iconv -f ISO-8859-1 -t utf8 changelog -o changelog.new`, but then
`file changelog.new` returns 'ASCII text' again, and
On Mon, Aug 04, 2003 at 01:15:07PM -0400, Stephen Gran wrote:
> Just a quick question about encoding changelog in utf-8. My normal
> locale is iso-8859-1 (en_US or so, I guess), and `file changelog`
> returns 'ASCII text'. I tried
> `iconv -f ISO-8859-1 -t utf8 changelog -o changelog.new`, but t
This one time, at band camp, Mike Hommey said:
> On Monday 04 August 2003 19:15, Stephen Gran wrote:
> [snip]
> > As you can probably tell, I am not that familiar with the issues around
> > utf-8, but my impression was that it is a superset of ASCII, so if I
> > only use ASCII characters, it should
On Monday 04 August 2003 19:15, Stephen Gran wrote:
[snip]
> As you can probably tell, I am not that familiar with the issues around
> utf-8, but my impression was that it is a superset of ASCII, so if I
> only use ASCII characters, it should be fine.
You are perfectly right.
--
"I have sampled
Hello all,
Just a quick question about encoding changelog in utf-8. My normal
locale is iso-8859-1 (en_US or so, I guess), and `file changelog`
returns 'ASCII text'. I tried
`iconv -f ISO-8859-1 -t utf8 changelog -o changelog.new`, but then
`file changelog.new` returns 'ASCII text' again, and
16 matches
Mail list logo