Frank Schönheit - Sun Microsystems Germany wrote:
Hi Bernd,
Hi Frank,
Just have a look at
http://development.openoffice.org/releases/2.3.0.html to get an
impression, these are the actucal release notes for the 2.3.0 user Release.
And that´s the result of what we currently semi-automatically generated
for the 2.0.3 Release by parsing (or not being able to parse)
specification documents.
Out of curiosity: What will the automatisms do with
http://www.openoffice.org/servlets/ReadMsg?list=allfeatures&msgNo=3270?
It has become a habit (rightfully so) to extend existing extensions when
the respective feature evolves, and to put the URL of the complete
specification into the feature mail. Does this mean our release notes
will contain the abstract of the complete specification?
Well yes it´s a rather simple algorithm and well normally your
expectation would be right that in this case the text from the first
paragraph of the abstract would be used. But well here it´s special. The
spec document has been changed in a way that the abstract can not be
extracted anymore because the "abstract" headline has been changed by
adding a 1) Footnote to it which brakes the process. So here the
fallback to use the feature info will be in place.
See:
<https://eis.services.openoffice.org/EIS2/guide.CheckSpecification?url=http://specs.openoffice.org/appwide/security/Electronic_Signatures_and_Security.sxw>
Ciao
Frank
Ciao,
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
