Abiword doesn't have a button for "default color" for font

[gpk]

Binary package hint: abiword

Once you colorize some text, you cannot ever quite return it to the original state. That's because there is no button for "default text color" like there is for "clear highlighting". When you go back to black, you go back to a black that over-rides the style. That means the output xml looks like this:

<p style="Normal" xid="2"><c>One</c><c props="color:000000"> two </c><c>three.</c></p>

Even though, to the unaided eye, all the words are identically black.

This has some bad side-effects. First of all, it means your document progressively gets fragmented into smaller and smaller chunks if you use font colors during collaborative editing. And *that* means you cannot merge these fragments, and *that* means that the saved file is bigger than it ought to be.

I attach an abiword file containing words "One two three." I had changed the font color on "two" then changed it back to black.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: abiword 2.8.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-23.37-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
Date: Sat Nov 13 14:59:45 2010
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: abiword

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

This bug has been reported to the developers of the software. You can track it and make comments at: http://bugzilla.abisource.com/show_bug.cgi?id=12946

Thanks for taking the time to make Ubuntu better!

[Charlie Kravetz (cjkgeek)]

http://bugzilla.abisource.com/show_bug.cgi?id=12946 has been marked a duplicate of http://bugzilla.abisource.com/show_bug.cgi?id=247

[Simon Quigley (tsimonq2)]

Thank you for reporting this bug to Ubuntu. Ubuntu 10.10 reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

I've tried recreating this bug with your release and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.