inkscape/src/extension/implementation, branch livecoding An experimental livecoding plugin for Inkscape Extensions: Implement translationdomain functionality 2019-10-19T12:33:34+00:00 Patrick Storz eduard.braun2@gmx.de 2019-10-17T00:16:32+00:00 76ce73061550ff42e97c1fec9836c35cc0e24d64 Inkscape will read the "translationdomain" attribute from the <inkscape-extension> root element in the .inx file. It will then attempt to lookup a message catalog that matches this domain, register it with gettext, and use it for translations. Message catalogs may be located in either - the .inx file's location - the root of the "extensions" directory containing the .inx - the system location Inkscape's own catalog is loaded from To make this functionality available to script extensions, Inkscape will set the environment variables INKEX_GETTEXT_DOMAIN and INKEX_GETTEXT_DIRECTORY so extension scripts can then use something like bindtextdomain(INKEX_GETTEXT_DOMAIN, INKEX_GETTEXT_DIRECTORY) textdomain(INKEX_GETTEXT_DOMAIN) to enable the feature. See also https://gitlab.com/inkscape/inkscape/issues/333 https://gitlab.com/inkscape/extensions/issues/117 
Inkscape will read the "translationdomain" attribute from the
<inkscape-extension> root element in the .inx file.

It will then attempt to lookup a message catalog that matches
this domain, register it with gettext, and use it for translations.

Message catalogs may be located in either
- the .inx file's location
- the root of the "extensions" directory containing the .inx
- the system location Inkscape's own catalog is loaded from

To make this functionality available to script extensions, Inkscape
will set the environment variables
  INKEX_GETTEXT_DOMAIN
and
  INKEX_GETTEXT_DIRECTORY
so extension scripts can then use something like
  bindtextdomain(INKEX_GETTEXT_DOMAIN, INKEX_GETTEXT_DIRECTORY)
  textdomain(INKEX_GETTEXT_DOMAIN)
to enable the feature.

See also
  https://gitlab.com/inkscape/inkscape/issues/333
  https://gitlab.com/inkscape/extensions/issues/117
Extensions: Switch .xslt file look-up to dependency logic as well 2019-10-14T18:58:58+00:00 Patrick Storz eduard.braun2@gmx.de 2019-10-14T18:58:58+00:00 19463b12ec3527406825b9d2e092d6e78688f2a4 






Extensions: Improve logic to lookup script extensions
2019-10-14T17:36:29+00:00

Patrick Storz
eduard.braun2@gmx.de

2019-10-13T18:02:49+00:00

bb3261782fa74919c3ee34baf60dc09da61aff1e

- Use identical logic for looking up <dependency>s and <command>s.
- Remove duplicate (but inconsistent and incomplete) logic from
  script.cpp that was used to search for the <command> again
- Remove <check> element from .inx format
  It seems unused (at the very least by core extensions) and
  redundant to <dependency> checking
- Deprecate the <command>-specific "reldir" attribute.
  Consistently use the functionally identical "location" attribute
  that was only used for <dependency>s before
- Introduce the new relative location value location="inx",
  which looks up <dependencies> and <command>s relative to the
  .inx file's location.





- Use identical logic for looking up <dependency>s and <command>s.
- Remove duplicate (but inconsistent and incomplete) logic from
  script.cpp that was used to search for the <command> again
- Remove <check> element from .inx format
  It seems unused (at the very least by core extensions) and
  redundant to <dependency> checking
- Deprecate the <command>-specific "reldir" attribute.
  Consistently use the functionally identical "location" attribute
  that was only used for <dependency>s before
- Introduce the new relative location value location="inx",
  which looks up <dependencies> and <command>s relative to the
  .inx file's location.







cleanup includes a bit
2019-08-31T14:50:39+00:00

Patrick Storz
eduard.braun2@gmx.de

2019-08-04T23:13:40+00:00

2e2f1abfd59888af7749429e9016cd1768b9a0a6












Switch Inkscape::Extension to use InxWidgets instead of InxParameters
2019-08-31T14:50:38+00:00

Patrick Storz
eduard.braun2@gmx.de

2019-08-04T22:53:57+00:00

40df9f6ef495c4577958502ffb4f23a4a4e1092f












Fix various minor typos
2019-07-01T23:35:16+00:00

Yuri Chornoivan
yurchor@ukr.net

2019-07-01T23:35:16+00:00

7f3aa2882be5547d5308870bced554502ca4421c












Remove support for saving as JavaFX 1.x script (*.fx)
2019-05-10T13:25:07+00:00

Karl Cheng
qantas94heavy@gmail.com

2019-05-10T12:16:22+00:00

261bb887eb8c5f110e58b352fde85c27690a345a

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





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







More document.h cleanup.
2019-04-06T18:54:25+00:00

Tavmjong Bah
tavmjong@free.fr

2019-04-06T18:54:25+00:00

87eb273ceca7e4212a4bfbf2e04b616bac73a701












script.cpp: more cleanup
2019-03-29T22:40:16+00:00

Patrick Storz
eduard.braun2@gmx.de

2019-03-29T22:24:26+00:00

6225b656b339a86e6886b63aabb59fd0f7c87af8












script.cpp: Glib::spawn_async_with_pipes actually wants UTF-8
2019-03-29T22:18:24+00:00

Patrick Storz
eduard.braun2@gmx.de

2019-03-29T22:18:24+00:00

a90a46ec05952fa162f4285ef19239c9a167a066