Hi Bernd, On Wednesday, 2007-11-14 10:06:21 +0100, Bernd Eilers wrote:
>> Seconded. The "dirty" in the fall-back is that it doesn't preserve >> formatting ;-) i.e. the text written should be surrounded by <pre> tags, >> e.g. see i74918 in http://development.openoffice.org/releases/2.3.0.html > > Oh no Eike, that´s just a missing Feature on my side which I would need to > fix ;-) Fine :) > What I consider bad on using this fallback is the problem that the > feature-info is often to technical to be used for the release notes, eg. > it´s often mentioning stuff like ChildWorkspaces where something got > integrated etc. which the end user doesn´t know about what this is but > well that may be only my impression. That's a matter of education then. Developers should get acquainted with the idea that feature announcements should be written such that they're end user compatible ;-) We could also agree on something like tagged sections, such as a [technical] blah here [/technical] would not be included in a compilation of feature announcements. Using square brackets instead of angle brackets would prevent confusion with HTML tags if the text is to be included in some HTML page like a wiki or such. The EIS form could actively support that by offering two textareas, one description for users, one technical. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Use [EMAIL PROTECTED] Thanks.
pgpBYBm4W741p.pgp
Description: PGP signature
