[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Substitute for the MSOOXML concept of Comments
From:       Carlos Licea <carlos_licea () hotmail ! com>
Date:       2010-07-14 22:14:35
Message-ID: 201007141614.35228.carlos_licea () hotmail ! com
[Download RAW message or body]

> I don't want to use "unacceptable" as an argument as thats too strong, but
> I do think Thorsten has a good point.
> 
> If our filters create ODF that is only actually parsable by KOffice and
> would likely require us to create reading code in KOffice and a new
> feature to show this too. All for MSOffice interoperability. Also this
> KOffice-only feature would be saved out in a koffice-only manner which
> means we are essentially hindering interoperability and adding a lot of
> maintenance because the MSOOXML spec is pretty darn huge and filled with
> this kind of stuff.
>
> In my opinion; the fact that MS created a feature that doesn't cleanly map
> to ODF should in my opinion mean we find the closest possible standardized
> representation and use that. Which has the advantage of that document
> being usable for KWord and OOo and many other ODF readers including
> MSOffice.
I agree that interoperability should be amongst our major concerns, but I see 
nothing wrong with making our additions to ODF, and then try to make it into 
the standard.

As a side note, this change doesn't affect KWord. This kind of comments 
(§19.4.1 cm) are only for presentations.

Now, if you could stop focusing only on the creation of another element. 
Instead I'd like to hear proposals on what approach to take.

Also, I've already provided another way to do this but nobody has commented on 
that. This approach bends a little bit the rules and loses some information 
but it's ODF compatible.
-- 
Carlos Licea
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

[prev in list] [next in list] [prev in thread] [next in thread]