Make SVG 1.2 features optional

[Alfonse]

Using Inkscape to create SVG documents for the web is one of its more important uses. Including SVG 1.2 features (a spec that isn't even finished yet) as a standard feature is potentially useful, but it really gets in the way when you need to use Inkscape to make SVG documents for a wide audience.

Being able to restrict Inkscape to SVG 1.1 only would be a very good thing. This would be a per-document option. Things like flowing text and the like could be excised from the UI easily enough, creating regular text instead.

[su_v (suv-lp)]

related to or duplicate of
Bug #167335 “flowed text has no SVG 1.1-compliant fallback”:
<https://bugs.launchpad.net/inkscape/+bug/167335>

[jazzynico (jazzynico)]

I'm marking this report duplicate of Bug #167335 “flowed text has no SVG 1.1-compliant fallback”. Please revert this status and comment if you think it's not the case.

[Alfonse (jmckesson)]

I'm not asking for an alternate way to create text that is SVG 1.1 compliant. What I'm asking for is an option that says, "No matter what, the UI will not allow me to create anything that is not SVG 1.1 compliant." Since 1.1 is the current standard, it makes sense to *ensure* that you cannot create non-1.1 compliant files.

[jazzynico (jazzynico)]

Ok, Bug #167335 is for saving options, this report for editing options.

The feature tag is not useful. The (official) svg one already covers all that deals with the svg specs and how they are implemented in Inkscape.

[su_v (suv-lp)]

@Pablo - imho adding the 'saving' tag here is misleading: this report is about restricting available features of Inkscape in the user interface (the saving part - providing a SVG 1.1-compliant fallback - is handled in bug #167335).