>> ... I really wish the MS Word export with password protection was there!
>> I was hoping to convert my organization over to OOo, but they are used
>> to using MS Word passwords to "protect" sensitive documents. Not that
>> the protection is any good, but that's what OOo would have to
>> interoperate with in order to get management approval.
Well i think you have answered your own question, move to a more secure
encryption system and implement Open Office while at same time leaving
the MS Word in place just as a legacy app for reading old docs.
Oh, come on!!
His request is perfectly reasonable. I too am happy to see OOo able to
open MS password protected files. How [EMAIL PROTECTED] hard would it be to add
support for their lame password in the 'Saved As' version of a .doc file
too? Sometimes it seems to me that (some of) the OOo devs go out of
their way to be difficult, just to make some kind of political 'point'
similar to the one you tried to make above.
Perhaps you could contribute this feature to the codebase. I would thank
you and so would thousands of others.
Bite me Roderick. Typical elitist nonsense. Anyone who knows anything
about programming, and has even given the OOo codebase a *cursory*
looksee, knows that writing anything more than a simple plug-in or macro
is something that is difficult to the *extreme*, and would require a
level of commitment (time and effort just in learning enough about the
code just to get to the point where they *might* be able to *begin* to
be productive) not possible to someone who is not being paid by SUN (or
someone else).
The fact is, the programmers *did* write the code enabling OOo to *open*
a MS password protected document. The fact is, they could *just* as
easily written the code to allow it to *save* it in reverse. They
*chose* not to do so - most likely for *political* reasons.
How [EMAIL PROTECTED] hard would it be to add support for their lame password in
the 'Saved As' version of a .doc file
a) The US has this stupid law known as the DMCA, which , for all
practical purposes, defines ROT-13 as "a secure encryption scheme".
b) Writing and distribution code that breaks that "secure encryption
scheme", can be prosecuted under current us law as a felony.
rot, and more rot. This is the same tired excuse that they used to not
support *opening* password protected files in OOo1. The legal argument
was easily demonstrated to be flawed, just as this application of it.
The DMCA *in* *no* *way* prevents OOo from doing this - that is just an
excuse.
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
