amiba 0.0.8 → 0.0.9

data/lib/amiba/frontend/public/javascript/MathJax/docs/rst/jsMath.rst

@@ -0,0 +1,31 @@
+.. _jsMath-support:
+
+*********************************
+Converting to MathJax from jsMath
+*********************************
+
+MathJax is the successor to the popular `jsMath
+<http://www.math.union.edu/locate/jsMath/>`_ package for rendering
+mathematics in web pages.  Like jsMath, MathJax works by locating and
+processing the mathematics within the webpage once it has been loaded
+in the browser by a user viewing your web pages.  If you are using
+jsMath with its ``tex2math`` preprocessor, then switching to MathJax
+should be easy, and is simply a matter of configuring MathJax
+appropriately.  See the section on :ref:`Configuring MathJax
+<configuration>` for details about loading and configuring MathJax.
+
+On the other hand, if you are using jsMath's ``<span
+class="math">...</span>`` and ``<div class="math">...</div>`` tags to
+mark the mathematics in your document, then you should use MathJax's
+``jsMath2jax`` preprocessor when you switch to MathJax.  To do this,
+include ``"jsMath2jax.js"`` in the `extensions` array of your
+configuration, with the `jax` array set to include ``"input/TeX"``.
+
+.. code-block:: javascript
+
+    extensions: ["jsMath2jax.js"],
+    jax: ["input/TeX", ...]
+
+There are a few configuration options for ``jsMath2jax``, which you
+can find in the ``config/MathJax.js`` file, or in the :ref:`jsMath
+configuration options <configure-jsMath2jax>` section.

data/lib/amiba/frontend/public/javascript/MathJax/docs/rst/mathjax.rst

@@ -0,0 +1,36 @@
+****************
+What is MathJax?
+****************
+
+MathJax is an open-source JavaScript display engine for LaTeX and
+MathML that works in all modern browsers.  It was designed with the
+goal of consolidating the recent advances in web technologies into a
+single, definitive, math-on-the-web platform supporting the major
+browsers and operating systems.  It requires no setup on the part of
+the user (no plugins to downlaod or software to install), so the page
+author can write web documents that include mathematics and be
+confident that users will be able to view it naturally and easily.
+One simply includes MathJax and some mathematics in a web page, and
+MathJax does the rest.
+
+MathJax uses web-based fonts (in those browsers that support it) to
+produce high-quality typesetting that scales and prints at full
+resolution (unlike mathematics included as images).  MathJax can be
+used with screen readers, providing accessibility for the visually
+impaired.  With MathJax, mathematics is text-based rather than
+image-based, and so it is available for search engines, meaning that
+your equations can be searchable, just like the text of your pages.
+MathJax allows page authors to write formulas using TeX and LaTeX
+notation, or `MathML <http://www.w3.org/TR/MathML3>`_, a World Wide
+Web Constortium standard for representing mathematics in XML format.
+MathJax will even convert TeX notation into MathML, so that it can be
+rendered more quickly by those browsers that support MathML natively,
+or so that you can copy and past it into other programs.
+
+MathJax is modular, so it loads components only when necessary, and
+can be extended to include new capabilities as needed.  MathJax is
+highly configurable, allowing authors to customize it for the special
+requirements of their web sites.  Finally, MathJax has a rich
+application programming interface (API) that can be used to make the
+mathematics on your web pages interactive and dynamic.
+

data/lib/amiba/frontend/public/javascript/MathJax/docs/rst/mathml.rst

@@ -0,0 +1,97 @@
+.. _MathML-support:
+
+**********************
+MathJax MathML Support
+**********************
+
+The support for :term:`MathML` in MathJax consists of three parts:  the
+`mml2jax` preprocessor, the MathML input processor, and the NativeMML
+output processor.  The first of these looks for ``<math>`` tags within
+your document and marks them for later processing by MathJax.  The
+second converts the MathML to the internal format used by MathJax, and
+the third turns the internal format into MathML within the page so
+that it can be displayed by the browser's native MathML support.
+
+Because of MathJax's modular design, you do not need to use all three
+of these components.  For example, you could use the `tex2jax`
+preprocessor and the TeX input processor, but the NativeMML output
+processor, so that your mathematics is entered in TeX format, but
+displayed as MathML.  Or you could use the `mml2jax` reprocessor and
+MathML input processor with the HTML-CSS output processor to make
+MathML available in browsers that don't have native MathML support.
+It is also possible to have MathJax select the output processor for
+you so that MathML is used in those browsers that support it, while
+HTML-CSS is used for those that don't.  See the :ref:`common
+configurations <common-configurations>` section for details and
+examples.
+
+Of course it is also possible to use all three components together.
+It may seem strange to go through an internal format just to return to
+MathML in the end, but this is actually what makes it possible to view
+MathML within an HTML page (rather than an XHTML page), without
+the complications of handling special MIME-types for the document, or
+any of the other setup issues that make using native MathML
+difficult.  MathJax handles the setup and properly marks the
+mathematics so that the browser will render it as MathML.  In
+addition, MathJax provides its contextual menu for the MathML, which
+lets the user zoom the mathematics for easier reading, get the copy
+the source markup, and so on, so there is added value to using MathJax
+even whith a pure MathML workflow.
+
+
+MathML in HTML pages
+====================
+
+For MathML that is handled via the pre-processor, you should not use
+the named MathML entities, but rather use the numeric entities like
+``&#x221A;`` or unicode characters embedded in the page itself.  The
+reason is that entities are replaced by the browser before MathJax
+runs, and some browsers report errors for unknown entities.  For
+browsers that are not MathML-aware, that will cause errors to be
+displayed for the MathML entities.  While that might not occur in the
+browser you are using to compose your pages, it can happen with other
+browsers, so you should avoid the named entities whenever possible.
+If you must use named entities, you may need to declare them in the
+`DOCTYPE` declaration by hand.
+
+When you use MathML in an HTML document rather than an XHTML one
+(MathJax will work woth both), you should not use the "self-closing"
+form for tags with no content, but should use separate open and close
+tags.  That is, use
+
+.. code-block:: html
+
+    <mspace width="thinmathspace"></mspace>
+
+rather than ``<mspace width="thinmathspace />``.  This is because HTML
+does not have self-closing tags, and some browsers will get the
+nesting of tags wrong if you attempt to use them.  For example, with
+``<mspace width="1em" />``, since there is no closing tag, the rest of
+the mathematics will become the content of the ``<mspace>`` tag; but
+since ``<mspace>`` should have no content, the rest of the mathematics
+will not be displayed.  This is a common error that should be avoided.
+
+
+Supported MathML commands
+=========================
+
+MathJax supports the `MathML3.0 <http://www.w3.org/TR/MathML3/>`_
+presentation mathematics tags, with some limitations.  The MathML
+support is still under active development, so some tags are not yet
+implemented, and some features are not fully developed, but are
+coming.
+
+The deficiencies include:
+
+- No support for the elementary math tags: ``mstack``, ``mlongdiv``,
+  ``msgroup``, ``msrow``, ``mscarries``, and ``mscarry``.
+
+- Limited support for line breaking (they are only allowed in direct
+  children of ``mrow`` or implied ``mrow`` elements.
+
+- No support for alignment groups in table.
+
+- No support for right-to-left rendering.
+
+See the `results of the MathML3.0 test suite
+<http://www.w3.org/Math/testsuite/results/tests.html>`_ for details.

data/lib/amiba/frontend/public/javascript/MathJax/docs/rst/mjtheme/static/mj.css_t

@@ -0,0 +1,256 @@
+/**
+ * Sphinx stylesheet -- default theme
+ * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ */
+
+@import url("basic.css");
+
+/* -- page layout ----------------------------------------------------------- */
+
+body {
+    font-family: {{ theme_bodyfont }};
+    font-size: 100%;
+    background-color: {{ theme_footerbgcolor }};
+    color: #000;
+    margin: 0;
+    padding: 0;
+}
+
+div.document {
+    background-color: {{ theme_sidebarbgcolor }};
+}
+
+div.documentwrapper {
+    float: left;
+    width: 100%;
+}
+
+div.bodywrapper {
+    margin: 0 0 0 230px;
+}
+
+div.body {
+    background-color: {{ theme_bgcolor }};
+    color: {{ theme_textcolor }};
+    padding: 0 20px 30px 20px;
+}
+
+{%- if theme_rightsidebar|tobool %}
+div.bodywrapper {
+    margin: 0 230px 0 0;
+}
+{%- endif %}
+
+div.footer {
+    color: {{ theme_footertextcolor }};
+    width: 100%;
+    padding: 9px 0 9px 0;
+    text-align: center;
+    font-size: 75%;
+}
+
+div.footer a {
+    color: {{ theme_footertextcolor }};
+    text-decoration: underline;
+}
+
+div.related {
+    background-color: {{ theme_relbarbgcolor }};
+    line-height: 30px;
+    color: {{ theme_relbartextcolor }};
+}
+
+div.related a {
+    color: {{ theme_relbarlinkcolor }};
+}
+
+div.sphinxsidebar {
+    {%- if theme_stickysidebar|tobool %}
+    top: 30px;
+    margin: 0;
+    position: fixed;
+    overflow: auto;
+    height: 100%;
+    {%- endif %}
+    {%- if theme_rightsidebar|tobool %}
+    float: right;
+    {%- if theme_stickysidebar|tobool %}
+    right: 0;
+    {%- endif %}
+    {%- endif %}
+}
+
+{%- if theme_stickysidebar|tobool %}
+/* this is nice, but it it leads to hidden headings when jumping
+   to an anchor */
+/*
+div.related {
+    position: fixed;
+}
+
+div.documentwrapper {
+    margin-top: 30px;
+}
+*/
+{%- endif %}
+
+div.sphinxsidebar h3 {
+    font-family: {{ theme_headfont }};
+    color: {{ theme_sidebartextcolor }};
+    font-size: 1.4em;
+    font-weight: normal;
+    margin: 0;
+    padding: 0;
+}
+
+div.sphinxsidebar h3 a {
+    color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar h4 {
+    font-family: {{ theme_headfont }};
+    color: {{ theme_sidebartextcolor }};
+    font-size: 1.3em;
+    font-weight: normal;
+    margin: 5px 0 0 0;
+    padding: 0;
+}
+
+div.sphinxsidebar p {
+    color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar p.topless {
+    margin: 5px 10px 10px 10px;
+}
+
+div.sphinxsidebar ul {
+    margin: 10px;
+    padding: 0;
+    color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar ul li {
+    margin-top: .2em;
+}
+
+div.sphinxsidebar a {
+    color: {{ theme_sidebarlinkcolor }};
+}
+
+div.sphinxsidebar input {
+    border: 1px solid {{ theme_sidebarlinkcolor }};
+    font-family: sans-serif;
+    font-size: 1em;
+}
+
+/* -- body styles ----------------------------------------------------------- */
+
+a {
+    color: {{ theme_linkcolor }};
+    text-decoration: none;
+}
+
+a:hover {
+    text-decoration: underline;
+}
+
+div.body p, div.body dd, div.body li {
+    text-align: justify;
+    line-height: 130%;
+}
+
+div.body h1,
+div.body h2,
+div.body h3,
+div.body h4,
+div.body h5,
+div.body h6 {
+    font-family: {{ theme_headfont }};
+    background-color: {{ theme_headbgcolor }};
+    font-weight: normal;
+    color: {{ theme_headtextcolor }};
+    border-top: 1px solid {{ theme_headbordercolor }};
+    border-bottom: 2px solid {{ theme_headbordercolor }};
+    margin: 30px -20px 20px -20px;
+    padding: 3px 0 3px 10px;
+}
+
+div.body h1 { margin-top: 0; font-size: 200%; }
+div.body h2 { font-size: 160%; }
+div.body h3 { font-size: 140%; padding-left: 20px; }
+div.body h4 { font-size: 120%; padding-left: 20px; }
+div.body h5 { font-size: 110%; padding-left: 20px; }
+div.body h6 { font-size: 100%; padding-left: 20px; }
+
+a.headerlink {
+    color: {{ theme_headlinkcolor }};
+    font-size: 0.8em;
+    padding: 0 4px 0 4px;
+    text-decoration: none;
+}
+
+a.headerlink:hover {
+    background-color: {{ theme_headlinkcolor }};
+    color: white;
+}
+
+div.body p, div.body dd, div.body li {
+    text-align: justify;
+    line-height: 130%;
+}
+
+div.admonition p.admonition-title + p {
+    display: inline;
+}
+
+div.note {
+    background-color: #eee;
+    border: 1px solid #ccc;
+}
+
+div.seealso {
+    background-color: #ffc;
+    border: 1px solid #ff6;
+}
+
+div.topic {
+    background-color: #eee;
+}
+
+div.warning {
+    background-color: #ffe4e4;
+    border: 1px solid #f66;
+}
+
+p.admonition-title {
+    display: inline;
+}
+
+p.admonition-title:after {
+    content: ":";
+}
+
+pre {
+    padding: 5px;
+    background-color: {{ theme_codebgcolor }};
+    color: {{ theme_codetextcolor }};
+    line-height: 130%;
+    border: 2px solid {{ theme_codebordercolor }};
+    border-left: none;
+    border-right: none;
+}
+
+tt {
+    background-color: #ecf0f3;
+    padding: 0 1px 0 1px;
+/*    font-size: 0.95em;*/
+}
+
+.warning tt {
+    background: #efc2c2;
+}
+
+.note tt {
+    background: #d6d6d6;
+}

data/lib/amiba/frontend/public/javascript/MathJax/docs/rst/mjtheme/theme.conf

@@ -0,0 +1,30 @@
+[theme]
+inherit = basic
+stylesheet = mj.css
+pygments_style = sphinx
+
+[options]
+rightsidebar = false
+stickysidebar = false
+
+footerbgcolor    = #11303d
+footertextcolor  = #ffffff
+sidebarbgcolor   = #d4e9f7
+sidebartextcolor = #3a3a3a
+sidebarlinkcolor = #3a8942
+relbarbgcolor    = #191a19
+relbartextcolor  = #ffffff
+relbarlinkcolor  = #ffffff
+bgcolor          = #ffffff
+textcolor        = #222222
+headbgcolor      = #f2f2f2
+headtextcolor    = #20435c
+headlinkcolor    = #c60f0f
+headbordercolor  = #cccccc
+linkcolor        = #355f7c
+codebgcolor      = #f1f8ff
+codetextcolor    = #333333
+codebordercolor  = #6799b3
+
+bodyfont = sans-serif
+headfont = 'Trebuchet MS', sans-serif