rsvg2 3.2.3-x64-mingw32 → 3.2.4-x64-mingw32

data/vendor/local/share/doc/librsvg/README.md

@@ -0,0 +1,162 @@
+Librsvg
+=======
+
+This is librsvg - A small library to render Scalable Vector Graphics
+([SVG][svg]), associated with the [GNOME Project][gnome].  It renders
+SVG files to [Cairo][cairo] surfaces.  Cairo is the 2D, antialiased
+drawing library that GNOME uses to draw things to the screen or to
+generate output for printing.
+
+Do you want to render non-animated SVGs to a Cairo surface with a
+minimal API?  Librsvg may be adequate for you.
+
+Using librsvg
+-------------
+
+**Compiling:** Librsvg uses a mostly normal [autotools] setup.  You
+may run into some peculiarities due to the Rust internals library if
+you are **cross-compiling** or if you are in a **build system with no
+network access**, or if you are **building binary packages from a
+librsvg tarball**.  In those cases, please refer to the
+[`COMPILING.md`][compiling] file.
+
+**Documentation:** You can read the [documentation for librsvg][docs] at
+developer.gnome.org.  Please [tell us][mail] if you don't find
+something there that you need.
+
+**Bug tracking:** If you have found a bug, take a look at [our bug
+tracker][bugs].  Please see the "[reporting bugs][reporting-bugs]"
+section in the file [CONTRIBUTING.md][contributing] to see how to
+provide a good bug report.
+
+**Asking questions:** Feel free to ask questions about using librsvg
+in the [desktop-devel-list][d-d-l] mailing list.
+
+**Programming languages:** Librsvg exports its API through [GObject
+Introspection][gi].  This way, it is available in many programming
+languages other than C.  Please see your language binding's
+documentation for information on how to load the `Rsvg` namespace.
+
+Contributing to librsvg's development
+-------------------------------------
+
+There is a code of conduct for contributors to librsvg; please see the
+file [`code-of-conduct.md`][coc].
+
+For information on how to report bugs, or how to contribute to librsvg
+in general, please see the file [`CONTRIBUTING.md`][contributing].
+
+Goals of librsvg
+----------------
+
+Librsvg aims to be a low-footprint library for rendering SVG images.
+It is used primarily in the [GNOME project](https://www.gnome.org) to
+render SVG icons and vector images that appear on the desktop.  It is
+also used in Wikimedia to render the SVG images that appear in
+Wikipedia, so that even old web browsers can display them.  Many
+projects which casually need to render static SVG images use librsvg.
+
+We aim to be a "render this SVG for me, quickly, and with a minimal
+API" kind of library.
+
+Feature additions will be considered on a case-by-case basis.
+
+Non-goals of librsvg
+--------------------
+
+We don't aim to:
+
+* Implement every single SVG feature that is in the spec.
+
+* Implement scripting or external access to the SVG's DOM.
+
+* Implement support for CSS-based animations (but if you can think of
+  a nice API to do this, we would be glad to know!)
+
+* Replace the industrial-strength SVG rendering machinery in modern
+  web browsers.
+
+Of course, [contributions are welcome][contributing].  In particular,
+if you find nice ways of doing the above while still maintaining the
+existing API of librsvg, we would love to know about it!
+
+Who uses librsvg?
+-----------------
+
+Librsvg is part of the [GNOME platform][platform].  Inside GNOME,
+librsvg takes multiple roles:
+
+* Loads SVGs from the generic gdk-pixbuf loader infrastructure, so any
+  application which uses gdk-pixbuf can load SVGs as if they were
+  raster images.
+
+* Loads SVG icons for the desktop.
+
+* Creates SVG thumbnails for the file manager.
+
+* Loads SVGs within GNOME's default image viewer, Eye of Gnome.
+
+Outside of GNOME's core:
+
+* GNOME games (chess, five-or-more, etc. to draw game pieces)
+
+* GIMP
+
+* GCompris
+
+* Claws-mail
+
+* Darktable
+
+* Mate-panel
+
+* Evas/Enlightenment
+
+* Emacs
+
+* ImageMagick
+
+* Wikipedia, to render SVGs as raster images for old browsers.
+  *Special thanks to Wikimedia for providing excellent bug reports.*
+
+
+Presentations on librsvg
+------------------------
+
+"[Replacing C library code with Rust: What I learned with
+librsvg][guadec-presentation]" was presented at GUADEC 2017.  It gives
+a little history of librsvg, and how/why it is being ported to Rust
+from C.
+
+Maintainers
+-----------
+
+The maintainer of librsvg is [Federico Mena Quintero][federico].  Feel
+free to contact me for any questions you may have about librsvg, both
+its usage and its development.  You can contact me in the following
+ways:
+
+* [Mail me][mail] at federico@gnome.org.
+
+* IRC: I am `federico` on `irc.gnome.org` in the `#rust` or
+  `#gnome-hackers` channels.  I'm there most weekdays (Mon-Fri)
+  starting at about UTC 14:00 (that's 08:00 my time; I am in the UTC-6
+  timezone).  If this is not a convenient time for you, feel free to
+  [mail me][mail] and we can arrange a time.
+
+[svg]: https://en.wikipedia.org/wiki/Scalable_Vector_Graphics
+[gnome]: https://www.gnome.org/
+[cairo]: https://www.cairographics.org/
+[coc]: code-of-conduct.md
+[autotools]: https://autotools.io/index.html
+[compiling]: COMPILING.md
+[docs]: https://developer.gnome.org/rsvg/stable/
+[mail]: mailto:federico@gnome.org
+[bugs]: https://gitlab.gnome.org/GNOME/librsvg/issues
+[gi]: https://wiki.gnome.org/Projects/GObjectIntrospection
+[contributing]: CONTRIBUTING.md
+[reporting-bugs]: CONTRIBUTING.md#reporting-bugs
+[d-d-l]: https://mail.gnome.org/mailman/listinfo/desktop-devel-list
+[federico]: https://people.gnome.org/~federico/
+[platform]: https://developer.gnome.org/
+[guadec-presentation]: https://people.gnome.org/~federico/blog/docs/fmq-porting-c-to-rust.pdf

data/vendor/local/share/doc/librsvg/code-of-conduct.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at federico@gnome.org. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+

data/vendor/local/share/gir-1.0/Rsvg-2.0.gir

@@ -63,7 +63,7 @@ and/or use gtk-doc annotations.  -->
            glib:type-name="RsvgHandle"
            glib:get-type="rsvg_handle_get_type"
            glib:type-struct="HandleClass">
-      <doc xml:space="preserve">The #RsvgHandle is an object representing the parsed form of a SVG</doc>
+      <doc xml:space="preserve">Lets you load SVG data and render it.</doc>
       <constructor name="new" c:identifier="rsvg_handle_new">
         <doc xml:space="preserve">Returns a new rsvg handle.  Must be freed with @g_object_unref.  This
 handle can be used for dynamically loading an image.  You need to feed it
@@ -254,7 +254,8 @@ freed until @g_object_unref is called.</doc>
       <method name="get_dimensions_sub"
               c:identifier="rsvg_handle_get_dimensions_sub"
               version="2.22">
-        <doc xml:space="preserve">Get the size of a subelement of the SVG file. Do not call from within the size_func callback, because an infinite loop will occur.</doc>
+        <doc xml:space="preserve">Get the size of a subelement of the SVG file. Do not call from within the
+size_func callback, because an infinite loop will occur.</doc>
         <return-value transfer-ownership="none">
           <type name="gboolean" c:type="gboolean"/>
         </return-value>
@@ -274,10 +275,8 @@ freed until @g_object_unref is called.</doc>
                      transfer-ownership="none"
                      nullable="1"
                      allow-none="1">
-            <doc xml:space="preserve">An element's id within the SVG, or %NULL to get
-  the dimension of the whole SVG.  For example, if you have a layer
-  called "layer1" for that you want to get the dimension, pass
-  "#layer1" as the id.</doc>
+            <doc xml:space="preserve">An element's id within the SVG, starting with "##", for
+example, "##layer1"; or %NULL to use the whole SVG.</doc>
             <type name="utf8" c:type="const char*"/>
           </parameter>
         </parameters>
@@ -302,13 +301,19 @@ will be returned.  Note that the pixbuf may not be complete until
       <method name="get_pixbuf_sub"
               c:identifier="rsvg_handle_get_pixbuf_sub"
               version="2.14">
-        <doc xml:space="preserve">Returns the pixbuf loaded by @handle.  The pixbuf returned will be reffed, so
-the caller of this function must assume that ref.  If insufficient data has
-been read to create the pixbuf, or an error occurred in loading, then %NULL
-will be returned.  Note that the pixbuf may not be complete until
-@rsvg_handle_close has been called.</doc>
+        <doc xml:space="preserve">Creates a #GdkPixbuf the same size as the entire SVG loaded into @handle, but
+only renders the sub-element that has the specified @id (and all its
+sub-sub-elements recursively).  If @id is #NULL, this function renders the
+whole SVG.
+
+If you need to render an image which is only big enough to fit a particular
+sub-element of the SVG, consider using rsvg_handle_render_cairo_sub(), upon a
+surface that is just the size returned by rsvg_handle_get_dimensions_sub().
+You will need to offset the rendering by the amount returned in
+rsvg_handle_get_position_sub().</doc>
         <return-value transfer-ownership="full" nullable="1">
-          <doc xml:space="preserve">the pixbuf loaded by @handle, or %NULL.</doc>
+          <doc xml:space="preserve">a pixbuf, or %NULL if an error occurs
+during rendering.</doc>
           <type name="GdkPixbuf.Pixbuf" c:type="GdkPixbuf*"/>
         </return-value>
         <parameters>
@@ -320,9 +325,8 @@ will be returned.  Note that the pixbuf may not be complete until
                      transfer-ownership="none"
                      nullable="1"
                      allow-none="1">
-            <doc xml:space="preserve">The id of an element inside the SVG, or %NULL to
-render the whole SVG. For example, if you have a layer called
-"layer1" that you wish to render, pass "##layer1" as the id.</doc>
+            <doc xml:space="preserve">An element's id within the SVG, starting with "##", for
+example, "##layer1"; or %NULL to use the whole SVG.</doc>
             <type name="utf8" c:type="const char*"/>
           </parameter>
         </parameters>
@@ -347,10 +351,12 @@ the size_func callback, because an infinite loop will occur.</doc>
             <doc xml:space="preserve">A place to store the SVG fragment's position.</doc>
             <type name="PositionData" c:type="RsvgPositionData*"/>
           </parameter>
-          <parameter name="id" transfer-ownership="none">
-            <doc xml:space="preserve">An element's id within the SVG.
-For example, if you have a layer called "layer1" for that you want to get
-the position, pass "##layer1" as the id.</doc>
+          <parameter name="id"
+                     transfer-ownership="none"
+                     nullable="1"
+                     allow-none="1">
+            <doc xml:space="preserve">An element's id within the SVG, starting with "##", for
+example, "##layer1"; or %NULL to use the whole SVG.</doc>
             <type name="utf8" c:type="const char*"/>
           </parameter>
         </parameters>
@@ -367,7 +373,7 @@ the position, pass "##layer1" as the id.</doc>
             <type name="Handle" c:type="RsvgHandle*"/>
           </instance-parameter>
           <parameter name="id" transfer-ownership="none">
-            <doc xml:space="preserve">an element's id within the SVG</doc>
+            <doc xml:space="preserve">an element's id within the SVG, starting with "##", for example, "##layer1".</doc>
             <type name="utf8" c:type="const char*"/>
           </parameter>
         </parameters>
@@ -634,6 +640,7 @@ from #GIOErrorEnum are also possible.</doc>
         <type name="gint" c:type="gint"/>
       </property>
       <field name="parent">
+        <doc xml:space="preserve">parent instance</doc>
         <type name="GObject.Object" c:type="GObject"/>
       </field>
       <field name="priv" readable="0" private="1">
@@ -648,7 +655,7 @@ from #GIOErrorEnum are also possible.</doc>
     <record name="HandleClass"
             c:type="RsvgHandleClass"
             glib:is-gtype-struct-for="Handle">
-      <doc xml:space="preserve">Class structure for #RsvgHandle</doc>
+      <doc xml:space="preserve">Class structure for #RsvgHandle.</doc>
       <field name="parent">
         <doc xml:space="preserve">parent class</doc>
         <type name="GObject.ObjectClass" c:type="GObjectClass"/>
@@ -692,10 +699,10 @@ from #GIOErrorEnum are also possible.</doc>
     <constant name="MAJOR_VERSION" value="2" c:type="LIBRSVG_MAJOR_VERSION">
       <type name="gint" c:type="gint"/>
     </constant>
-    <constant name="MICRO_VERSION" value="20" c:type="LIBRSVG_MICRO_VERSION">
+    <constant name="MICRO_VERSION" value="3" c:type="LIBRSVG_MICRO_VERSION">
       <type name="gint" c:type="gint"/>
     </constant>
-    <constant name="MINOR_VERSION" value="40" c:type="LIBRSVG_MINOR_VERSION">
+    <constant name="MINOR_VERSION" value="42" c:type="LIBRSVG_MINOR_VERSION">
       <type name="gint" c:type="gint"/>
     </constant>
     <record name="PositionData" c:type="RsvgPositionData">
@@ -709,7 +716,7 @@ from #GIOErrorEnum are also possible.</doc>
         <type name="gint" c:type="int"/>
       </field>
     </record>
-    <constant name="VERSION" value="2.40.20" c:type="LIBRSVG_VERSION">
+    <constant name="VERSION" value="2.42.3" c:type="LIBRSVG_VERSION">
       <type name="utf8" c:type="gchar*"/>
     </constant>
     <function name="cleanup" c:identifier="rsvg_cleanup" version="2.36">
@@ -730,10 +737,15 @@ See xmlCleanupParser() for more information.</doc>
     </function>
     <function name="set_default_dpi"
               c:identifier="rsvg_set_default_dpi"
-              version="2.8">
-      <doc xml:space="preserve">Sets the DPI for the all future outgoing pixbufs. Common values are
-75, 90, and 300 DPI. Passing a number &lt;= 0 to @dpi will
-reset the DPI to whatever the default value happens to be.</doc>
+              version="2.8"
+              deprecated="1"
+              deprecated-version="2.42.3">
+      <doc xml:space="preserve">Do not use this function.  Create an #RsvgHandle and call
+rsvg_handle_set_dpi() on it instead.</doc>
+      <doc-deprecated xml:space="preserve">This function used to set a global default DPI.  However,
+it only worked if it was called before any #RsvgHandle objects had been
+created; it would not work after that.  To avoid global mutable state, please
+use rsvg_handle_set_dpi() instead.</doc-deprecated>
       <return-value transfer-ownership="none">
         <type name="none" c:type="void"/>
       </return-value>
@@ -746,10 +758,15 @@ reset the DPI to whatever the default value happens to be.</doc>
     </function>
     <function name="set_default_dpi_x_y"
               c:identifier="rsvg_set_default_dpi_x_y"
-              version="2.8">
-      <doc xml:space="preserve">Sets the DPI for the all future outgoing pixbufs. Common values are
-75, 90, and 300 DPI. Passing a number &lt;= 0 to @dpi will
-reset the DPI to whatever the default value happens to be.</doc>
+              version="2.8"
+              deprecated="1"
+              deprecated-version="2.42.3">
+      <doc xml:space="preserve">Do not use this function.  Create an #RsvgHandle and call
+rsvg_handle_set_dpi_x_y() on it instead.</doc>
+      <doc-deprecated xml:space="preserve">This function used to set a global default DPI.  However,
+it only worked if it was called before any #RsvgHandle objects had been
+created; it would not work after that.  To avoid global mutable state, please
+use rsvg_handle_set_dpi() instead.</doc-deprecated>
       <return-value transfer-ownership="none">
         <type name="none" c:type="void"/>
       </return-value>

data/vendor/local/share/gtk-doc/html/rsvg-2.0/annotation-glossary.html

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Annotation Glossary: RSVG Libary Reference Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.0">
-<link rel="home" href="index.html" title="RSVG Libary Reference Manual">
-<link rel="up" href="index.html" title="RSVG Libary Reference Manual">
+<title>Annotation Glossary: Librsvg Reference Manual</title>
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
+<link rel="home" href="index.html" title="Librsvg Reference Manual">
+<link rel="up" href="index.html" title="Librsvg Reference Manual">
 <link rel="prev" href="api-index-2-36.html" title="Index of new symbols in 2.32">
 <link rel="next" href="licence.html" title="Appendix A. Licence">
-<meta name="generator" content="GTK-Doc V1.26 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -49,6 +49,6 @@
 <dd class="glossdef"><p>Free data after the code is done.</p></dd>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.26</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>