The specs are checked in CVS like the code; however there is no CWS
handling for them AFAIK. Perhaps you'd best change the document, attach
it to an issue and send it to me with mmp on CC. The correct component
for the issue would be "specs" I think.
As for making the properties bold: sure, why not ?
In general I'd say the correct people to contact is probably always the
owner/author of the spec. Someone from UX is also a good candidate IMHO.
Kind regards, pl
Giuseppe Castagno wrote:
> Hi all,
>
> while I was writing a macro using the OOo PDF export feature involving
> the use of PDF protection, I noticed that the specification [1] lacks
> the specific PDF security property value descriptions.
> Those are lurking here [2].
>
> I'd like to add that description in chapter 3 on the spec in order to
> have a single reference for all properties, without changing anything
> else in the spec.
>
> Another thing I'd like to do is to "bolden" the property names, just to
> make them stand out, though I don't know if this is something accepted
> in the current spec practice...
>
> What would be the best way of carrying it out?
> Open an issue? What component? ...
>
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
