feature_matrix[1].htm /update

Tue, 04 Dec 2001 09:22:01 -0800 

Hello
This is regarding:
http://bugzilla.abisource.com/show_bug.cgi?id=2276
I've modified the matrix to show current implementation status of docbook in
abiword.

I'll try to fill in the features I find as I go.

Please look at my work and confirm for upating on the site.

It would be nice if I turn off the colors or find another way of indicating
status but...hey it's a great matrix! One of the few I've seen now that I
think about it!
Keep up the good work!
Dennis


 feature_matrix[1].htm
Title: AbiSource feature details

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

 This feature is done.
 This feature is not planned for 1.0. If you send us code, you will change our minds.
  This feature is partially done, but needs work
  This feature is done, but is too bug-ridden to be usable
  This feature is not implemented
 Unknown, because [EMAIL PROTECTED] hasn't "officially" tested it yet.
  Not applicable

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

View Dialog Keyboard Toolbar AbiWord RTF doc htm txt docbook LaTeX
color yes yes n/a v2.0 i,e i,e i e n/a   no
font-family yes yes (1) yes i,e i,e i e n/a   no
font-style yes yes yes yes i,e i,e i e n/a   e
font-weight yes yes yes yes i,e i,e i e n/a   e
font-size yes yes (1) yes i,e i,e i e n/a   e
text-decoration yes yes yes yes i,e i,e i e n/a   (2)
text-position yes yes yes yes i,e i,e i e n/a   e
font-variant v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 n/a   v2.0
font-stretch v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 n/a   v2.0
  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

View Dialog Keyboard Toolbar AbiWord RTF doc htm txt docbook LaTeX
style yes no (3) (1) i,e (2) (2) e n/a    
p style= yes no n/a (1) i,e (2) (2) e n/a   e
s name= yes no n/a (1) i,e (2) (2) e n/a    
s props= yes oo n/a (1) i,e #590 (2) #461 n/a    
s basedon= yes no n/a (1) i,e   (2) #461 n/a    
s followedby= v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 v2.0 n/a    

  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

View Dialog Keyboard Toolbar AbiWord RTF doc htm txt docbook LaTeX
(headers) use no no no i,e no no n/a n/a   no
(footers) use no mo no i,e no no n/a n/a   no
(lists) no no no no no no (1) no      
(tables) v2.0 v2.0 v2.0 v2.0 v2.0 (2) (1) v2.0 n/a   v2.0

  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

View Dialog Keyboard Toolbar AbiWord RTF doc htm txt Docbook LaTeX
Latin-1 yes n/a yes n/a yes           e
Latin Extended yes n/a yes n/a yes           no
Greek yes n/a yes n/a yes           no
Cyrillic yes n/a yes n/a yes           no
Hebrew   n/a   n/a             no
Arabic   n/a   n/a             no
Nagari   n/a   n/a             no
Thai   n/a   n/a             no
Hàn Zì   n/a   n/a             no
Kana   n/a   n/a             no
Hangul   n/a   n/a             no
Accented width same   n/a   n/a             e

Explanation of language

  • view -- The feature's complete when the user can "edit" it through our UI. However, there are many half-implemented features where the view can only "use" the information if it gets into the file some other way, such as by hand-editing the file.
  • Dialog -- Do we have a complete dialog up for this? (yes, no)
  • Keyboard -- Is there a corresponding keyboard shortcut? (yes, no, or n/a)
  • Toolbar -- Again, this is mostly a yes/no question, although for things which go in combo boxes (such as font, style, and zoom), it can get more complex. Read-only lists are easy to do. Editable ones take more design work to get right.
  • abw, rtf, doc -- Here, the idea is to make sure that we can both import and export (i,e) the information properly.
  • htm, txt, LaTeX -- Ditto, except these formats are export only or lossy, so "n/a" is sometimes an option.
Last edited September 4, 2000
LaTeX tested by Pierre Abbat on code downloaded August 24, 2000, from CVS

Reply via email to