Something inside me says "plain text". Keep it short, keep it simple, make it readable everywhere. The developers can provide info in Word, OO.org, text, e-mail, whatever.
If you have graphics or complex tables in your release notes, of course plain text won't do. But then why do you have graphics and complex tables in your release notes? Put the fancy stuff in the main docs where it belongs. Save the release notes for the real late-breaking information.
Plain and simple--come to think of it, that's what the girls at school used to call me...
Stuart ************************************************** To post a message to austechwriter, send the message to austechwriter@xxxxxxxxxxxxxx To subscribe to austechwriter, send a message to austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject field. To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field. To search the austechwriter archives, go to www.freelists.org/archives/austechwriter To contact the list administrator, send a message to austechwriter-admins@xxxxxxxxxxxxx **************************************************
