Residual "junk" in 'Plain SVG'

Bug #744819 reported by Gregor Shapiro on 2011-03-29
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Inkscape
Low
Unassigned

Bug Description

I created an Inkscape.svg file, with some text. I turned the text into paths and vacuumed the definitions then saved a copy of the file as a "plain SVG" in the hope that it would validate correctly after editing some of the xmlns and meta data. Imagine my surprise to still find a bunch of references to text and typefaces in the document. After removing those - IMO there should not have been any text at all in the svg everything was paths!- the file was found to be valid by w3.org.

Update:
Bug #167335, bug #390549, bug #168720, bug #171983 cover most of the cited issues. Remaining issue AFAICT:

c) '-inkscape-font-specification'
The nonstandard CSS style property of text objects (or groups/paths of text converted to paths) is not removed when saving as 'Plain SVG'

Gregor Shapiro (gregor-shapiro) wrote :

And a validated version

su_v (suv-lp) wrote :

a) Element 'FlowRoot'/'FlowPara' undefined

(…)
   version="1.2"
(…)
  <flowRoot id="flowRoot4080" (…) >
    <flowRegion id="flowRegion4082">
      <rect id="rect4084" (…) />
    </flowRegion>
    <flowPara id="flowPara4086" />
  </flowRoot>

Non-compliant implementation of 'Flowed Text' - duplicate of
Bug #167335 “flowed text has no SVG 1.1-compliant fallback”

Empty, invisible 'Flowed Text' - duplicate of
Bug #485269 “Invisible and unselectable flow region in image”

b) References to text styles (including font family)
These are not invalid as far as I understand, and (IIRC) originally kept on purpose as style attribute of the resulting path or parent group after converting text to path - possibly to be able to reconstruct the converted text object or add more text using the same font specification.

See issue 2) in bug #390549, as well as bug #171983

c) -inkscape-font-specification
This attribute probably should not be in the "Plain SVG" file, though as CSS attribute I'm not sure it is invalid in a strict sense (the question whether a separate attribute within the inkscape namespace should be used instead was briefly discussed in bug #169973).

Please do not forget to always provide information about your Inkscape version and OS/platform used to reproduce the reported issue.

tags: added: saving svg
su_v (suv-lp) wrote :

Correction:
- c) -inkscape-font-specification
- This attribute probably should not be in the "Plain SVG" file, though as CSS attribute I'm not sure it is invalid in a strict sense

+ c) -inkscape-font-specification
+ This property probably should not be in the "Plain SVG" file, though as CSS property I'm not sure it is invalid in a strict sense

Gregor Shapiro (gregor-shapiro) wrote :

That answers most of my questions. It would definitely be great to be able to easily generate svg files that both pass w3 validation and are as "lightweight" as possible. (That is what I mistakenly assumed "Plain SVG" would be)

su_v (suv-lp) wrote :

> b) References to text styles (including font family)

I finally found the older report I hand in mind about this issue (it was linked as duplicate to a -IMHO- unrelated CSS problem):
Bug #168720 “Text styles remain in type objects converted to paths.”

summary: - Residual "junk" in xml file
+ Residual "junk" in 'Plain SVG'
su_v (suv-lp) wrote :

Setting status to 'Confirmed' for now - needs verification about the 'validness' of such a CSS style property.

description: updated
Changed in inkscape:
importance: Undecided → Low
status: New → Confirmed
su_v (suv-lp) wrote :

On 2011-03-29 11:47 (+0200), ~suv wrote:
> c) -inkscape-font-specification

Related:
* Bug #1324809 “-inkscape-font-specification should be removed”
  https://bugs.launchpad.net/inkscape/+bug/1324809

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers