bugfix for iframes
fix Cursor::insertCmd/LatexCommandInput::renderCommand

wasn't correctly merged from master:
- master refactored LatexCommandInput::renderCommand to just call
  Cursor::insertCmd, and added a public API call that calls
  Cursor::insertCmd
- dev changed how fragments worked, which changed
  LatexCommandInput::renderCommand. In the merge conflict, the dev
  version of it was kept

This commit now fixes insertCmd and refactors dev's renderCommand
to use it.
fix #120 TextBlocks couldn't be created

This was because when we switched MathCommand::createBlocks from munging
pointers to calling Node::adopt in 3d9ec92, there was a bug where we
accidentally removed the .blur() call on all the blocks, which was fixed
in caab952 by calling .blur() on all the blocks in
MathCommand::createBefore, after the createBlocks call. Unbeknownst to
us, TextBlock overrides createBlocks not just to create an
InnerTextBlock rather than a MathBlock as it's child, but also
intentionally didn't call .blur() (which removes the entire TextBlock,
since it thinks it's being called because the cursor left the TextBlock
and the TextBlock is empty).
add test case for LaTeX parsing of \text{}
scaled elements are not non-leaf

rather, they are different semantic classes that both need to be
inline-block
fix opaque matrixed el's in IE8, eps. nthroots

since IE8 doesn't support CSS transforms, the Matrix filter is used to
stretch square roots etc, which antialiases wrong when the background
isn't opaque, so we set them all to have an opaque background.

The problem is that, in particular, the [n] of nthroots gets obscured by
the opaque background of the square root radical.

After much research and trial and error, I've ended up using the Chroma
filter as the only way to make the background transparent. This is
plagued with problems, documented in [the wiki page on Transforms][1].

[1]: https://github.com/mathquill/mathquill/wiki/Transforms
Merge pull request #105 from bahblah/master

Bugfix for iframes
fix drag-to-select in iframe: use ownerDocument

use fix from #105: attach mouse{move,up} handlers to [ownerDocument][1]
instead of the document that is local to the window this JavaScript is
being run in.

Also, it was sloppy of me not to have cited this in the original
implementation, but the reason we attach the mouse{move,up} handlers to
the document in the first place is [this Quirksmode article][2].

[1]: http://reference.sitepoint.com/javascript/Node/ownerDocument
[2]: http://www.quirksmode.org/js/dragdrop.html
selection should highlight stretched elements too
\sqrt's HTML template uses non-leaf

instead of custom CSS classes. Also fixes tall square roots being
highlighted wrong when selected (e.g. selecting \sqrt{\frac{1}} no
longer looks so weird).
allow typing/pasting of stupid Latin-1 numeralikes

see huge comment
first stab at updating the README for dev
s/dom/HTML DOM/
s/math dom/edit tree/
Merge branch 'dev'

Conflicts:
	src/rootelements.js
v0.9.0
add `make publish` for publishing to mathquill.github.com
correct the urls for the scripts
fix #135 in Safari 5.1 can't type over selection

Safari 5.1 (at least), after selecting something and then typing, the
textarea is incorrectly reported as selected during the input event, and
defer()-ed functions were only called by the nextmost flush(). Now,
instead of flush()-ing, we repeatedly call checkTextarea() to check for
typed or pasted text, so as long as everything eventually stabilizes,
we'll correctly read the typed or pasted text.
use npm and the node_modules directory for mocha/pjs