Remove support for saving as JavaFX 1.x script (*.fx)

JavaFX 1.x is long obsolete (since 2012-12-20) and the code for it has
not been maintained. There have been no end user comments/reports since
2012 and a few bugs that would be important remain unfixed.

Given that this is not an import format, the impact of removing this
should be extremely low.

Refs: https://www.oracle.com/technetwork/java/javafx/overview/faq-1446554.html#8
Refs: http://web.archive.org/web/20170316051832/http://blogs.oracle.com/javafx/entry/javafx_1_2_and_javafx
Refs: https://stackoverflow.com/q/18865774/2074608

1 files changed, 12 insertions, 1 deletions

diff --git a/src/extension/implementation/xslt.cpp b/src/extension/implementation/xslt.cpp
index 1f2b79281..8ea8e5a7a 100644
--- a/src/extension/implementation/xslt.cpp
+++ b/src/extension/implementation/xslt.cpp
@@ -163,7 +163,18 @@ SPDocument * XSLT::open(Inkscape::Extension::Input */*module*/,
 void XSLT::save(Inkscape::Extension::Output *module, SPDocument *doc, gchar const *filename)
 {
     /* TODO: Should we assume filename to be in utf8 or to be a raw filename?
-     * See JavaFXOutput::save for discussion. */
+     * See JavaFXOutput::save for discussion.
+     *
+     * From JavaFXOutput::save (now removed):
+     * ---
+     * N.B. The name `filename_utf8' represents the fact that we want it to be in utf8; whereas in
+     * fact we know that some callers of Extension::save pass something in the filesystem's
+     * encoding, while others do g_filename_to_utf8 before calling.
+     *
+     * In terms of safety, it's best to make all callers pass actual filenames, since in general
+     * one can't round-trip from filename to utf8 back to the same filename.  Whereas the argument
+     * for passing utf8 filenames is one of convenience: we often want to pass to g_warning or
+     * store as a string (rather than a byte stream) in XML, or the like. */
     g_return_if_fail(doc != nullptr);
     g_return_if_fail(filename != nullptr);