scratch.xml

<?xml version="1.0" encoding="UTF-8" ?>

<!--********************************************************************
-->

<!-- Overall element for a Mathbook XML document; mandatory, always  -->
<!-- Experiment with the "xml:lang" attribute to see localization    -->
<!-- changes, the  xsl/localizations  directory has more information -->
<mathbook>
    <docinfo>
        <brandlogo url="https://cdn.rawgit.com/byoshiwara/MFG-html/master/" source="images/cover.png" /> 
        <latex-preamble>
            <package>cancel</package>
        </latex-preamble>
        <!--
        TeX/LaTeX macros can be written in the usual way.
        Whitespace and line breaks are irrelevant here.
        These are "write once, use everywhere".
        -->
        <cross-references text="type-hybrid" />
        <!--
        Extra packages, package options, and package settings for latex-based images.
        Inserted in the preamble for LaTeX output.
        Inserted in the preamble to each standalone latex-based image for HMTL SVG output.
        -->
        <latex-image-preamble>
        \usepackage{pgfplots}               % loads tikz package
        \usepackage{smartdiagram}           % for a circular diagram
        \pgfplotsset{axis x line = middle,
                     axis y line = middle}
        \usetikzlibrary{backgrounds}
        \usetikzlibrary{arrows,matrix}
        </latex-image-preamble>
        <!--
        The Sage Notebook has its own interface and worksheet list.
        To use the sorting features optimally, it helps to have subdivisions
        begin with the same short prefix.  An "initialism" (nee acronym)
        here will be used for that purpose if present.  This is only employed
        for producing Sage notebook versions and in the title shown in the
        browser. (If not present, you will get a harmless warning just for
        Sage worksheet production.)
        -->
        <initialism>Scratch</initialism>
        <!--
        With a <feedback> element, in the HTML version, you get a button
        for reporting typos and errors.  You might link to a Google Docs
        spreadsheet or something similar.  Default is to get a button
        labeled "Feedback", which will be localized to your target language.
        You can override this with some text of your choosing, but then you
        lose the localization feature.
        -->
        <feedback>
            <url>not-implemented.html</url>
             <!-- <text>My Button Text</text>  -->
        </feedback>

        <!--
        "Names" for various parts of a document are determined exactly
        once for each language, ensuring consistency and saving you the
        bother of always typing them in.  These can be found in the
        files in the  xsl/localizations  directory.

        You can make a document-specific, global override.  Here we
        decide we have no need for any "proposition"s and repurpose
        that environment in US English as a "Conundrum."

        See the localization file for more on language codes, and realize
        that US English is the default if there is no "lang" attribute
        given on the document.
        -->
        <rename element="warning" lang="en-US">Caution</rename>

        <!-- Various third-party add-ons need some sort of token     -->
        <!-- Using an element here serves two purposes               -->
        <!--   (1)  it is a flag to enable the addon                 -->
        <!--   (2)  it holds the token and MBX supplies generic code -->
        <!-- This is for the Google Custom Search Engine in HTML     -->
        <search>
            <google>
                <cx>006592449927388994635:w0x-ox5bpme</cx>
            </google>
        </search>

        <!-- Images in HTML output may carry a discreet list of links    -->
        <!-- to "archival" versions of images in a variety of formats.   -->
        <!-- Authors have complete freedom to do this as they choose,    -->
        <!-- along with complete responsibility to provide the actual    -->
        <!-- files, with proper filenames and suffices.  Search this     -->
        <!-- source file for "archive=" to see particular examples.      -->
        <!-- The following demonstrates a global specification, which    -->
        <!-- we just use for testing - it just makes totally fake links. -->
        <!--
        <images>
            <archive>One Two Three</archive>
        </images>
        -->

        <!-- Demonstration of subtree specifications for archive formats -->
        <!-- (Do not use in concert with above global test)              -->
        <!-- Chapter on graphics, fake "A B" links throughout            -->
        <!-- No other part of the @archive scheme is affected            -->
        <!-- Two images, inside figures, within graphics chapter         -->
        <!--   1) one has "A B" links turned off                         -->
        <!--   2) single link "exceptional"                              -->
        <!--
        <images>
            <archive from="graphics">A B</archive>
            <archive from="figure-asymptote-levers" />
            <archive from="figure-asymptote-contour-plot">exceptional</archive>
        </images>
        -->

    </docinfo>

    <!--
    The article element is top-level for anything short of a book.
    There is a book element, which is not demonstrated here.
    The "xml:id" attribute will be used for the filename of the
    HTML output.
    -->
    <article xml:id="scratch">
        <title>Testing Snippets</title>
        <subtitle>Just checking ptx coding</subtitle>

        <!--
        The frontmatter contains a variety of items that precede
        the actual content.  They should be placed in the proper order,
        here the title material should precede a table of contents.
        They differ from "docinfo" items in that they will be *content*
        that a reader will actually see.

        The xml:id string is used to form a filename for a webpage.
        Setting this one to "index" makes for a good default page
        when you host your project on a server.
        -->

        <frontmatter xml:id="index">
            <!--
            Items typically on the main title page of a book,
            but here as an article they are handled more compactly
             -->

            <titlepage>

               <!-- There can be several authors here -->
                <author>
                    <personname>Nemo</personname>
                    <!-- department here is one line, so unstructured -->
                    <department>Department of Retirement</department>
                    <!-- institution uses two lines, so structured as such -->
                    <institution>
                        <line>Leisure U</line>
                        <line>Atascadero, CA</line>
                    </institution>
                    <email>byoshiwara@gmail.com</email>
                </author>

                <!-- Can set date manually or use the "today" element -->
                <date><today /></date>

            </titlepage>

            <abstract>
                <p>This is a sample of many of the things you can do with <pretext />.  Sometimes the math makes sense, sometimes it seems to be written in the first person, sort of like this Abstract.</p>
            </abstract>
            <!--
            Acknowledgements, dedications, colophon (ISBN, copyright, etc)
            are supported in the book document type.  Such a diverse range
            is not yet available for articles.  Send requests.
             -->
        </frontmatter>

        <!--
        Articles have sections, which have subsections,
        which have subsubsections.These are all "containers"
        and so line breaks and extraneous whitespace gets
        scrubbed.  Use indentation and line breaks liberally
        within containers to make the structure of your
        source readable.
        -->

        <section>
            <title>Introduction</title>

            <!--
            URLs can be done in a traditional fashion, as in the
            abstract below. Or you can make an empty element and the URL in
            the href attribute will be the content you click on.  See the
            example near the discussion of Asymptote.
            -->

<p>
    When using polynomial division, it helps to write the polynomials in descending powers of the variable. If the numerator is missing any terms, we can insert terms with zero coefficients so that like powers will be aligned. For example, to perform the division
    <me>\frac{3x - 1 + 4x^3}{2x-1}</me>
    we first write the numerator in descending powers as <m>4x^3 + 3x - 1</m>. We then insert <m>0x^2</m> between <m>4x^3</m> and <m>3x</m> and set up the quotient as</p><p>
    <sidebyside width="33%"><image source="images/fig-long-division4.jpg"><description>long division box</description></image></sidebyside>
    We then proceed as in <xref ref="example-long-division" text="type-global"/>. You can check that the quotient is
    <me>2x^2 + x + 2 + \frac{1}{2x-1}</me>
</p>


            <p>Generated: <today />, <timeofday /></p>

        </section>


        <backmatter xml:id="backmatter">
            <title>Reference</title>

            <appendix>
                <title>Notation</title>
                <p>This is some notation introduced in the article.</p>
                <notation-list />
            </appendix>

            <appendix>
                <title>Solutions to Selected Exercises</title>
                <solution-list />
            </appendix>

            <appendix xml:id="appendix-results">
                <title>List of Results</title>

                <p>We didn't bother putting anything in the appendix.</p>

                <list-of elements="  theorem corollary" divisions="section    subsection " empty="no" />
            </appendix>

            <appendix>
                <title>Index</title>

                <p>There is nothing here.</p>

                <paragraphs>
                    <title>Bully Pulpit: Index Headings</title>

                    <p>Professionals do not capitalize the headings (entries) of an index, unless it is a proper noun (name, place, <etc />).  We do not provide any enforcement of this advice, nor any assistance.  It is your responsibility to provide quality source material in this regard.</p>
                </paragraphs>

                <paragraphs>
                    <title>Note</title>

                    <p>Most all of the index entries below to page 2 (PDF output) are just from a suite of non-sensical tests.  These are harder to recognize in the <init>HTML</init> output.</p>
                </paragraphs>
            </appendix>

            <!-- Bibliography/References can appear anywhere, -->
            <!-- but these are in the backmatter              -->

            <references>
                <title>References</title>

                <biblio type="raw" xml:id="biblio-judson-AATA">Tom Judson, <title>Abstract Algebra: Theory and Applications</title>.
                <note xml:id="note-judson-AATA"><p>Another online, open-source offering.</p></note>
                </biblio>

                <biblio type="raw" xml:id="biblio-lay-article">David C. Lay, <title>Subspaces and Echelon Forms</title>. <journal>The College Mathematics Journal</journal>, January 1993, <volume>24</volume> <number>1</number>, 57<ndash />62.</biblio>

            </references>

            <index>
                <title>Index</title>
                <index-list />
            </index>

            <colophon>
                <p>This article was authored in <pretext />.</p>
            </colophon>
        </backmatter>
    </article>
</mathbook>