mathematical 1.6.14 → 1.6.18

data/ext/mathematical/lasem/COPYING

@@ -1,113 +1,125 @@
-		  GNU LIBRARY GENERAL PUBLIC LICENSE
-		       Version 2, June 1991
-
- Copyright (C) 1991 Free Software Foundation, Inc.
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335, USA
+                  GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 2.1, February 1999
 
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.
 
-[This is the first released version of the library GPL.  It is
- numbered 2 because it goes with version 2 of the ordinary GPL.]
+[This is the first released version of the Lesser GPL.  It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
 
-			    Preamble
+                            Preamble
 
   The licenses for most software are designed to take away your
 freedom to share and change it.  By contrast, the GNU General Public
 Licenses are intended to guarantee your freedom to share and change
 free software--to make sure the software is free for all its users.
 
-  This license, the Library General Public License, applies to some
-specially designated Free Software Foundation software, and to any
-other libraries whose authors decide to use it.  You can use it for
-your libraries, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
+  This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it.  You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+  When we speak of free software, we are referring to freedom of use,
+not price.  Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
 
   To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if
-you distribute copies of the library, or if you modify it.
+distributors to deny you these rights or to ask you to surrender these
+rights.  These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
 
   For example, if you distribute copies of the library, whether gratis
 or for a fee, you must give the recipients all the rights that we gave
 you.  You must make sure that they, too, receive or can get the source
-code.  If you link a program with the library, you must provide
-complete object files to the recipients so that they can relink them
-with the library, after making changes to the library and recompiling
+code.  If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
 it.  And you must show them these terms so they know their rights.
 
-  Our method of protecting your rights has two steps: (1) copyright
-the library, and (2) offer you this license which gives you legal
+  We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
 permission to copy, distribute and/or modify the library.
 
-  Also, for each distributor's protection, we want to make certain
-that everyone understands that there is no warranty for this free
-library.  If the library is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original
-version, so that any problems introduced by others will not reflect on
-the original authors' reputations.
+  To protect each distributor, we want to make it very clear that
+there is no warranty for the free library.  Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
 
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that companies distributing free
-software will individually obtain patent licenses, thus in effect
-transforming the program into proprietary software.  To prevent this,
-we have made it clear that any patent must be licensed for everyone's
-free use or not licensed at all.
-
-  Most GNU software, including some libraries, is covered by the ordinary
-GNU General Public License, which was designed for utility programs.  This
-license, the GNU Library General Public License, applies to certain
-designated libraries.  This license is quite different from the ordinary
-one; be sure to read it in full, and don't assume that anything in it is
-the same as in the ordinary license.
-
-  The reason we have a separate public license for some libraries is that
-they blur the distinction we usually make between modifying or adding to a
-program and simply using it.  Linking a program with a library, without
-changing the library, is in some sense simply using the library, and is
-analogous to running a utility program or application program.  However, in
-a textual and legal sense, the linked executable is a combined work, a
-derivative of the original library, and the ordinary General Public License
-treats it as such.
-
-  Because of this blurred distinction, using the ordinary General
-Public License for libraries did not effectively promote software
-sharing, because most developers did not use the libraries.  We
-concluded that weaker conditions might promote sharing better.
-
-  However, unrestricted linking of non-free programs would deprive the
-users of those programs of all benefit from the free status of the
-libraries themselves.  This Library General Public License is intended to
-permit developers of non-free programs to use free libraries, while
-preserving your freedom as a user of such programs to change the free
-libraries that are incorporated in them.  (We have not seen how to achieve
-this as regards changes in header files, but we have achieved it as regards
-changes in the actual functions of the Library.)  The hope is that this
-will lead to faster development of free libraries.
+  Finally, software patents pose a constant threat to the existence of
+any free program.  We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder.  Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+  Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License.  This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License.  We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+  When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library.  The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom.  The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+  We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License.  It also provides other free software developers Less
+of an advantage over competing non-free programs.  These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries.  However, the Lesser license provides advantages in certain
+special circumstances.
+
+  For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard.  To achieve this, non-free programs must be
+allowed to use the library.  A more frequent case is that a free
+library does the same job as widely used non-free libraries.  In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+  In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software.  For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+  Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
 
   The precise terms and conditions for copying, distribution and
 modification follow.  Pay close attention to the difference between a
 "work based on the library" and a "work that uses the library".  The
-former contains code derived from the library, while the latter only
-works together with the library.
-
-  Note that it is possible for a library to be covered by the ordinary
-General Public License rather than by this special one.
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
 
-		  GNU LIBRARY GENERAL PUBLIC LICENSE
+                  GNU LESSER GENERAL PUBLIC LICENSE
    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
 
-  0. This License Agreement applies to any software library which
-contains a notice placed by the copyright holder or other authorized
-party saying it may be distributed under the terms of this Library
-General Public License (also called "this License").  Each licensee is
-addressed as "you".
+  0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
 
   A "library" means a collection of software functions and/or data
 prepared so as to be conveniently linked with application programs
@@ -134,7 +146,7 @@ such a program is covered only if its contents constitute a work based
 on the Library (independent of the use of the Library in a tool for
 writing it).  Whether that is true depends on what the Library does
 and what the program that uses the Library does.
-  
+
   1. You may copy and distribute verbatim copies of the Library's
 complete source code as you receive it, in any medium, provided that
 you conspicuously and appropriately publish on each copy an
@@ -256,7 +268,7 @@ distribute the object code for the work under the terms of Section 6.
 Any executables containing that work also fall under Section 6,
 whether or not they are linked directly with the Library itself.
 
-  6. As an exception to the Sections above, you may also compile or
+  6. As an exception to the Sections above, you may also combine or
 link a "work that uses the Library" with the Library to produce a
 work containing portions of the Library, and distribute that work
 under terms of your choice, provided that the terms permit
@@ -283,23 +295,31 @@ of these things:
     Library will not necessarily be able to recompile the application
     to use the modified definitions.)
 
-    b) Accompany the work with a written offer, valid for at
+    b) Use a suitable shared library mechanism for linking with the
+    Library.  A suitable mechanism is one that (1) uses at run time a
+    copy of the library already present on the user's computer system,
+    rather than copying library functions into the executable, and (2)
+    will operate properly with a modified version of the library, if
+    the user installs one, as long as the modified version is
+    interface-compatible with the version that the work was made with.
+
+    c) Accompany the work with a written offer, valid for at
     least three years, to give the same user the materials
     specified in Subsection 6a, above, for a charge no more
     than the cost of performing this distribution.
 
-    c) If distribution of the work is made by offering access to copy
+    d) If distribution of the work is made by offering access to copy
     from a designated place, offer equivalent access to copy the above
     specified materials from the same place.
 
-    d) Verify that the user has already received a copy of these
+    e) Verify that the user has already received a copy of these
     materials or that you have already sent this user a copy.
 
   For an executable, the required form of the "work that uses the
 Library" must include any data and utility programs needed for
 reproducing the executable from it.  However, as a special exception,
-the source code distributed need not include anything that is normally
-distributed (in either source or binary form) with the major
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
 components (compiler, kernel, and so on) of the operating system on
 which the executable runs, unless that component itself accompanies
 the executable.
@@ -348,7 +368,7 @@ Library), the recipient automatically receives a license from the
 original licensor to copy, distribute, link with or modify the Library
 subject to these terms and conditions.  You may not impose any further
 restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
+You are not responsible for enforcing compliance by third parties with
 this License.
 
   11. If, as a consequence of a court judgment or allegation of patent
@@ -391,7 +411,7 @@ excluded.  In such case, this License incorporates the limitation as if
 written in the body of this License.
 
   13. The Free Software Foundation may publish revised and/or new
-versions of the Library General Public License from time to time.
+versions of the Lesser General Public License from time to time.
 Such new versions will be similar in spirit to the present version,
 but may differ in detail to address new problems or concerns.
 
@@ -412,7 +432,7 @@ decision will be guided by the two goals of preserving the free status
 of all derivatives of our free software and of promoting the sharing
 and reuse of software generally.
 
-			    NO WARRANTY
+                            NO WARRANTY
 
   15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
 WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
@@ -435,7 +455,7 @@ FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
 SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
 DAMAGES.
 
-		     END OF TERMS AND CONDITIONS
+                     END OF TERMS AND CONDITIONS
 
            How to Apply These Terms to Your New Libraries
 
@@ -454,19 +474,18 @@ convey the exclusion of warranty; and each file should have at least the
     Copyright (C) <year>  <name of author>
 
     This library is free software; you can redistribute it and/or
-    modify it under the terms of the GNU Library General Public
+    modify it under the terms of the GNU Lesser General Public
     License as published by the Free Software Foundation; either
-    version 2 of the License, or (at your option) any later version.
+    version 2.1 of the License, or (at your option) any later version.
 
     This library is distributed in the hope that it will be useful,
     but WITHOUT ANY WARRANTY; without even the implied warranty of
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
-    Library General Public License for more details.
+    Lesser General Public License for more details.
 
-    You should have received a copy of the GNU Library General Public
-    License along with this library; if not, write to the 
-    Free Software Foundation, Inc., 59 Temple Place - Suite 330, 
-    Boston, MA  02111-1307  USA.
+    You should have received a copy of the GNU Lesser General Public
+    License along with this library; if not, write to the Free Software
+    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
 
 Also add information on how to contact you by electronic and paper mail.
 

data/ext/mathematical/lasem/{NEWS → NEWS.md}

@@ -1,3 +1,13 @@
+Release 0.5.2
+=============
+
+  * viewer: new simple mathml and svg viewer (mjakeman)
+  * itex2mml: update to 1.6.1 (Emmanuel)
+  * build: switch to meson (Emmanuel)
+  * build: deprecation warning fixes (Emmanuel)
+  * documentation: port API doc to gi-docgen (Emmanuel)
+  * ci: linux pipeline, valgrind checks, publication of aravis test suite rendering (Emmanuel)
+
 Release 0.5.1
 =============
 

data/ext/mathematical/lasem/README.md

@@ -0,0 +1,65 @@
+# ![](lasem.svg)
+
+### What is Lasem ?
+
+Lasem is a C/Gobject based SVG/Mathml renderer. It uses cairo and pango as it's
+rendering abstraction layer, and then support numerous output formats: xlib,
+PNG, SVG, PDF, PS, EPS...
+
+The API tries to follow the SVG and MathML DOM.
+
+It currently includes two simple applications:
+
+lasem-render, which takes a filename as argument and generates either a SVG, a
+PDF or a PS file, depending on the output file extension. There's a debug mode
+option (-d) that displays the bounding boxes of elements as blue rectangles, the
+logical extents of text as red boxes and the ink extents of text as green boxes.
+It accepts either MathML, Latex maths and SVG input. For the latex input,
+lasemrender uses the embedded itex2mml library for the conversion to MathML.
+
+lsm-test, which, if launched without argument, renders recursively all svg and
+mml files in a directory, and generate an html file which displays the browser
+rendering, lasem rendering, and if present the reference output. The html
+filename is lasemtest.xml. It's main use is the rendering of the sample files in
+the samples directory, by invoking "cd test && ./lsm-test data".
+
+### Documentation
+
+The latest documentation is available
+[here](https://lasemproject.github.io/lasem).
+
+The Lasem test suite is rendered in a single page
+[here](https://lasemproject.github.io/lasem/lasemtest.xml). The first column is
+the Lasem rendering, the middle one the reference rendering and the last one the
+rendering of your browser.
+
+### Installing Lasem
+
+Lasem uses the meson build system ( http://mesonbuild.com/ ). After you have
+downloaded the latest release from
+[https://github.com/LasemProject/lasem/releases](https://github.com/LasemProject/lasem/releases),
+you can build and install Lasem like [any other meson
+project](http://mesonbuild.com/Quick-guide.html#compiling-a-meson-project):
+
+```
+meson build
+cd build
+ninja
+ninja install
+```
+
+The build can be configured at any time using `meson configure` in the build
+directory. `meson configure` invoked without any other argument will show the
+configuration options.
+
+On some platforms (like Ubuntu), you may have to configure the dynamic linker
+(ld) to let it know where the aravis libraries are installed, and run ldconfig
+as root in order to update ld cache.
+
+### Requirements
+
+gobject, glib, gio, gdk-pixbuf, gdk, cairo, pangocairo, libxml, bison, flex
+
+For the runtime, the following ttf fonts should be installed: cmr10, cmmi10,
+cmex10 and cmsy10.  They are provided by the lyx-fonts package in fedora, and
+the fonts-lyx package in debian/ubuntu.

data/ext/mathematical/lasem/docs/lasem-render-0.6.1

@@ -89,13 +89,13 @@ software or see the
 
 .SH AUTHORS
 \fBlasem-render-0.6\fR's primary author is Emmanuel Pacaud
-<emmanuel@gnome.org>.
+<emmanuel.pacaud@free.fr>.
 
 The initial version of this manpage was written by J.H.M. Dassen (Ray)
 <jdassen@debian.org>.
 
 .SH SEE ALSO
-.URL "https://live.gnome.org/Lasem" "The Lasem homepage" .
+.URL "https://github.com/LasemProject/lasem" "The Lasem Github Repository" .
 
 .URL "http://blogs.gnome.org/emmanuel/category/lasem/" "Blog entries on Lasem" .
 

data/ext/mathematical/lasem/docs/meson.build

@@ -0,0 +1,3 @@
+install_man('lasem-render-0.6.1')
+
+subdir('reference/lasem')

data/ext/mathematical/lasem/docs/reference/lasem/building.md

@@ -0,0 +1,32 @@
+Title: Installation
+
+# Installing Lasem
+
+Lasem uses the meson build system ( http://mesonbuild.com/ ). After you have
+downloaded the latest release from
+[https://github.com/LasemProject/lasem/releases](https://github.com/LasemProject/lasem/releases),
+you can build and install Lasem like [any other meson
+project](http://mesonbuild.com/Quick-guide.html#compiling-a-meson-project):
+
+```
+meson setup build
+cd build
+ninja
+ninja install
+```
+
+The build can be configured at any time using `meson configure` in the build
+directory. `meson configure` invoked without any other argument will show the
+configuration options.
+
+On some platforms (like Ubuntu), you may have to configure the dynamic linker
+(ld) to let it know where the aravis libraries are installed, and run ldconfig
+as root in order to update ld cache.
+
+## Requirements
+
+gobject, glib, gio, gdk-pixbuf, gdk, cairo, pangocairo, libxml, bison, flex
+
+For the runtime, the following ttf fonts should be installed: cmr10, cmmi10,
+cmex10 and cmsy10.  They are provided by the lyx-fonts package in fedora, and
+the fonts-lyx package in debian/ubuntu.

data/ext/mathematical/lasem/docs/reference/lasem/lasem.toml.in

@@ -0,0 +1,47 @@
+[library]
+version = "@version@"
+browse_url = "https://github.com/LasemProject/lasem"
+repository_url = "https://github.com/LasemProject/lasem.git"
+website_url = "https://github.com/LasemProject/lasem"
+docs_url = "https://lasemproject.github.io/docs/lasem-0.8/"
+authors = "Lasem Project Team"
+logo_url = "lasem.svg"
+license = "LGPL-2.1-or-later"
+description = "The Lasem Mathml and SVG Rendering Library"
+dependencies = [ ]
+devhelp = true
+search_index = true
+
+[dependencies."GLib-2.0"]
+name = "GLib"
+description = "Portable utility library"
+docs_url = "https://docs.gtk.org/glib/"
+
+[dependencies."GObject-2.0"]
+name = "GObject"
+description = "The base type system library"
+docs_url = "https://docs.gtk.org/gobject/"
+
+[dependencies."GIO-2.0"]
+name = "GIO"
+description = "GObject Interfaces and Objects, Networking, IPC, and I/O"
+docs_url = "https://docs.gtk.org/gio/"
+
+[theme]
+name = "basic"
+show_index_summary = true
+show_class_hierarchy = true
+
+[source-location]
+base_url = "https://github.com/LasemProject/lasem/blob/main/"
+
+[extra]
+# The same order will be used when generating the index
+content_files = [
+	'overview.md',
+	'building.md',
+]
+content_images = [
+	'../../../lasem.svg'
+]
+urlmap_file = "urlmap.js"

data/ext/mathematical/lasem/docs/reference/lasem/meson.build

@@ -0,0 +1,44 @@
+toml_conf = configuration_data()
+toml_conf.set('version', meson.project_version())
+
+gidocgen = find_program('gi-docgen')
+
+gidocgen_common_args = [
+  '--quiet',
+  '--no-namespace-dir',
+]
+
+docs_dir = get_option('datadir') / 'doc'
+
+expand_content_md_files = [
+  'overview.md',
+  'building.md',
+]
+
+lasem_toml=configure_file(
+  input: 'lasem.toml.in',
+  output: 'lasem.toml',
+  configuration: toml_conf,
+  install: true,
+  install_dir: docs_dir / 'lasem-@0@'.format(lasem_api_version)
+)
+
+custom_target(
+  'lasem-doc',
+  input: [ lasem_toml, lasem_gir[0] ],
+  output: 'lasem-@0@'.format(lasem_api_version),
+  command: [
+    gidocgen,
+    'generate',
+    gidocgen_common_args,
+    '--add-include-path=@0@'.format(meson.current_build_dir() / '../../../src'),
+    '--config=@INPUT0@',
+    '--output-dir=@OUTPUT@',
+    '--content-dir=@0@'.format(meson.current_source_dir()),
+    '@INPUT1@'
+    ],
+    depend_files: [ expand_content_md_files ],
+    build_by_default: true,
+    install: true,
+    install_dir: docs_dir
+  )

data/ext/mathematical/lasem/docs/reference/lasem/overview.md

@@ -0,0 +1,24 @@
+Title: Overview
+
+# What is Lasem ?
+
+Lasem is a C/Gobject based SVG/Mathml renderer. It uses cairo and pango as it's
+rendering abstraction layer, and then support numerous output formats: xlib,
+PNG, SVG, PDF, PS, EPS...
+
+The API tries to follow the SVG and MathML DOM.
+
+It currently includes two simple applications:
+
+**lasem-render**, which takes a filename as argument and generates either a SVG, a
+PDF or a PS file, depending on the output file extension. There's a debug mode
+option (-d) that displays the bounding boxes of elements as blue rectangles, the
+logical extents of text as red boxes and the ink extents of text as green boxes.
+It accepts either MathML, Latex maths and SVG input. For the latex input,
+lasemrender uses the embedded itex2mml library for the conversion to MathML.
+
+**lsm-test**, which, if launched without argument, renders recursively all svg and
+mml files in a directory, and generate an html file which displays the browser
+rendering, lasem rendering, and if present the reference output. The html
+filename is `lasemtest.xml`. It's main use is the rendering of the sample files
+in the samples directory, by invoking `cd test && ./lsm-test data`.

data/ext/mathematical/lasem/docs/reference/lasem/urlmap.js

@@ -0,0 +1,5 @@
+baseURLs = [
+    [ 'GLib', 'https://docs.gtk.org/glib/' ],
+    [ 'GObject', 'https://docs.gtk.org/gobject/' ],
+    [ 'Gio', 'https://docs.gtk.org/gio/' ],
+]

data/ext/mathematical/lasem/itex2mml/README.itex2MML

@@ -1,9 +1,12 @@
 itex2MML[1] transforms itex (a dialect of latex) into MathML. itex2MML is developed by
 Paul Gartside and Jacques Distler.
 
-Currently, we include itex2MML 1.4.5, with the following modification:
+Currently, we include itex2MML 1.6.1, with the following modification:
 
-  - printf use is removed from itex2MML.y.
+  - printf use is removed in CHAR from itex2MML.y
+  - a unused lable is removed from itex2MML.y
+  - %option noinput is added in itex2MML.l
+  - y.tab.h is renamed itex2MML.tab.h in itex2MML.l
 
 Some documentation can be found here [4].