veyepar: ODF: Great standard, but what works?

Author(s):	Ben Martin
Location	Boardwalk Gallery
Date	jan Wed 18	Days Raw Files
Start	20:20	First Raw Start	20:18
Duration	0:45:0	Offset	0:01:01
End	21:05	Last Raw End	21:18
Chapters	00:00 0:28:58
Total cuts_time	38 min.

http://linux.conf.au/schedule/presentation/85/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf ODF_Great_standard_but_what_works.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

ODF is an open standard for storing office documents like
text, spreadsheets, drawings, and presentations.While ODF1.2
has been a standard for years, most tools do not fully
implement the entire specification. See how many current
generation office suites implement and or ignore the features
of the ODF specification. I'll also cover some open source
tools which you can use to check how well your own documents
are preserved across many different office suites. Some
results are available at
http://autotests.opendocumentformat.org/
 
I have been working on tools to help you work out what is
supported by each office application and see how a document
is presented on a platform that you do not have access to.
odfautotests runs hundreds of tests that have been derived 
from the ODF standard, with each test aimed at showing how well each office application preserves a specific attribute or element of the ODF standard.

So for example you can see at a glance what
office application will throw away ruby text, and also see
how the ruby text is presented. While you might not care
about ruby text, returning an updated document to a Japanese
client with it stripped out will likely lead to tension.
odfserver is a new tool created this year to allow files to
be uploaded to a central server and have numerous office
applications load and save each file to test compatibility.

These testing tools are useful for a few groups of people. End users looking to use ODF and knowing what is properly perserved in their document. Small tests showing failing attributes are gold for developers who can then formulate plans as to which parts of the specification should be supported by their project next.

Comment:

production notes