Here are some specific ideas for fixing the issues raised. None are too hard:
> * .svg import (which does nothing but mess up documents for me) Disable .svg for 1.0 > * Smart quotes on Linux (the checkbox has no useful effect) Remove smart quotes checkbox from Linux build (don't show a broken control to the user). Hard map imported Windows characters to Linux alternatives (thus loading and saving a document with Linux changes the smart quotes back to normal quotes). See http://www.microsoft.com/globaldev/reference/WinCP.asp > * Styles (which are still a bit unpredictable) Fix previously reported "upredicable" bug. > * Bookmarks (which are, as far as I can tell, are invisible after insertion) Change menu "show paragrahps" to read "show markers". "show paragraphs" does not communicate that it will also show bookmarks. Fix rendering issues on Linux. > * Execute script (which just says ATTN: for me) "ATTN:" did not communicate to me "Scripting engine not installed". How about ghosting the icon if no scripting engine is installed? > Is image insertion really ready? The lack of .gif and .eps import are hard to take. > The inability to resize an image, or flow text around it, is a real downside. Finish resize image code. Allow images to be anchored to the PAGE. You can make your own image flow using the margin controls. Add .eps import. > * Autotext Ok, I just think Abi could do without this feature. Personal preference. > I think a review of the existing feature set for solidity and completeness would > be in order. No new functionality here, but ask if each subfeature works well > enough to call it 1.0. If not, fix it or disable it for 1.0. AbiWord has been >popular > with less features. IMHO a half baked feature does not belong in 1.0. Also consier: * Ghost the spellchecker menu if there is no dictionary loaded. DON'T just say that all words are spelled correctly! * Don't allow AbiWord fonts to mess up the system fontpath. * Have an EARLIER deadline for fixing all crashing bugs.
