Apache OpenOffice (AOO) Bugzilla – Issue 97515
Refactor sc and svx to prepare for Excel export encryption and sheet protection support
Last modified: 2013-08-07 15:14:30 UTC
We need to refactor sc and svx modules in order to prepare for the future integration of Excel export encryption and sheet protection options support. This change should not affect or alter any existing functionalities.
adding dr in the CC & set dependencies.
I'm taking ownership.
started.
set target to 3.1
fixed in the scsheetprotection02 cws just now. I've done the following stuff to revert to the current behavior: * disabled "Save with password" option for Excel export. * disabled the new sheet protection dialog when protecting a sheet, and switched back to the current simple password dialog. * when saving an encrypted excel document, resurrected the old password warning dialog and cleared the document password (if any), so that the document would get saved *un*-encrypted *without* password. * when importing an Excel document with document structure protection and/or sheet protection with password, deliberately forget the password(s). So, when such an Excel document is opened in Calc, you can easily unprotect the respective protection even without being prompted for a password. * when exporting to an Excel document with document structure protection and/or sheet protection with password, deliberately forget the password(s). When such a document is subsequently opened in Excel, you can easily unprotect the respective protection even without being prompted for a password. Basically, this change should not change any existing behavior.
Just an implementation note. Re-enabling the features implemented in the scsheetprotection02 should be as easy as * setting ENABLE_SHEET_PROTECTION from 0 to 1 in sc/inc/tabprotection.hxx, and * removing the #if 0 #endif from the CheckPasswordCapability function object in sfx2/source/dialog/filedlghelper.cxx.
verified in internal build cws_scsheetprotection02
set target to 3.2 as we don't want to split this (code changes now, strings later) and we'll only loose one or two weeks with the integration because release engineering is branching the versions (3.1 to 3.2)
Actually, this issue has already been verified... I'll re-assign to oc again just in case we need to verify this again (since it's a much more recent milestone). If not, just set this back to verified fixed.
testet with OOO320m12 and Excel 2007 SP2