It's discussions like this that make me glad that I'm just a cleaner. As far as I can see, any behaviour change that provokes such a polarised response from the devs is also likely to polarise users. Is it worth it?
Back to playing with compiler flags I go...
On 8-3-2013 19:15, John Cliff wrote:
>
> http://dictionary.reference.com/browse/export
>
> I've always taken export to mean what 3) on that page says -
>
Hi John,
I think a dictionary definition makes for a very bad argument, no? ;-)
We stick/mold a word onto functionality, not the other way around.
> like I said, I believe its wrong that we claim to open anything other
> than SVG, we dont, we import/translate them into an svg with varying
> levels of success. likewise, we can only save an svg, anything else is
> an export with a varying level of compatability.
You are correct that we translate everything to SVG. It is a good point.
We have to translate to SVG, there is no other way for the code to
handle things!
But, don't you agree that being able to use Inkscape as if it is a
PDF-editor is nice? (I mean the open/edit/save workflow, in contrast to
a (worst-case) open new/import/edit/export workflow, where the export
button means you have to click more stuff to select file type, etc, and
there not being a quick shortcut like Ctrl+S).
We shouldn't advertise Inkscape as a PDF-editor, but it would be a shame
to remove the functionality and it would make me very sad.
Cheers,
Johan
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel