The following color-coded matrix describes the current extent of support for various features in AbiWord. There's an explanation of the text in each cell at the bottom of this document.

Legend

To tell if a particular feature is complete across the entire product, look across that row. Likewise, to tell if a particular portion of the product is completely up to date, look down that column.

C PROPS

1. Waiting for the creation of a well-defined focus model to allow keyboard traversal of toolbar combo boxes.
2. Underline works in LaTeX, but strikeout doesn't.

P PROPS

	View	Dialog	Keyboard	Toolbar	AbiWord	RTF	doc	htm	txt	docbook	LaTeX
text-align	yes	(1)	yes	yes	i,e	i,e	i	e	n/a		(8)
line-height	yes	yes	yes	yes	i,e	(2)	i	n/a	n/a		e
orphans	yes	yes	n/a	n/a	i,e	e omly	no	n/a	n/a		no
widows	yes	yes	n/a	n/a	i,e	e only	no	n/a	n/a		no
keep-together	#653	yes	n/a	n/a	i,e	(5)	i	n/a	n/a		no
keep-with-next	no	(4)	n/a	n/a	(7)	(7)	(7)	n/a	n/a		no
margin-top	yes	yes	n/a	yes	i,e	i,e	i	n/a	n/a		no
margin-left	yes	yes	n/a	yes	i,e	#590	i	n/a	n/a		no
margin-right	yes	yes	n/a	yes	i,e	#590	i	n/a	n/a		no
margin-bottom	yes	yes	n/a	n/a	i,e	i,e	i	n/a	n/a		no
text-indent	yes	yes	n/a	yes	i,e	#590	i	n/a	n/a		no
tabstops	(3)	no	n/a	yes	(3)	(3)	no	n/a	n/a		no
default-tab-interval	yes	no	n/a	n/a	i,e	(6)	(6)	n/a	n/a		no
background-color	v2.0	v2.0	v2.0	v2.0	v2.0	v2.0	v2.0	v2.0	n/a		v2.0

1. Paragraph dialog still doesn't have tri-state drop-downs
2. RTF import of line spacing works, but tool bar controls don't recognize the spacing.
3. Only left align tabs are supported
4. The option is in the paragraph dialog, but it doesn't do anything.
5. Does RTF even support this? Perhaps this should be n/a instead?
6. Word changes tab stop on a document level, not paragraph level, so it is unclear this can be supported
7. This can't be effectively tested until AbiWord actually supports it in the view
8. Right-align and center work. Left-align and full produce no TeX command, and the result is full.

Section PROPS

	View	Dialog	Keyboard	Toolbar	AbiWord	RTF	doc	htm	txt	Docbook	LaTeX
columns	yes	no	n/a	yes	i,e	i,e	i	n/a	n/a		e
column-gap	yes	no	n/a	yes	i,e	no	i	n/a	n/a		(2)
section-space-after	use	no	n/a	n/a	i,e	(1)	(1)	n/a	n/a		(3)
page-margin-top	use	no	n/a	no	i,e	no	i	no	n/a		no
page-margin-left	use	no	n/a	no	i,e	no	i	no	n/a		no
page-margin-right	use	no	n/a	no	i,e	no	i	no	n/a
page-margin-bottom	use	no	n/a	no	i,e	no	i	no	n/a		no

1. RTF and Word do not support this attribute as far as I can tell.
2. Column gap produces a mishmash of overstrike. So does column break.
3. Section space produces one column followed by two columns, as it should, but there is no 3-line space.

Breaks

	View	Dialog	Keyboard	Toolbar	AbiWord	RTF	doc	htm	txt	Docbook	LaTeX
br (Line break)	yes	n/a	(2)	n/a	i,e	i,e	i	#629	e		e
cbr (Column break)	yes	yes	(2)	n/a	i,e	e only	i	n/a	n/a		(3)
pbr (Page break)	ues	yes	(2)	n/a	i,e	i,e	i	n/a	n/a		e
Section (Section break)	(1)	(1)	(2)	n/a	i,e	i,e	i	n/a	n/a		e

1. Odd/even page breaks not implemented yet
2. Needs documentation
3. Column break produces a mishmash of overstrike.

Image

	View	Dialog	Keyboard	Toolbar	AbiWord	RTF	doc	htm	txt	docbook	LaTeX
image	PNG only	yes	n/a	n/a	i,e	e only	no	#564	n/a		no
image dataid	PNG only	yes	n/a	n/a	i,e	e only	no	#564	n/a
height	(1)	no	n/a	n/a	i,e	no	no	#564	n/a		no
width	(1)	no	n/a	n/a	i,e	no	no	#564	n/a		no

1. Interactive editing of image height and width is not planeed for version 1.0

Data

	View	Dialog	Keyboard	Toolbar	AbiWord	RTF	doc	htm	txt	docbook	LaTeX
data	PNG only	yes	n/a?	n/a	i,e	e only	no	#564	n/a		no
d name	PNG only	yes	n/a?	n/a	i,e	e only	no	#564	n/a		no

Styles

1. Custom styles are not listed in toolbar yet.
2. Style information is collapsed into explicit properties, instead of defining and referencing the underlying styles.
3. Waiting for the creation of a well-defined focus model to allow keyboard traversal of toolbar combo boxes.

Field

	View	Dialog	Keyboard	Toolbar	AbiWord	RTF	doc	htm	txt	docbook	LaTeX
field	(1)	i,e	no	n/a	i,e	#635	#634	no	#636		(2)

1. More field types need to be spec-ed and implemented.
2. The fields exported blank, even though they had text in them.

Other features

1. The Word import engine can handle lists and tables, but AbiWord doesn't know what to do with them.
2. We might wish to convert table boundaries to tab stops as interim solution

CHARACTER SETS