Part 3, Section 2.4.1 regarding encryption

Section 2.4.2 currently contains this statement:

Each file entry that is encrypted shall be compressed with the "deflate" algorithm before being encrypted. Encrypted file entries shall be flagged as 'STORED' rather than 'DEFLATED' in the Zip file's central directory. The file entry's central directory records and its local file header both shall contain the compressed size of the file entry. The uncompressed size shall be contained in the manifest:size 3.8.13 attribute of the <manifest:file-entry> 3.3 element for the file entry.

There are two minor issues:
1. It say the file entry's central directory record and its local file header both should contain the compressed size. Actually this must be the size of the file after encryption. (Note for ODF 1.1, only Blowfish was supported and encryption did not change the size. So, in ODF 1.1 this statement was correct. But with teh support of other algorithms, the size may change.
2. Zip files have the option to store the size in a data descriptor that is behind the compressed data. The local file header in this case contain only a flag that the size can be found there. This is actually the way most implementations store the size. The current description however could be misunderstood to do not allow that. This is not intended, and should be clarified.