Update html docs to include recent changes in rst files
git-svn-id: https://mathjax.svn.sourceforge.net/svnroot/mathjax/trunk@602 b8fd5906-0fad-46e2-a0d3-10d94ff285d1
This commit is contained in:
parent
960c0db2ab
commit
311b800451
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
@ -199,7 +199,7 @@ information about the valid methods of specifying a callback.
|
|||
Creating a Callback Explicitly
|
||||
==============================
|
||||
|
||||
When you call a method that accpets a callback, you usually pass it a
|
||||
When you call a method that accepts a callback, you usually pass it a
|
||||
callback specification (like in the examples above), which *describes*
|
||||
a callback (the method will create the actual `Callback` object, and
|
||||
return that to you as its return value). You don't usually create
|
||||
|
|
|
@ -53,8 +53,8 @@ One way that MathJax makes use of this feature is in configuring its
|
|||
various extensions. The extension may not be loaded when the user's
|
||||
configuration code runs, so the configuration code can't modify the
|
||||
extension because it isn't there yet. Fortunately, most extensions
|
||||
signal when they are set up via an ``Extension [name] Ready`` message,
|
||||
so the configuration code can set up a listener for that message, and
|
||||
signal when they are loaded and initialized via an ``Extension [name] Ready`` message,
|
||||
so the configuration code can implement a listener for that message, and
|
||||
have the listener perform the configuration when the message arrives.
|
||||
But even if the extension *has* already been loaded, this will still
|
||||
work, because the listener will receive the ready signal even if it
|
||||
|
@ -70,7 +70,7 @@ sender can also indicate that past messages are not appropriate for
|
|||
new listeners. It does this by clearing the message history so that
|
||||
new listeners have no old posts to hear.
|
||||
|
||||
The actual message passed along the signal can be anything, but is
|
||||
The actual message passed along by the signal can be anything, but is
|
||||
frequently a string constant indicating the message value. It could
|
||||
also be a JavaScript array containing data, or an object containing
|
||||
`key:value` pairs. All the listeners receive the data as part of the
|
||||
|
@ -81,7 +81,7 @@ Creating a Listener
|
|||
|
||||
MathJax maintains two separate signal channels: the `startup signal`
|
||||
and the `processing signal` (or the `hub signal`). The startup signal
|
||||
is where the messages about different components startup up and
|
||||
is where the messages about different components starting up and
|
||||
becoming ready appear. The processing signal is where the messages
|
||||
are sent about processing mathematics, like the ``New Math`` messages
|
||||
for when newly typeset mathematics appears on the page. The latter is
|
||||
|
|
|
@ -41,7 +41,7 @@ TeX and LaTeX in HTML documents
|
|||
|
||||
Keep in mind that your mathematics is part of an HTML document, so you
|
||||
need to be aware of the special characters used by HTML as part of its
|
||||
markup. There can not be HTML tags within the math delimiters (other
|
||||
markup. There cannot be HTML tags within the math delimiters (other
|
||||
than ``<BR>``) as TeX-formatted math does not include HTML tags.
|
||||
Also, since the mathematics is initially given as text on the page,
|
||||
you need to be careful that your mathematics doesn't look like HTML
|
||||
|
@ -61,7 +61,7 @@ HTML). When this happens, the browser will think the tag continues up
|
|||
to the next ``>`` in the document (typically the end of the next
|
||||
actual tag in the HTML file), and you may notice that you are missing
|
||||
part of the text of the document. In the example above, the `` we
|
||||
have ...`` will not be displayed because the browsers thinks it is
|
||||
have ...`` will not be displayed because the browser thinks it is
|
||||
part of the tag starting at ``<y``. This is one indication you can
|
||||
use to spot this prooblem; it is a common error and should be avoided.
|
||||
|
||||
|
|
|
@ -207,7 +207,7 @@ information about the valid methods of specifying a callback.</p>
|
|||
</div>
|
||||
<div class="section" id="creating-a-callback-explicitly">
|
||||
<h3>Creating a Callback Explicitly<a class="headerlink" href="#creating-a-callback-explicitly" title="Permalink to this headline">¶</a></h3>
|
||||
<p>When you call a method that accpets a callback, you usually pass it a
|
||||
<p>When you call a method that accepts a callback, you usually pass it a
|
||||
callback specification (like in the examples above), which <em>describes</em>
|
||||
a callback (the method will create the actual <cite>Callback</cite> object, and
|
||||
return that to you as its return value). You don’t usually create
|
||||
|
|
Binary file not shown.
File diff suppressed because one or more lines are too long
|
@ -97,8 +97,8 @@ it starts listening after they were sent.</p>
|
|||
various extensions. The extension may not be loaded when the user’s
|
||||
configuration code runs, so the configuration code can’t modify the
|
||||
extension because it isn’t there yet. Fortunately, most extensions
|
||||
signal when they are set up via an <tt class="docutils literal"><span class="pre">Extension</span> <span class="pre">[name]</span> <span class="pre">Ready</span></tt> message,
|
||||
so the configuration code can set up a listener for that message, and
|
||||
signal when they are loaded and initialized via an <tt class="docutils literal"><span class="pre">Extension</span> <span class="pre">[name]</span> <span class="pre">Ready</span></tt> message,
|
||||
so the configuration code can implement a listener for that message, and
|
||||
have the listener perform the configuration when the message arrives.
|
||||
But even if the extension <em>has</em> already been loaded, this will still
|
||||
work, because the listener will receive the ready signal even if it
|
||||
|
@ -112,7 +112,7 @@ to hear old messages when it attaches itself to a signal object. The
|
|||
sender can also indicate that past messages are not appropriate for
|
||||
new listeners. It does this by clearing the message history so that
|
||||
new listeners have no old posts to hear.</p>
|
||||
<p>The actual message passed along the signal can be anything, but is
|
||||
<p>The actual message passed along by the signal can be anything, but is
|
||||
frequently a string constant indicating the message value. It could
|
||||
also be a JavaScript array containing data, or an object containing
|
||||
<cite>key:value</cite> pairs. All the listeners receive the data as part of the
|
||||
|
@ -121,7 +121,7 @@ message, and can act on it in whatever ways they see fit.</p>
|
|||
<h2>Creating a Listener<a class="headerlink" href="#creating-a-listener" title="Permalink to this headline">¶</a></h2>
|
||||
<p>MathJax maintains two separate signal channels: the <cite>startup signal</cite>
|
||||
and the <cite>processing signal</cite> (or the <cite>hub signal</cite>). The startup signal
|
||||
is where the messages about different components startup up and
|
||||
is where the messages about different components starting up and
|
||||
becoming ready appear. The processing signal is where the messages
|
||||
are sent about processing mathematics, like the <tt class="docutils literal"><span class="pre">New</span> <span class="pre">Math</span></tt> messages
|
||||
for when newly typeset mathematics appears on the page. The latter is
|
||||
|
|
|
@ -78,7 +78,7 @@ you need a LaTeX-to-HTML converter, you should consider <a class="reference exte
|
|||
<h2>TeX and LaTeX in HTML documents<a class="headerlink" href="#tex-and-latex-in-html-documents" title="Permalink to this headline">¶</a></h2>
|
||||
<p>Keep in mind that your mathematics is part of an HTML document, so you
|
||||
need to be aware of the special characters used by HTML as part of its
|
||||
markup. There can not be HTML tags within the math delimiters (other
|
||||
markup. There cannot be HTML tags within the math delimiters (other
|
||||
than <tt class="docutils literal"><span class="pre"><BR></span></tt>) as TeX-formatted math does not include HTML tags.
|
||||
Also, since the mathematics is initially given as text on the page,
|
||||
you need to be careful that your mathematics doesn’t look like HTML
|
||||
|
@ -96,7 +96,7 @@ HTML). When this happens, the browser will think the tag continues up
|
|||
to the next <tt class="docutils literal"><span class="pre">></span></tt> in the document (typically the end of the next
|
||||
actual tag in the HTML file), and you may notice that you are missing
|
||||
part of the text of the document. In the example above, the `` we
|
||||
have ...`` will not be displayed because the browsers thinks it is
|
||||
have ...`` will not be displayed because the browser thinks it is
|
||||
part of the tag starting at <tt class="docutils literal"><span class="pre"><y</span></tt>. This is one indication you can
|
||||
use to spot this prooblem; it is a common error and should be avoided.</p>
|
||||
<p>Usually, it is sufficient to simply put spaces around these symbols to
|
||||
|
|
Loading…
Reference in New Issue
Block a user