Gianluca Turconi wrote: > IMO, it isn't only a question about "better defaults", but a real > turning point for LibO. > > I'll try to clarify my point of view. > > Let's say that by the time ODF 1.2 will be out, every feature > currently supported from LibO will be in ODF specification too. That > would be simply great. > > Then, what? > > Will LibO 4.0/5.0 stay at ODF 1.2 until ODF 2.0 (or whatever > version) will be officially approved, becoming so the "Lingua > Franca" in exchanging documents for people and organizations or will > LibO try to implement more features that *may* be included in ODF > 2.0, becoming so a technical cutting edge application? > > They are two completely different visions of the project, I think. > Hi Gianluca, all,
soo - as a matter of fact, both LibO and OOo 3.3 will occasionally write out files that'll only comply to the "extended" ODF 1.2 conformance class. There are two major reasons for that: a) ODF evolves somewhat slowly (when 1.2 gets out, 1.1 will be almost 4 years old) - you cannot stop shipping features for 4 years b) OASIS, for very good practical reasons, only wants to standardize what has been successfully implemented (by at least three independent products, even) - so out of necessity, you'll need implementations of not-yet-standardized features, to actually make those standardizable via OASIS. So I guess moving on & extending ODF is a feature, not a bug - of course, for those who need it, you want a "strict mode" (which we have). Cheers, -- Thorsten -- Unsubscribe instructions: Email to discuss+h...@documentfoundation.org Posting guidelines: http://netmeister.org/news/learn2quote.html Archive: http://www.documentfoundation.org/lists/discuss/ *** All posts to this list are publicly archived ***
