W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: [widgets] Zip endian issue?

From: Marcos Caceres <marcosc@opera.com>
Date: Wed, 8 Apr 2009 19:27:20 +0200
Message-ID: <b21a10670904081027u20944acck2c66e23434ba8ea4@mail.gmail.com>
To: Jere.Kapyaho@nokia.com, "timeless.bmo1@gmail.com" <timeless@gmail.com>
Cc: public-webapps@w3.org
On Fri, Apr 3, 2009 at 11:17 AM,  <Jere.Kapyaho@nokia.com> wrote:
> Well,
>
> the ZIP file specification does say that all values are stored in
> little-endian byte order unless otherwise specified. The local file header
> signature is the four bytes 50 4B 03 04, in this order, always. Endianness
> is not even an issue, if you read and compare individual bytes.
>
> How could the ZIP file “be entirely transposed on media”? It is a binary
> file; if some entity is “transposing” it, it’s not the same file anymore. A
> practical example of where and how this would be happening is needed.

I guess that unless we come up with a realistic scenario, this is a
non-issue. Josh?

Kind regards,
Marcos

-- 
Marcos Caceres
http://datadriven.com.au
Received on Wednesday, 8 April 2009 17:28:22 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT