On 6/19/07, Bruce D'Arcus <> wrote:
On Jun 16, 2007, at 7:08 PM, wrote:
> This attribute does not work well with screen readers and the enhanced
> support we have in ODF
1.1 and 1.2 is preferred for nested tables.
So the issue is not subtables per se, but rather how they are encoded
in the ODF XML. Can we perhaps avoid arguing about whether subtables
are important or not?
> A more detailed analysis of the issue is here:
>
> http://lists.oasis-open.org/archives/office-accessibility/200608/
> msg00048.html
That was my reaction too after reading the linked page. It sounds like the issue may be more limited than deprecating nested tables entirely; as described it seems instead to be a need to deprecate their use for implementing table cell splits and joins.
I'm guessing that this would improve round-tripping with both WordPerfect and MS Word, neither of whose page layout engines support nested tables. But I'm wondering if a partial deprecation along such lines would necessarily resolve all related accessibility issues?
I'm also wondering if a partial deprecatation would also resolve all relevant difficulties in mapping between ODF apps and Word/WordPerfect. E.g., what might an ODF plug-in for MS Word do with a document generated in an ODF app that contains a nested table do with the nested table when importing such a document into Word?
Are we back to needing to discuss an interoperability subset of ODF with compatibility modes in the ODF apps?
