|Subject:||[Lynx-dev] SVG patch to accept svg and transform it to html.|
|Date:||Tue, 5 Aug 2008 07:37:00 +0100|
|SVG patch to accept svg and transform it to html. |
the SVG specification** says every stand-alone SVG file should have a title and that it should appear before any other child elements (except possibly 'metadata' elements) or character data content.
so as this is very similar to html <title> this could be a straight transform.
One that might stimulate further support and interest.
I apologise but even this patch task is likely to be beyond my abilities
a more complete transform is complex.*
were other suggestions discussed?
these extract have been re-arranged for clarity:
Authors should always provide a 'title' child element to the 'svg' element within a stand-alone SVG document. The 'title' child element to an 'svg' element serves the purposes of identifying the content of the given SVG document fragment. Since users often consult documents out of context, authors should provide context-rich titles. Thus, instead of a title such as "Introduction", which doesn't provide much contextual background, authors should supply a title such as "Introduction to Medieval Bee-Keeping" instead. For reasons of accessibility, SVG User Agents should always make the content of the 'title' child element to the 'svg' element available to users (See the User Agent Accessibility Guidelines 1.0 [UAAG]). The mechanism for doing so depends on the SVG User Agent (e.g., as a caption, spoken).
It is strongly recommended that at most one 'desc' and at most one 'title' element appear as a child of any particular element, and that these elements appear before any other child elements (except possibly 'metadata' elements) or character data content. If SVG User Agents need to choose among multiple 'desc' or 'title' elements for processing (e.g., to decide which string to use for a tooltip), the user agent shall choose the first one the test attributes of which resolve to true.
Each container element or graphics element in an SVG document may supply a 'desc' and may also supply a 'title' description. The 'desc' element contains a detailed description for the container or graphics element containing it. This description should be usable as replacement content for cases when the user cannot see the rendering of the SVG element for some reason. The 'title' element contains a short title for the container or graphics element containing it. This short title provides information supplementary to the rendering of the element, but is not sufficient to replace it.
*the extracts above also say:
"Each container element or graphics element in an SVG document may supply a 'desc' and may also supply a 'title' description."
"This description should be usable as replacement content for cases when the user cannot see the rendering of the SVG element for some reason."
so all description content could also be rendered as html.
html separators would be required, perhaps div?
I am not aware of any suggestions, proposals or techniques advising SVG authors, and these will be needed.
for instance maybe a text separators such as | or vertical bar, where one is not present.
it could be that where much description is present and is provided in svg groups, html lists would be a more appropriate transform.
but these types of discussion await a first step in the dark.
On 4 Aug 2008, at 21:47, Thomas Dickey wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|