Summary: | export "style sheets" and import them -- a long way to go yet, isn't it? | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | peter josvai <jepe> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | libreoffice-ux-advise, vsfoote |
Priority: | medium | Keywords: | needsUXEval |
Version: | 24.8.0.0 alpha0+ | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=95861 | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
peter josvai
2024-03-31 09:57:26 UTC
We are bound by what ODF framework supports, all other styling schemas need filter based translation--import and export (and why our CSS is not native and integration of HTML5/CSS3 is missing, see also bug 95861). Template ODF documents (nothing to do with the Master document .ODM) is much more efficient to store and exchange style details. Trivial to describe minimalistic ODF archives (especially with ODF Flat XML) as containers of styled paragraphs, tables, page layouts that can be applied to new documents or pasted as new elements on an existing document (opened in any of the LibreOffice moduels, not just Writer). So, beside improving the import/export *filters* for HTML5 and CSS (2.1 or 3) and a browser like "Web" viewing of that rendering, how much advantage is there really to implementing something more than current ODF template documents to hold applicable ODF styling? Not seeing a need to split out handling of our ODF 1.3 compliant styling--too much dev work for something that would be alien to all external "style" implementations, W3C CSS or other. Template archives are enough. (In reply to V Stuart Foote from comment #1) > Not seeing a need to split out handling of our ODF 1.3 compliant styling... Nor a good use case that makes it necessary. Thanks for your input anyway, Peter! |