https://bugs.documentfoundation.org/show_bug.cgi?id=99628

--- Comment #9 from V Stuart Foote <[email protected]> ---
Thanks Regina. 

Unfortunately, the Inkscape project got out in front of the SVG 1.2 Full and
implemented the Flowed Text proposals--then apparently skipped the SVG 1.2 Tiny
handling of textArea.

Meaning a lot of SVGs generated in Inkscape come into LibreOffice with the
<flowRoot><flowRegion><flowPara> structures--e.g. the day of week lettering in
the rectangular boxes on the calendar testcase SVG here--that for bug 50114 we
simply ignore, guaranteeing broken rendering for SVGs coming from Inkscape.

Is anyone plugged in to what Inkscape is considering?  And we probably should
have been parsing the Inkscape flowed text structure in solidarity with them
(at least until they abandon it and move forward with whatever the W3C
publishes as SVG 2). 

Seems the question now for LibreOffice becomes: should we continue to ignore
the Inkscape Flowed Text images, or figure a way to parse them to canvas and
convert them to SVG 1.1 text when saved or exported, or to implement Inkscape's
methods and retain the source SVG. 

Then going forward, presumably implement the SVG 2 recommendations (either the
content area & wrapping area of 10.5 [1], or figure out what to do with the the
HTML5/CSS3 centric text "flows" through Exclusions or Regions [2]) and *how* to
push this back out as compliant ODF.

See some ugliness coming in chasing the emerging SVG "standards"

=-as an aside-=

Is there guidance from OASIS on where to take ODF as W3C drives content towards
HTML5.1 and CSS3?

It is a bit alarming in that many of the accessibility requirements (e.g. US
Section 508, or European Standard EN 301 549) that apply to LibreOffice as a
"user agent for authoring & media delivery" derive from the W3C's WCAG 2.0 [3]
perspective--not from OASIS ODF standards. We are required by statute in many
locations to be functionally compliant with the WCAG 2.0/UAAG 2.0 [4]
guidelines.


=-refs-=
[1] https://www.w3.org/TR/SVG2/text.html#TextLayout
[2]
https://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Mailing_List_Feedback#Text_flow_to_arbitrary_shapes
[3] Web Content Accessibility Guidelines - WCAG 2.0
[4] User Agent Accessibility Guidelines - UAAG 2.0

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to