[ODFPlugtest] program, october 14 and 15

[Patrick Durusau]

Bart,

On 7/8/2010 11:18 AM, Hanssens Bart wrote:
> Probably start with a mapping, headers should map rather nicely.
>
> Styles on the other hand... even if one can map everything to CSS,
> CSS itself isn't supported equally by all browsers.
>
>    
Err, meant style more abstractly. So that a mapping could stipulate a 
graceful fallback if a particular style is not supported.

One of the design features of ODF is that if all you have is <text:p> 
and <text:h>, you have the content of the document.

That isn't literally true but close enough.

Styles impact how you display that content, numbering, etc. Very 
important to have a useful document but ODF strives to preserve the 
content/style distinction that is inherent, at least in early markup 
experience.

> Change tracking ? (now HTML does have INS and DEL elements...)
>
>    

That is probably harder because our current change tracking could be 
more robust.

Hope you are having a great day!

Patrick

> Bart
>
> ________________________________________
> From: plugtest-bounces at opendocsociety.org [plugtest-bounces at opendocsociety.org] On Behalf Of Jos van den Oever [jos.van.den.oever at kogmbh.com]
> Sent: Thursday, July 08, 2010 4:54 PM
> To: plugtest at opendocsociety.org
> Subject: Re: [ODFPlugtest] program, october 14 and 15
>
> On Thursday, July 08, 2010 04:34:06 pm robert_weir at us.ibm.com wrote:
>    
>> I would be interested in such a presentation.
>>
>> Also, I have some interest in seeing whether we can take what we learn
>> from writing HTML-based editors, and turn that into a standard, maybe a
>> subset of ODF called "ODF Web Profile" or maybe it would be called "HTML5
>> ODF Profile"?
>>      
> There are things that are hard to do in webpages, such as doing close text
> wrapping around irregular objects, embedding ole objects and dividing the text
> flow into separate pages. There could be a document describing what features
> could be omitted, but that would take the challenge out of writing a web based
> editor, now wouldnt it? ;-)
>
> What would you like to see in such a standard?
>
> Cheers,
> Jos
>
> --
> Jos van den Oever, software architect
> +49 391 25 19 15 53
> http://kogmbh.com/legal/
> _______________________________________________
> Plugtest mailing list
> Plugtest at opendocsociety.org
> http://lists.opendocsociety.org/mailman/listinfo/plugtest
> _______________________________________________
> Plugtest mailing list
> Plugtest at opendocsociety.org
> http://lists.opendocsociety.org/mailman/listinfo/plugtest
>
>    

-- 
Patrick Durusau
patrick at durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau