OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [office] List Proposal Vote Deadline on Wednesday

On 5/2/07, Thomas Zander <zander@kde.org> wrote:
> Actually, this is not true. I just realized.
> David made a good explanation on how we have a proposal that uses 3 keys
> and another that uses 2 keys for each list item.
> The logical conclusion is that a '2 keys' model can be emulated in the
> 3-key model.  Simply by keeping 1 key always the same. (insert 'duh'
> here ;)
> Or in other words; converting a WW document into a ODF document can be
> done in the 'oliver/thomas proposal' by having all your lists use 1
> list-id and having different styles for each list.
> The conversion back is then easy as well.
> Bottom line; if there is a feature on ODF that WW doesn't support (like
> the concept of one style being reused for different lists) then don't use
> it and you can export just fine.  Which means that loading and saving a
> WW doc can and will be loss-less if you write a good converter.

I'm not competent to evaluate this. But I don't recall seeing anything
in the Sun/KOffice proposal specifying what that single key is to be.
It seems that what you propose might work if one were concerned only
with KOffice <> MSOffice round-tripping. But think of the more
involved use case where the same document gets handled by a bunch of
different apps, say for example a MSOffice <> KOffice <> OpenOffice <>
Google Docs round trip. In your scenario, does it matter that there is
no single key identified in the spec to be used by all apps?

The situation is far more complex than writing a converter for going
between just two apps.

Best regards,


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]