+ Now click Submit to see it rendered below...
@@ -405,17 +773,18 @@ QUICKSTART
You should see
=\int\limits_{-\infty}^x e^{-t^2}dt) if you submit the sample expression
- already in the box.
+ src="../cgi-bin/mimetex.cgi?\normalsize
+ f(x)=\int\limits_{-\infty}^x e^{-t^2}dt"
+ alt="" border=0 style="Vertical-Align:-11px">
+ if you submit the sample expression already in the box.
And the <img> tag to embed this same integral anywhere
in your own document is
<img src="../cgi-bin/mimetex.cgi?\large f(x)=\int_{-\infty}^xe^{-t^2}dt"
alt="" border=0 align=middle>
- You can see numerous additional examples illustrating html
- <img> tags using mimeTeX by viewing this page's source.
+
The typical mimeTeX <img> tag has the form
<img src="../cgi-bin/mimetex.cgi?any valid LaTeX/mimeTeX expression"
alt="" border=0 align=middle>
@@ -423,12 +792,12 @@ QUICKSTART
page containing these tags to your compiled mimetex.cgi program, and
where any valid LaTeX/mimeTeX expression
is pretty much any valid LaTeX math expression:
- - As discussed in the Introduction,
+
+
- There are occasional exceptions where I couldn't
+ program mimeTeX to recognize valid LaTeX syntax.
+ One particular "gotcha" is that mimeTeX bindings
are pretty much left-to-right. Thus, for example, although
mimeTeX correctly interprets \frac12 as well as
\frac1{x^2}, etc, the legal LaTeX expression
@@ -437,18 +806,20 @@ QUICKSTART
the same way x^\alpha12 would be interpreted, which is
nonsense for \frac. The same "gotcha" also applies to
other combinations of commands, e.g., you must write
- \sqrt{\frac\alpha\beta}, etc.
+ \sqrt{\frac\alpha\beta}, or
+ \frac\alpha{\sqrt\beta}, etc.
The Syntax Reference section
- contains much additional information. Or you can just begin
+ contains much additional information.
+ - Besides such exceptions, mimeTeX
+ also provides various LaTeX extensions. For example, font size
directives like \Large are permitted within mimeTeX
- math mode expressions. But note well: if you take
- advantage of mimeTeX extensions, your math mode expressions
- will no longer be accepted by standard TeX engines.
+ math mode expressions, but flagged as errors by LaTeX.
+
+ Some font examples ...
Finally, illustrated below are some examples of fonts and symbols
- available with mimeTeX. All symbols and sizes from cmr, cmmi. cmsy,
- cmex and rsfs should be available, but they're not all shown.
- Mathbb symbols are also available but not shown.
+ available with mimeTeX. All symbols and sizes from cmr, cmmi,
+ cmmib (use \mathbf{ }), cmsy, cmex, bbold (use
+ \mathbb{ }), rsfs (use \mathscr{ }),
+ stmary and cyrillic wncyr (use {\cyr } or
+ \cyr{ }) should be available, but they're not all shown.
And also not shown are various "constructed symbols" like \sqrt,
accents, etc. The illustrated font sizes are numbered 4=\Large,
- 3=\large and 2=\normalsize (not shown are 5=\LARGE, 1=\small and
- 0=\tiny).
+ 3=\large and 2=\normalsize (not shown are 7=\Huge, 6=\huge,
+ 5=\LARGE, 1=\small and 0=\tiny).
cmmi latin uppercase, and lowercase
2$\pi&2$\rho&2$\sigma&2$\tau&2$\upsilon&2$\phi&2$\chi&2$\psi&2$\omega}"
alt="" border=0 align=middle>
-cmsy symbols at mimeTeX font size 3
+cmsy symbols at mimeTeX font size 3
+(operators shown large are automatically "promoted"
+to the larger size in \displaystyle mode)
1$\rm~117-127:~&\sqcap&\sqsubseteq&\sqsupseteq&\S&\dag&\ddag&\P&\clubsuit&
\Diamond&\Heart&\spadesuit}" alt="" border=0 align=middle>
-a few other cmmi and cmr symbols at mimeTeX font size 4
+a few other cmmi, cmr, stmary and wncyr symbols
+at mimeTeX font size 4
+1$\rm~cmr:~&\ss&\ae&\oe&\AE&\OE \\
+1$\rm~stmary:~&\moo&\Lbag&\Rbag&\lightning&\llbracket&\rrbracket&
+\subsetpluseq&\supsetpluseq&\Yup&\Ydown\\
+1$\rm~wncyr:~&\cyr A&\cyr a&\cyr B&\cyr b&\cyr V&\cyr v&\cyr G&\cyr g&
+\cyr D&\cyr d&\cyr Dj&\cyr dj&\cyr\=E&\cyr\=e&\cyr Zh&\cyr zh}"
+alt="" border=0 align=middle>
Very briefly, download
Form TX
and follow the included instructions.
In principle, you automatically own the copyright
to anything you write the moment it's on paper. In practice,
if the matter comes under dispute, the courts look _very_ favorably
- on you for demonstrating your intent by registering the copyright.
-
+ on you for demonstrating your intent by registering the copyright.
+ For example, courts will stop unauthorized use of unregistered
+ material, but monetary damages are awarded _only_ if you
+ register the copyright before infringement occurs.
Very quickly --- download
-
-
+
+
mimetex.zip and then type
@@ -906,149 +1297,102 @@ SECTION II. BUILDING MIMETEX
I've built and run mimeTeX under Linux and NetBSD using gcc. The source
- code is ansi-standard C, and should compile and execute under all
- environments without any change whatsoever. Build instructions below
+ code is ansi-standard C, and should compile and run under all
+ environments without change. Instructions below
are for Unix. Modify them as necessary for your particular situation
(note the -DWINDOWS switch if applicable).
- A summary of the steps needed to build mimeTeX is
+
+
+ The steps needed to download and compile mimeTeX are
- Download and unzip
-
-
- mimetex.zip in any convenient working directory.
+
+
+ mimetex.zip in any convenient working directory.
+ Your working directory should now contain
+
+ | README | mimeTeX release notes |
+ | COPYING | GPL license, under which you may use
+ mimeTeX |
+ | mimetex.c | mimeTeX source program and all required
+ functions |
+ | mimetex.h | header file for mimetex.c (and for
+ gfuntype.c) |
+ | gfuntype.c | parses output from gftype -i
+ and writes bitmap data |
+ | texfonts.h | output from several gfuntype runs,
+ needed by mimetex.c |
+ | gifsave.c | gif library by Sverre H. Huseby
+ http://shh.thathost.com
+ |
+ | mimetex.html | this file, the mimeTeX
+ user's manual |
+
+
+ Note: all files use Unix line termination, i.e., linefeeds
+ (without carriage returns) signal line endings. Conversion for
+ Windows PC's, Macs, VMS, etc, can usually be accomplished by
+ unzip's -a option, i.e., unzip -a mimetex.zip
+
- To compile an executable that emits anti-aliased gif images
- (which is how the page you're viewing is displayed)
- cc -DAA mimetex.c gifsave.c -lm -o mimetex.cgi
- - or, to emit gif images without anti-aliasing
- cc -DGIF mimetex.c gifsave.c -lm -o mimetex.cgi
+ (which is recommended for most uses), just type the following
+ command from the Unix shell
+
+ cc -DAA mimetex.c gifsave.c -lm -o mimetex.cgi
+ - Or, to compile an executable that emit gif images
+ without anti-aliasing
+
+ cc -DGIF mimetex.c gifsave.c -lm -o mimetex.cgi
- Alternatively, to compile an executable that emits mime xbitmaps
- cc -DXBITMAP mimetex.c -lm -o mimetex.cgi
+
+ cc -DXBITMAP mimetex.c -lm -o mimetex.cgi
- Compile Notes:
- If (and only if) you're compiling a Windows executable with
the -DAA or -DGIF option (but not -DXBITMAP), then
add -DWINDOWS . For example,
- cc -DAA -DWINDOWS
- mimetex.c gifsave.c -lm -o mimetex.cgi
+ gcc -DAA -DWINDOWS
+ mimetex.c gifsave.c -lm -o mimetex.exe
The above Unix-like syntax works with
MinGW and
djgpp
Windows compilers, but probably not with most others,
- where it's only intended as a "template".
+ where it's only intended as a "template".
+
+ Explanation: mimeTeX writes gif bytes directly to stdout, as usual
+ for cgi's. But Windows treats stdout as a character stream,
+ interpreting any hex 0A byte as an <lf>, and automatically
+ preceding it with a spurious hex 0D <cr> byte. The
+ -DWINDOWS switch compiles in a non-portable, Windows-specific
+ _setmode() call that sets stdout to binary mode.
+ - If you're compiling for Windows and would prefer
+ to install mimeTeX as a Win32 DLL, see the
+
+ Code Project developed by
+ Shital Shah, and
+ download
+ eq2img_all.zip containing Shital's latest code.
-
-
- And a summary of the steps needed to install mimeTeX is
-
- - Just mv mimetex.cgi to your server's cgi-bin/
- directory, set permissions as necessary, and you're all done.
- - Now, to quickly test your mimetex.cgi, try typing a url into
- your browser's locator window something like
- http://www.yourdomain.com/cgi-bin/mimetex.cgi?x^2+y^2
- which should display
-
 in the upper-left corner of your window.
- - After the preceding test succeeds, you can optionally
- "regression test" all mimeTeX features as follows:
- - mv mimetex.html (this file) to your server's htdocs/
- directory
- - If the relative path from htdocs to cgi-bin isn't
- ../cgi-bin then edit mimetex.html and change the
- few dozen occurrences as necessary (globally changing
- ../cgi-bin/mimetex.cgi should work).
- - Now visit your page
- http://www.yourdomain.com/mimetex.html
- - Once mimetex.html displays properly, you can assume
- everything is working, and can begin authoring html documents
- using mimetex.cgi to render your own math.
+
+ The gfuntype program is only needed if you plan to change the
+ font information in texfonts.h, as explained in
+ Appendix IVa below.
+ In that case, compile gfuntype with the command
+
+ cc gfuntype.c mimetex.c -lm -o gfuntype
- Any problems with the above?
- Read the more detailed instructions below.
-
-
-
-
- Download
-
-
- mimetex.zip and unzip it in any convenient working directory.
- Your working directory should now contain
-
- | README | mimeTeX release notes |
- | LICENSE | GPL license, under which you may use
- mimeTeX |
- | mimetex.c | mimeTeX source program and all required
- functions |
- | mimetex.h | header file for mimetex.c (and for
- gfuntype.c) |
- | gfuntype.c | parses output from gftype -i
- and writes bitmap data |
- | texfonts.h | output from several gfuntype runs,
- needed by mimetex.c |
- | gifsave.c | gif library by Sverre H. Huseby
-
- http://shh.thathost.com |
- | mimetex.html | this file, mimeTeX tutorial and
- user's manual |
-
- Note: all files use Unix line termination, i.e., linefeeds
- (without carriage returns) signal line endings. Conversion for
- Windows PC's, Macs, VMS, etc, can usually be accomplished by
- unzip's -a option, i.e., unzip -a mimetex.zip
-
-
-
-
- To compile a mimeTeX executable that emits anti-aliased gif images
- (which is recommended for most uses) issue the command
- cc -DAA mimetex.c gifsave.c -lm -o mimetex.cgi
-
-
- Or, for an executable that emits gif images without anti-aliasing,
- issue the command
- cc -DGIF mimetex.c gifsave.c -lm -o mimetex.cgi
-
-
- Alternatively, to compile a mimeTeX executable that emits
- mime xbitmaps, just issue the command
- cc -DXBITMAP mimetex.c -lm -o mimetex.cgi
-
-
- Compile Notes:
- - If (and only if) you're compiling a Windows executable with
- the -DAA or -DGIF option (but not -DXBITMAP), then
- add -DWINDOWS . For example,
- cc -DAA -DWINDOWS
- mimetex.c gifsave.c -lm -o mimetex.cgi
- The above Unix-like syntax works with
- MinGW and
- djgpp
- Windows compilers, but probably not with most others,
- where it's only intended as a "template".
- Explanation: mimeTeX writes gif bytes directly to
- stdout, as usual for cgi's. But Windows treats
- stdout as a character stream, interpreting any hex 0A byte
- as an <lf>, and automatically preceding it with
- a spurious hex 0D <cr> byte. The -DWINDOWS switch
- compiles in a non-portable, Windows-specific _setmode()
- call that sets stdout to binary mode.
-
-
- Several other optional compile-line options
+ That's all there is to compiling mimeTeX.
+ Several other optional compile-line options
available for mimetex.c are discussed below.
- The gfuntype program is only needed if you plan to change the
- font information in texfonts.h, as explained in
- Appendix IVa below.
- In that case, compile gfuntype with the command
- cc gfuntype.c mimetex.c -lm -o gfuntype
-
- That's all there is to building mimeTeX. You can now test your
- mimetex.cgi executable from the Unix command line by typing, e.g.,
- ./mimetex.cgi "x^2+y^2" which should emit two ascii
- rasters something like the following
+ Immediately after compiling mimeTeX, test your new executable
+ by typing ./mimetex.cgi "x^2+y^2"
+ from the Unix shell (or mimetex "x^2+y^2"
+ from the Windows Command Prompt), which should emit
+ two "ascii rasters" something like the following
Ascii dump of bitmap image... Hex dump of colormap indexes...
...........**....................**... ..........1**1...................1**1..
..........*..*......*...........*..*.. ..........*23*......*............*23*..
@@ -1069,32 +1413,81 @@ Ascii dump of bitmap image...
grayscale colormap indexes assigned to neighboring pixels, and with
the rgb value for each index.) Just typing ./mimetex.cgi
without an argument should produce ascii rasters for the default
- expression f(x)=x^2. If you see the two ascii rasters then your
- binary's good, so mv it to your server's cgi-bin/ directory and
- set permissions as necessary.
-
-
-
- Once mimetex.cgi is working, mv it to your server's cgi-bin/
- directory (wherever cgi programs are expected), and chmod/chown it
- if necessary. Then mv mimetex.html to your server's htdocs/
- directory. Now point your browser to www.yourdomain.com/mimetex.html ,
- and you should see a page identical to this one.
-
- Note: the two directories are typically of the form
- somewhere/www/cgi-bin/ and somewhere/www/htdocs/ , so I set up
- mimtex.html to get mimetex.cgi from the relative path ../cgi-bin/.
- If your directories are non-conforming, you may have to edit the
- few dozen occurrences of ../cgi-bin/mimetex.cgi in mimetex.html .
- Sometimes a suitable symlink works; if not, you'll have to edit.
- Globally changing ../cgi-bin/mimetex.cgi often works.
-
- Either way, once mimetex.html displays properly, you can assume
- everything is working, and can begin authoring html documents using
- mimetex.cgi to render your own math.
+ expression f(x)=x^2. If you see these two ascii rasters then
+ your binary's good. Otherwise, you must find and fix the problem
+ before proceeding.
+
+
+
+
+ Once you've successfully tested mimetex.cgi from the Unix shell
+ (or mimetex.exe from the Windows Command Prompt),
+ the steps needed to install mimeTeX are
+
+ - mv mimetex.cgi (or move mimetex.exe)
+ to your server's cgi-bin/ directory, wherever cgi
+ programs are expected.
+ - Now you may need to chmod 755 mimetex.cgi
+ and/or chown it, too, depending on your server's
+ requirements. Contact your system administrator or ISP
+ if you're not already familiar with this information.
+ - Once mimetex.cgi is moved to your server's cgi-bin/
+ directory, with permissions and owner set as necessary,
+ you're all done.
+
+
+ Immediately after installing mimeTeX, test your new mimetex.cgi
+ by typing a url into your browser's locator window something like
+
+ http://www.yourdomain.com/cgi-bin/mimetex.cgi?x^2+y^2
+ which should display
+ 
+ in the upper-left corner of your window,
+ just like clicking this link does, which tests my mimetex.cgi,
+
+ http://www.forkosh.com/cgi-bin/mimetex.cgi?x^2+y^2
+ If you see the same 
+ image from the yourdomain link, then you've completed
+ a successful mimeTeX installation.
+
+ If you don't see the image, then your installation failed.
+ If your earlier post-compilation "ascii raster" test
+ succeeeded, then the problem is probably some server-specific
+ installation requirement. First make sure you installed mimetex.cgi
+ in the correct cgi-bin/ directory, set the correct chmod
+ permissions, and typed the correct url into your browser's locator
+ window. Then contact your system administrator or ISP,
+ and ask how to install cgi programs on your server.
+
+ After you've successfully installed mimeTeX, and both preceeding tests
+ have succeeded, you can optionally "regression test"
+ all mimeTeX features as follows:
+
+ - mv mimetex.html (this file) to your server's
+ htdocs/ directory
+ - Paths to cgi-bin/ and htdocs/ directories
+ are typically path/www/cgi-bin/ and
+ path/www/htdocs/, so I set up mimtex.html
+ to access mimetex.cgi from the relative path ../cgi-bin/.
+ If your directories are non-conforming, you may have to edit
+ the few dozen occurrences of ../cgi-bin/mimetex.cgi
+ in your mimetex.html page. Sometimes a suitable symlink works;
+ if not, you'll have to edit. Globally changing
+ ../cgi-bin/mimetex.cgi usually works.
+ - Now visit your page
+ http://www.yourdomain.com/mimetex.html
+ - Once your mimetex.html displays properly, you can assume
+ everything is working, and can begin authoring html documents
+ using mimetex.cgi to render your own math.
+
+
+ That's all there is to installing mimeTeX. .
-
+
In addition to -DAA or -DGIF or -DXBITMAP (along with -DWINDOWS
when necessary) on the mimetex.c compile line, as discussed above,
@@ -1125,9 +1518,9 @@ Ascii dump of bitmap image...
algorithm for anti-aliasing, which is applied to the
existing set of bitmap fonts. This lowpass filter applies
weights  to neighboring pixels. The defaults
- weights are CENTERWT=32, ADJACENTWT=3 and CORNERWT=1,
+ weights are CENTERWT=8, ADJACENTWT=2 and CORNERWT=1,
which you can adjust to control anti-aliasing.
-DCACHEPATH=\"path/\"
This option saves each rendered image to a file in directory
@@ -1143,20 +1536,35 @@ Ascii dump of bitmap image...
is relative to mimetex.cgi, and must be writable by it.
Files created under path/ are named
filename.gif, where filename
- is the 32-character MD5 hash of the LaTeX expression.
- When caching a new image, mimeTeX also
+ is the 32-character MD5 hash of your LaTeX expression.
+ If you're also using mimeTeX's
+ Vertical-Align: feature, prefix your
+ path/ with a leading % and write
+ -DCACHEPATH=\"%path/\"
+ instead. That leading % won't become part of
+ your cache directory's path/, but it will signal
+ mimeTeX to cache headers along with each image.
+ Otherwise, the Vertical-Align: information is lost,
+ and attempts to align cached images will fail.
+ When caching a new image, mimeTeX also
updates the file path/mimetex.log containing
a timestamp, filename and LaTeX expression for each new file
created. A sample entry looks like
---------------------------------------------------------------------
-2004-08-07:09:00:53am f8ccc8dd93c8eeb1d9c40b353ef781e0.gif
+2008-09-07:11:29:53am f8ccc8dd93c8eeb1d9c40b353ef781e0.gif
\LARGE x=\frac{-b\pm\sqrt{b^2-4ac}}{2a}
---------------------------------------------------------------------
+ -DDEFAULTSIZE=n
+ MimeTeX currently has eight font sizes numbered 0-7,
+ and always starts out in DEFAULTSIZE, whose default value is 3.
+ Specify -DDEFAULTSIZE=2 on the compile line if you prefer
+ mimeTeX to start in default size 2, etc.
-DDISPLAYSIZE=n
By default, operator limits like \int_a^b are rendered
\textstyle
 at font sizes \normalsize
and smaller, and rendered \displaystyle
![]() \textstyle, \displaystyle, \limits or
\nolimits directives in an expression always override
the DISPLAYSIZE default.
- -DNEWCOMMANDS=newcommands.h
+ -DGAMMA=gammacorrection
+ Applies gammacorrection to antialiased
+ gif images. Default is 1.25 (rather than the standard 2.2).
+ Specify 0.0 to turn off gamma correction (1.0 makes no
+ gamma correction but doesn't actually turn it off).
+ -DNEWCOMMANDS=\"newcommands.h\"
LaTeX-like \newcommand's are available in mimeTeX,
via the following facility to help you define your
own "new commands" during compilation. Edit a file named
- newcommands.h (or any filename you specify with the
- -DNEWCOMMANDS switch). For newcommands _without_
+ newcommands.h (or any filename you specify between
+ \"...\"'s with the -DNEWCOMMANDS=\"filename\"
+ switch). For newcommands _without_
arguments, your file should contain one or more lines
like the following examples:
{ "\\iint", NULL, "{\\int\\int}" },
@@ -1219,11 +1633,10 @@ Ascii dump of bitmap image...
To see many additional examples, search for the
uppercase string NEWCOMMANDS in mimetex.c, and look below that.
All the above examples are already there.
- -DNORMALSIZE=n
- MimeTeX currently has six font sizes numbered 0-5,
- and always starts out in NORMALSIZE, whose default value is 2.
- Specify -DNORMALSIZE=3 on the compile line if you prefer
- mimeTeX to start in default size 3, etc.
+ -DOPAQUE
+ By default, mimeTeX renders gif images with black symbols
+ on a transparent white background. Defining OPAQUE renders
+ images on an opaque background instead.
-DPATHPREFIX=\"path/\"
The \input{ } and
\counter{ } commands discussed below
@@ -1235,7 +1648,33 @@ Ascii dump of bitmap image...
defined as path/ if you want input files in some
other directory. And make sure your path/ ends
with / (or with \ for Windows).
- -DREFERER=\"domain\" or
+ -DPLUSBLANK -or-
+ -DPLUSNOTBLANK
+ mimeTeX receives your LaTeX math expression as a url
+ query string, in which blank spaces are often encoded
+ as %20 or as plus signs +, and
+ where actual plus signs are often encoded as %2B.
+ But these conventions aren't always respected,
+ and even when they are blank spaces may be either
+ %20 or +. The only ambiguity for
+ mimeTeX is whether or not to translate plus signs +
+ back to blank spaces.
+ If you know how your applications behave,
+ then define PLUSBLANK to always translate plus signs +
+ to blank spaces, or define PLUSNOTBLANK to never translate.
+ Otherwise, if you define neither,
+ mimeTeX applies some common-sense rules to decide whether or
+ not to translate. These usually work, but can't be guaranteed.
+ If your query string contains actual blank spaces or
+ blanks encoded as %20, then plus signs +
+ aren't translated. Otherwise, if your query string
+ contains %2B, then plus signs + are
+ translated. If neither %20 nor %2B, or both
+ %20 and %2B, occur in your query string,
+ then the situation is ambiguous. In this case, if mimeTeX
+ finds two or more plus signs ++ with no intervening
+ space, then they're translated; otherwise they're not.
+ -DREFERER=\"domain\" -or-
-DREFERER=\"domain1,domain2,etc\"
Blocks mimeTeX requests from unauthorized domains that
are using your mimetex.cgi (hence your server's resources)
@@ -1266,25 +1705,25 @@ Ascii dump of bitmap image...
could conceivably flood your file system by submitting
zillions of \counter{filename} commands
to mimeTeX, each with a different filename.
- -DSQUASHMARGIN=n or
- -DNOSQUASH
+ -DSMASHMARGIN=n -or-
+ -DNOSMASH
TeX typically renders an expression like
\frac12\int_{a+b+c}^{d+e+f}g(x)dx as
- dx) . MimeTeX tries to remove extra
whitespace, rendering the same expression as
- }dx) instead.
- Compile with -DNOSQUASH if you prefer the typical TeX
+ Compile with -DNOSMASH if you prefer the typical TeX
behavior as mimeTeX's default. Or, to adjust the minimum
- number of pixels between squashed symbols (default is 3),
- compile with -DSQUASHMARGIN=n.
- See Squash for further discussion.
- -DWARNINGS=n or
+ number of pixels between smashed symbols (default is 3),
+ compile with -DSMASHMARGIN=n.
+ See Smash for further discussion.
+ -DWARNINGS=n -or-
-DNOWARNINGS
If an expression submitted to mimeTeX contains an
unrecognzied escape sequence, e.g., "y=x+\abc+1", then
@@ -1298,11 +1737,12 @@ Ascii dump of bitmap image...
-DWHITE
MimeTeX usually renders black symbols on a white
background. This option renders white symbols on
- a black background instead.
+ a transparent black background instead (or on an opaque
+ black background when combined with -DOPAQUE ).
-
+
MimeTeX usually runs from a browser, obtaining its input expression
from a query_string. But you can also run mimeTeX from your Unix
@@ -1314,7 +1754,9 @@ Ascii dump of bitmap image...
possibly useful functionality from the command line. In particular,
you can store a gif (or xbitmap) image of any expression to a file.
No syntax checking is applied to command-line arguments, so enter
- them carefully.
+ them carefully. (Likewise, plus signs + are never
+ translated to blank spaces, nor is any other %xx url decoding
+ performed on command-line arguments.)
The complete command-line syntax for mimeTeX is
@@ -1322,6 +1764,10 @@ Ascii dump of bitmap image...
[ -e export_file ] or write gif image to export_file
[ expression expression, e.g., "x^2+y^2",
| -f input_file ] or read expression from input_file
+ [ -g1 -d ] dump .pbm-formatted image on stdout
+ [ -g1 -e export_file ] or write .pbm image to export_file
+ [ -g2 -d ] dump anti-aliased .pgm image on stdout
+ [ -g2 -e export_file ] or write .pgm image to export_file
[ -m msglevel ] verbosity of debugging output
[ -o ] render image with opaque background
[ -s fontsize ] default fontsize, 0-5
@@ -1331,24 +1777,42 @@ Ascii dump of bitmap image...
./mimetex -d "x^2+y^2" > expression.gif
creates expression.gif containing an image of x^2+y^2
- -e Like -d but writes the actual gif (or xbitmap) directly
- to export_file, e.g.,
+ -e export_file Like -d but writes the actual gif
+ (or xbitmap) directly to export_file, e.g.,
./mimetex -e expression.gif "x^2+y^2"
- also creates expression.gif containing an image of x^2+y^2
+ creates file expression.gif containing an image of x^2+y^2
expression Place LaTeX expression directly on command
line, with no -switch preceding it, as in the example
- immediately above, or...
+ immediately above, or.....
- -f Read expression from input_file (and automatically
- assume -d switch). The input_file may contain the
- expression on one line or spread out over many lines.
- MimeTeX will concatanate all lines from input_file
- to construct one long expression. Blanks, tabs, and
- newlines are just ignored.
+ -f input_file .....read expression from input_file
+ (and automatically assume -d switch). The input_file
+ may contain the expression on one line or spread out
+ over many lines. MimeTeX will concatanate all lines
+ from input_file to construct one long expression.
+ Blanks, tabs, and newlines are just ignored.
+
+ -g1 -d dumps a .pbm-formatted portable bitmap image to stdout.
+ Note that this is the bitmap image _before_ anti-aliasing.
+
+ -g1 -e export_file Like -g1 -d but writes the .pbm-formatted
+ portable bitmap directly to export_file, e.g.,
+ ./mimetex -g1 -e expression.pbm "x^2+y^2"
+ creates file expression.pbm containing a bitmap image
+ of x^2+y^2 before anti-aliasing.
+
+ -g2 -d dumps a .pgm-formatted portable graphic image to stdout.
+ Note that this is the bytemap image _after_ anti-aliasing.
+
+ -g2 -e export_file Like -g2 -d but writes the .pgm-formatted
+ portable graphic image directly to export_file, e.g.,
+ ./mimetex -g3 -e expression.pgm "x^2+y^2"
+ creates file expression.pgm containing a bytemap image
+ of x^2+y^2 after anti-aliasing.
- -m 0-99, controls verbosity level for debugging output
- (usually used only while testing code).
+ -m msglevel 0-99, controls verbosity/message level for
+ debugging output (usually used only while testing code).
-o Rather than the default transparent gif background,
the rendered image will contain black symbols on an
@@ -1357,11 +1821,13 @@ Ascii dump of bitmap image...
display utility,
./mimetex -o -d "x^2+y^2" | display &
opens a small window containing the rendered expression.
+ (Note: if you already compiled mimeTeX with -DOPAQUE
+ then -o renders images on a transparent background.)
- -s 0-5, font size. As usual, the font size can also
- be specified within the expression by a directive,
- e.g., \large f(x)=x^2 displays f(x)=x^2 at font size 3,
- overriding -s. Default font size is 2.
+ -s fontsize 0-7, font size. Font size can also be specified
+ within the expression by a directive, e.g., \Large f(x)=x^2
+ displays f(x)=x^2 at font size 4, overriding -s.
+ Default font size is 3.
@@ -1372,10 +1838,12 @@ SECTION III. SYNTAX REFERENCE
Since mimeTeX's syntax is as TeX-like as possible, we'll mostly discuss
- the occasional exceptions (which exist only to simplify my programming
- task, not to impose any syntactic aesthetics of mine on you). This
- section contains short paragraphs that each discuss some aspect of
- mimeTeX where your LaTeX experience might not be precisely relevant.
+ the occasional differences.
+
+ This section contains short paragraphs that each discuss some aspect
+ of mimeTeX where your LaTeX experience might not be precisely
+ duplicated.
Anything not discussed here that still doesn't behave like you expect
is probably just not implemented. That includes (La)TeX packages
@@ -1442,17 +1910,46 @@ SECTION III. SYNTAX REFERENCE
As usual, you must explicitly write one of the recognized math
spaces to put extra visible space in your rendered expressions.
- MimeTeX recognizes math spaces \, \: \; as well as
- \/ and \quad and \qquad . You may also
- write \hspace{10} to insert a 10-pixel (or any other number)
- space, scaled by any preceding \unitlength,
- as illustrated just above. There are no negative spaces.
+ MimeTeX recognizes math spaces \/ \, \: \;
+ as well as \quad and \qquad ,
+ and also a backslashed blank
+ 
+ (i.e., a \ followed by a blank).
+ For example,
+ (a\/b\,c\:d\;e\ f\quad g\qquad h)
+ renders
+ ) .
+ In mimeTeX, you may also write \hspace{10}
+ to insert a 10-pixel (or any other number) space, scaled by any
+ preceding \unitlength, as illustrated
+ just above.
+
+ For negative spaces, \! produces a small (two
+ pixel) negative space, e.g., a=b renders
+ 
+ whereas a\!=b renders
+ 
+ and a\!\!=b renders
+  .
+ For large negative space, \hspace{-10} permits
+ a negative argument. But it stops at the first pixel to its left
+ rather than "erasing" pixels. If you don't want to stop, use
+ \hspace*{-10} instead. For example,
+ ABC\hspace*{-20}-DEF renders
+  , erasing all of the C
+ and the right half of the B.
+
MimeTeX also supports \hfill{textwidth}, where
textwidth is roughly equivalent to LaTeX's
@@ -1461,18 +1958,18 @@ SECTION III. SYNTAX REFERENCE
expression will span. However, if \hfill{ } appears
within a { }-enclosed subexpression, then it applies
only to that subexpression. For example,
- {abc \hfill{50} def} \hfill{100} ghi
+ {abc \hfill{75} def} \hfill{150} ghi
produces
- The first/inner \hfill{50} inserts exactly enough whitespace so
- that subexpression "abc def" spans 50 pixels.
- Then the second/outer \hfill{100} inserts exactly enough
- whitespace so that the entire expression spans 100 pixels.
+ The first/inner \hfill{75} inserts exactly enough whitespace so
+ that subexpression "abc def" spans 75 pixels.
+ Then the second/outer \hfill{150} inserts exactly enough
+ whitespace so that the entire expression spans 150 pixels.
Without explicit { }-nesting, mimeTeX evaluates expressions
- left-to-right (sinistrally), e.g., ...\hfill{100}...\hfill{50}...
- is exactly equivalent to ...\hfill{100}{...\hfill{50}...}.
+ left-to-right (sinistrally), e.g., ...\hfill{150}...\hfill{75}...
+ is exactly equivalent to ...\hfill{150}{...\hfill{75}...}.
Notice that, this time, the second/right textwidth
argument is necessarily smaller than the first/left.
@@ -1488,7 +1985,7 @@ SECTION III. SYNTAX REFERENCE
y=a+b+c+d\\\hspace{50}+e+f+g+h
to produce
However, mimeTeX can't correctly handle automatically-sized delimiters
@@ -1496,12 +1993,13 @@ SECTION III. SYNTAX REFERENCE
y=\left\{a+b+c+d\\\hspace{50}+e+f+g+h\right\}
produces
+ src="../cgi-bin/mimetex.cgi?\large y=\{a+b+c+d\\
+ \hspace{50}+e+f+g+h\}" alt="" border=0 align=middle>
whereas you probably wanted
+ src="../cgi-bin/mimetex.cgi?\large y=\big{a+b+c+d\\
+ \hspace{50}+e+f+g+h\big}" alt="" border=0 align=middle>
+
which I produced using \big{...\\...\big} instead
of \left\{...\\...\right\}. Expressions of the
form \left...\right \\ \left...\right should all be
@@ -1559,14 +2057,22 @@ and some other characters..
500-or-so lines of mimetex.h. And several additional
symbols like \ldots and \AA and \hbar are
defined by the mimeTeX preprocessor, function mimeprep( )
- in mimetex.c Generally speaking, I've tried
- to encode the cmmi10, cmsy10, cmr10, cmex10, rsfs10 and bbold10
- families with "names", e.g., \alpha \beta \forall \sqcup, etc,
- identical to your LaTeX expectations. For example, the
- calligraphic symbols in cmsy10 are accessed by writing
- \mathcal{A} \mathcal{B} \mathcal{XYZ}. Similarly, write
- \mathscr{A} for the rsfs10 fonts, and write \mathbb{R}
- for bbold10.
+ in mimetex.c Generally speaking, I've tried to
+ encode the cmr10, cmmi10, cmmib10, cmsy10, cmex10, bbold10, rsfs10,
+ stmary10 and wncyr10 families with "names", e.g., \alpha \beta
+ \forall \sqcup, etc, identical to your LaTeX expectations.
+ For example, the calligraphic symbols in cmsy10 are accessed by
+ writing \mathcal{A} \mathcal{B} \mathcal{XYZ}. Similarly,
+ write \mathbf{A} for the cmmib fonts, write \mathscr{A}
+ for rsfs10, write \mathbb{R} for bbold10, and write
+ {\cyr Khrushchev} or \cyr{Khrushchev} to see
+  .
+ Most LaTeX distributions supply stmaryrd.dvi and stmaryrd.sty
+ that both document the names of the stmary10 symbols.
+ Similarly, amsfndoc.dvi documents the names of the wncyr10
+ cyrillic symbols and ligatures.
- \sum_{i=1}^ni=\frac{n(n+1)}2
+ \normalsize \sum_{i=1}^ni=\frac{n(n+1)}2
produces
}2) , whereas
- \displaystyle \sum_{i=1}^ni=\frac{n(n+1)}2 produces
+ \displaystyle \normalsize \sum_{i=1}^ni=\frac{n(n+1)}2
+ produces
}2) ,
and
@@ -1735,7 +2280,7 @@ and some other characters..
As usual, \nolimits turns displaystyle off (or textstyle on)
for the operator immediately preceding it. For example,
- \large\sum\nolimits_{i=1}^ni=\frac{n(n+1)}2
+ \large \sum\nolimits_{i=1}^ni=\frac{n(n+1)}2
produces
and likewise, \limits turns displaystyle on for the operator
immediately preceding it. For example,
- \sum\limits_{i=1}^ni=\frac{n(n+1)}2 produces
+ \normalsize \sum\limits_{i=1}^ni=\frac{n(n+1)}2
+ produces
}2)
By the way, \limits affects _any_ character
or subexpression immediately preceding it. For example,
A^i_j produces
 as usual, whereas
A\limits^i_j produces
![]() ..
anything at all in italic (font family cmmi10).
All four forms respect spaces between words, except that the
first/required space after {\rm etc} and
- {\it etc} is still ignored. For example,
+ {\it etc} is still ignored. For example,
anything at all just produces
 whereas
\text{anything at all} produces
 and
\textit{anything at all} produces
 instead.
+ src="../cgi-bin/mimetex.cgi?\normalsize\textit{anything at all}"
+ alt="" border=0 align=middle> instead.
+
+ You don't usually surround mimeTeX expressions with $'s,
+ but that works in the usual way for \text{ } and
+ \mbox{ }, rendering the $...$-enclosed
+ subexpression in mathmode. For example,
+ n=\left\{m/2\text{ if $m$ even}
+ \\(m+1)/2\text{ if $m$ odd}\right.
+ produces
+ /2\text{ if $m$ odd}\right.)
@@ -1821,7 +2382,10 @@ and some other characters..
- LaTeX's \left( and \right) may be written exactly
+ LaTeX's \left( ... \right) and the other 21
+ standard LaTeX delimiters are also recognized by mimeTeX.
+ And mimeTeX also recognizes an etex-like \middle.
+
+ Several of the most common automatically sized delimiters
+ are illustrated below...
- LaTeX or
mimeTeX |
- or mimeTeX
abbreviation |
+
+ Delimiter |
+
example... |
...renders |
| \left( ... \right) |
- \( ... \) |
+
\left( \frac1{1-x^2} \right)^2 |
^2) ..
|
| \left[ ... \right] |
- \[ ... \] |
- \left[ 1+\frac xn \right]^n |
+
+ \left[ \frac1{\sqrt2}x - y \right]^n |
 |
| \left\{ ... \right\} |
- \{ ... \} |
+
\left\{ 1^2,2^2,3^2,\ldots \right\} |
  |
| \left| ... \right| |
- \| ... \| |
- \det \left| \begin{array}{cc} 1&2\\
- 3&4 \end{array} \right| |
+
+ \left| \begin{matrix} a_1 & a_2 \\
+ a_3 & a_4 \end{matrix} \right| |
 |
| \left\| ... \right\| |
- \= ... \= |
+
\left\|x^2-y^2\right\| |
 |
- | \left\{ ... \right. |
- \{ ... \. |
- y=\left\{ \text{this\atop that} \right. |
+ \left\{ ...
+ \right. |
+
+ y=\left\{ \text{this\\that}
+ \right. |
 |
- | \left. ... \right\} |
- \. ... \} |
- \left. \text{this\atop that} \right\}=y |
+ \left.
+ ... \right\} |
+
+ \left.
+ \text{this\\that} \right\}=y |
 |
Notes...
- - The other LaTeX delimiters, i.e., floor's, ceil's,
- arrows, etc, can't yet be sized to fit.
+
- Size declarations inside any of the
above delimiter pairs affect only the enclosed subexpression,
e.g., \Large w=\left(\small x+y\right)+z produces
+z)
- - An abbreviated left delimiter must be paired with the same
+
- An expression may contain as many etex-like \middle's as
+ you like, and in mimeTeX the surrounding \left...\right
+ isn't required. When omitted, the scope of \middle is
+ either the entire expression or the { }-enclosed
+ subexpression in which the \middle's occur. For example,
+ \frac{a+1}b \middle/ \middle(\frac{c+1}d \middle/ \frac{e+1}f\middle)
+ renders
+
) .
+ - In the last two examples, note that mimeTeX recognizes the
+ \\ in \text{this\\that}
+ as a linebreak. For example, x=1\\y=2\\z=3 renders
+
+
+
+
+
+
+
Besides the \left...\right delimiters discussed above,
@@ -1976,22 +2564,22 @@ and some other characters..
and its matching \right. delimiter.
The \right delimiter needn't necessarily be
the \right. illustrated, e.g.,
- \left\int_a^b x^2dx =\frac{x^3}3\right|\nolimits_a^b
+ \left\int_a^b x^2dx =\frac{x^3}3\right|_a^b
produces
 . Except for Opening (TeX class 4) and
+ \left\int_a^bx^2dx=\frac{x^3}3\right|_a^b" border=0 alt=""
+ align=middle>.
You can also write \left\sum, \left\prod,
- \left\cup, etc, for many of the symbols in CMEX10.
+ \left\cup, etc, for many of the symbols in CMEX10 and STMARY10.
And any symbol that works with \left will also work
- with \right . But mimeTeX abbreviations like
+ with \right .
Unescaped ( )'s and [ ]'s and | |'s
and < >'s don't need to be balanced since mimeTeX just
@@ -2017,11 +2605,24 @@ Raise and rotate, Compose, Abb
Accents...
- \vec{ } \hat{ } \bar{ } \tilde{ } \dot{ }
- and \ddot{ } are the only accents currently supported,
- and they're all "wide". You can write \widehat{ } if you
- like, but there's absolutely no difference either way.
- \bar{ } and \overline{ } are identical.
+ \vec{ } \hat{ } \bar{ } \tilde{ } \dot{ }
+ \ddot{ } and \acute{ } \grave{ }
+ \breve{ } \check{ } are the only accents currently
+ supported. The first four are all "wide". For example, you can write
+ \widehat{ } if you like, but there's absolutely no
+ difference either way (and \bar{ } and
+ \overline{ } are identical). The last four accents
+ only take a single character argument.
+
+ Other accent-like directives available in mimeTeX are
+ \underline{ } \cancel{ } \sout{ },
+ as well as
+ \overset{ }{ } \underset{ }{ }
+ and the more ususal
+ \overbrace{ }^{ } \underbrace{ }_{ }.
+ And \not also works on the single character immediately
+ following it. Some of these directives are discussed in more detail
+ below.
@@ -2032,7 +2633,7 @@ Raise and rotate, Compose, Abb
also behave as expected, e.g.,
\lim_{n\to\infty}S_n=S produces
@@ -2057,7 +2658,7 @@ Raise and rotate, Compose, Abb
any white space after the arrow, e.g., f:x\longrightarrow~[0,1]
produces
 . Without any intervening white space,
mimeTeX would have "eaten" the [0,1].
@@ -2099,17 +2700,28 @@ Raise and rotate, Compose, Abb
displays super/subscripts in the usual way.
+\rotatebox{ }{ } and \reflectbox[ ]{ }
+...
The \raisebox{height}{expression}
and \rotatebox{angle}{expression}
- commands help you fine-tune and manipulate mimeTeX renderings.
- The height argument is number of pixels, scaled by
- \unitlength, and can be positive
- or negative. The angle argument is number of degrees,
- and can also be positive (for clockwise) or negative, but must be a
- multiple of 90. Finally, the expression can be any
- valid LaTeX/mimeTeX expression. For example, mimeTeX's preprocessor
+ and \reflectbox[axis]{expression}
+ commands help you fine-tune and manipulate mimeTeX renderings:
+
+ - \raisebox's height argument is number
+ of pixels, scaled by \unitlength,
+ and can be positive or negative.
+ - \rotatebox's angle argument is number
+ of degrees, and can also be positive (for clockwise) or
+ negative, but must be a multiple of 90.
+ - \reflectbox's optional axis argument
+ defaults to 1 if not given, which reflects horizontally
+ (the usual LaTeX behavior), or reflects vertically if
+ specified as 2.
+ - For all three commands, the expression
+ can be any valid LaTeX/mimeTeX expression.
+
+ For example, mimeTeX's preprocessor
defines the LaTeX ?` symbol, an upside-down question
mark, like
abc\raisebox{-2}{\rotatebox{180}?}def produces
@@ -2117,6 +2729,14 @@ Raise and rotate, Compose, Abb
src="../cgi-bin/mimetex.cgi?
\large\rm abc\raiseb{-2}{\rotateb{180}{\LARGE?}}def"
alt="" border=0 align=middle>
+ Using \reflectbox[2]{ } instead of
+ \rotatebox{180}{ } would result in the slightly
+ different
+ abc\raisebox{-2}{\reflectbox[2]?}def produces
+ 
@@ -2133,12 +2753,40 @@ Raise and rotate, Compose, Abb
alt="" border=0 align=middle>
Separately or in some judicious combination, \compose and
- \raisebox and \rotatebox should help you construct
- special symbols not "natively" available with mimeTeX's limited
- set of built-in font families. This can be especially useful
- in conjunction with the -DNEWCOMMANDS compile-time
+ \raisebox and \rotatebox and \reflectbox
+ should help you construct special symbols not "natively" available
+ with mimeTeX's limited set of built-in font families.
+ This can be especially useful in conjunction with the
+ -DNEWCOMMANDS compile-time
option discussed above.
+
+
+
+ \rule{width}{height} behaves in the usual way,
+ rendering a black rectangle width pixels wide and
+ height pixels high, with its base on the established
+ baseline. For example,
+ \frac12xyz\rule{10}{20}ghi produces
+ 
+
+ The mimeTeX version of \rule has an optional
+ [lift] argument, so that its full form is
+ \rule[lift]{width}{height}.
+ lift moves the rule's baseline by the specified
+ number of pixels, up if positive or down if negative.
+ For example,
+ \frac12xyz\rule[5]{10}{20}ghi produces
+  and
+ \frac12xyz\rule[-15]{10}{20}ghi produces
+ 
+
@@ -2172,101 +2820,101 @@ Raise and rotate, Compose, Abb
\Large\color{blue} e^x=\sum_{n=0}^\infty\frac{x^n}{n!}"
alt="" border=0 align=middle>
-
+
TeX represents characters by boxes, with no idea how ink will be
distributed inside. So an expression like
\frac12\int_{a+b+c}^{d+e+f}g(x)dx is typically rendered as
- dx}) dx}) .
But mimeTeX knows the character shapes of its fonts, and therefore tries
to remove extra whitespace, rendering the same expression as
- }dx) }dx) instead.
- Precede any expression with the mimeTeX directive \nosquash
- to render it without "squashing". Or compile mimetex.c with the
- -DNOSQUASH option if you prefer
+ Precede any expression with the mimeTeX directive \nosmash
+ to render it without "smashing". Or compile mimetex.c with the
+ -DNOSMASH option if you prefer
the typical TeX behavior as mimeTeX's default. In this case,
- precede any expression with \squash to render it "squashed".
+ precede any expression with \smash to render it "smashed".
And note that explicit space like \hspace{10}
- or \; , etc, is never squashed.
+ or \; , etc, is never smashed.
- The scope of \squash and \nosquash is the
+ The scope of \smash and \nosmash is the
{ }-enclosed subexpression in which the directive occurs.
For example, if you want the g(x) part of the
- preceding example squashed, but not the 1/2 part,
+ preceding example smashed, but not the 1/2 part,
then the expression
- \nosquash\frac12{\squash\int_{a+b+c}^{d+e+f}g(x)dx}
+ \nosmash\frac12{\smash\int_{a+b+c}^{d+e+f}g(x)dx}
renders as
- dx}}) dx}}) .
- For finer-grained control, note that \squash is shorthand
- for the default \squashmargin{+3} (and \nosquash is
- shorthand for \squashmargin{0}). \squashmargin's value
- is the minimum number of pixels between squashed symbols. The leading
- + is optional. If present, the font size (\tiny=0,...,\LARGE=5)
+ For finer-grained control, note that \smash is shorthand
+ for the default \smashmargin{+3} (and \nosmash is
+ shorthand for \smashmargin{0}). \smashmargin's value
+ is the minimum number of pixels between smashed symbols. The leading
+ + is optional. If present, the font size (\tiny=0,...,\Huge=7)
is added to the specified minimum. Compile mimetex.c with the
- -DSQUASHMARGIN=n option to change
+ -DSMASHMARGIN=n option to change
the default from 3 to n. Compare the preceding
- example with the over-squashed \squashmargin{1}
- }dx) \smashmargin{1}
+ }dx) instead.
- Squashing is in "alpha testing" and some expressions still don't look
- quite right when squashed, e.g., 1^2,2^2,3^2,\ldots renders as
- ![]() Smashing is in "beta testing" and some expressions still don't look
+ quite right when smashed, e.g., 1^2,2^2,3^2,\ldots renders as
+  . Just compile with -DNOSQUASH
+ alt="" border=0 align=middle>. Just compile with -DNOSMASH
if you come across numerous annoying situations.
-
+
The usual LaTeX \not "slashes" the single symbol
following it, e.g., i\not\partial\equiv i\not\nabla
produces
 .
- For arbitrary expressions, mimeTeX provides \Not
+ For arbitrary expressions, mimeTeX provides \cancel
which draws a line from the upper-right to lower-left corner of its
- argument, e.g., a\Not{x^2}=bx^{\not3} produces
+ argument, e.g., a\cancel{x^2}=bx^{\not3} produces
 .
Finally, similar to the ulem.sty package, \sout
draws a horizontal strikeout line through its argument,
e.g., \sout{abcdefg} produces
 . MimeTeX's \sout also
takes an optional argument that adjusts the vertical position of its
strikeout line by the specified number of pixels, e.g.,
\sout[+2]{abcdefg} produces
 and
\sout[-2]{abcdefg} produces
 .
@@ -2306,6 +2954,9 @@ Raise and rotate, Compose, Abb
| \begin{align} |
a&=b \\ c&=d \\ etc |
\end{align} |
+ | \begin{cases} |
+ a&b \\ c&d \\ etc |
+ \end{cases} |
| \begin{gather} |
a \\ b \\ etc |
\end{gather} |
@@ -2348,8 +2999,8 @@ Raise and rotate, Compose, Abb
The default font size is unchanged by \array{ }, but you
can explicitly control it in the usual way, e.g.,
- {\large\begin{matrix}...\end{matrix}} renders the entire array
- in font size 3. In addition, any &...& cell may contain font
+ {\Large\begin{matrix}...\end{matrix}} renders the entire array
+ in font size 4. In addition, any &...& cell may contain font
size declarations which are always local to that cell,
e.g., &\fs{-1}...& renders that one cell one font size smaller
than current.
@@ -2536,7 +3187,7 @@ Raise and rotate, Compose, Abb
(50,35){\circle(50,45;34)} %%lower lip%% }
{
+ src=)
Have a nice day!
@@ -2564,19 +3215,21 @@ Raise and rotate, Compose, Abb
in LaTeX, and won't be discussed further. Short discussions
of some other commands follow.
-
+
\stackrel{ }{ } behaves as usual in LaTeX,
rendering its first argument one font size smaller and centered above
its second. And the amsmath-style \overset{ }{ } is
identical. For example,
- "\vec x\stackrel{\rm def}=(x_1\ldots x_n)"
+ "\vec x\overset{\rm def}=(x_1\ldots x_n)"
produces
)
"Conversely" to \stackrel{ }{ }, mimeTeX provides
@@ -2586,10 +3239,10 @@ Raise and rotate, Compose, Abb
first argument one font size smaller and centered below its second.
For example, the \log function name doesn't treat
limits like \lim_, but you can write, for example,
- "\relstack{\log}{\rm base 2}32=5" to render
+ "\underset{\rm base 2}\log32=5" to render
MimeTeX's \limits provides an easier but non-standard
@@ -2612,7 +3265,7 @@ Raise and rotate, Compose, Abb
the usual \fbox{expression} command, e.g.,
"\fbox{x=\frac12}" produces
You can also write \fbox[width]{expression}
@@ -2620,6 +3273,58 @@ Raise and rotate, Compose, Abb
\fbox[width][height]{expression}
to explicitly set both width and height.
+
+
+ \today renders
+ 
+ in the usual LaTeX text mode way.
+ That's \today's default format#1. MimeTeX has
+ an optional format argument so that, for example,
+ \blue\today[2] renders
+  ,
+ showing both date and time. And
+ \red\today[3] renders
+  ,
+ showing time only.
+
+ To accommodate time zones, you may also write, for example,
+ \small\blue\today[2,+3], which renders
+  ,
+ adding three hours to format#2.
+ The arguments may be in either order. The time zone increment
+ must always be preceded by either + or -,
+ and must be in the range -23 to +23.
+
+ \calendar renders a calendar for
+ the current month, as illustrated by the left-hand image below.
+ For a different month, the optional argument
+ \small\blue\calendar[2001,9] renders the right-hand
+ image, for the requested year and month. Years must be
+ 1973...2099 and months must be 1...12.
+
+ 
+ 
+
+ The default calendar emphasizes the current day of the current month,
+ while any other month emphasizes no day. Day emphasis is controlled
+ by an optional third argument. \calendar[0,0,1]
+ emphasizes the first day of the current month, and
+ \calendar[2001,9,11] emphasizes the eleventh
+ day of that month. \calendar[0,0,99]
+ renders the current month with no day emphasized.
+
@@ -2686,7 +3391,7 @@ Raise and rotate, Compose, Abb
Somewhat more detailed log information can be accumulated in
the optional logfile. If you provide that
filename, mimeTeX writes a line to it of the form
- 2004-09-20:12:59:33pm <tag>=99 192.168.1.1 http_referer
+ 2008-09-07:12:59:33pm <tag>=99 192.168.1.1 http_referer
containing a timestamp, the counter tag and its current value,
and the user's IP address and http_referer page if they're
available.
@@ -2739,13 +3444,14 @@ SECTION IV. APPENDICES
(supplied with your mimeTeX distribution).
The final output from each such sequence of three runs
- (metafont > gftype -i > gfuntype) gives mimeTeX the information
- it needs to render one particular font family at one particular
- size. The file texfonts.h supplied with your mimeTeX
- distribution collects the output from 36 such (sequences of)
- runs, representing six font families at six sizes each.
+ (metafont > gftype -i > gfuntype) gives mimeTeX the
+ bitmap information it needs to render one particular font
+ family at one particular size. The file texfonts.h
+ supplied with your mimeTeX distribution collects the output
+ from 72 such (sequences of) runs, representing nine font
+ families at eight sizes each.
- This collection of information in texfonts.h is
+ This collection of information in texfonts.h is
"wired" into mimeTeX through tables maintained in mimetex.h.
To change mimeTeX's fonts, you'll have to first modify (or totally
replace) texfonts.h using your own gfuntype output, and then
@@ -2762,7 +3468,8 @@ SECTION IV. APPENDICES
Running metafont to generate a .gf file from .mf
source will usually be your very first step. A typical such run
might be
- mf '\mode=onetz; mag=magstep(.5); input cmmi10'
+
+ mf '\mode=preview; mag=magstep(-16.393225); input cmmi10'
which in this case generates output file
cmmi10.131gf (which is mimeTeX's font size 3 for the
cmmi family).
@@ -2788,39 +3495,54 @@ SECTION IV. APPENDICES
Then pull all the output files into one big texfonts.h file
(or write a small texfonts.h which just #include's them all).
- For your information, the 36 sequences of runs represented
+ For your information, the 72 sequences of runs represented
in the texfonts.h file supplied with your mimeTeX distribution
- correspond to the following six inital metafont runs for cmr10
- size=0 (.83gf) mf '\mode=eighthre; input cmr10'
+ correspond to the following eight inital metafont runs for cmr10
+
+ size=0 (.83gf) mf '\mode=eighthre; input cmr10'
+ 1 (.100gf) mf '\mode=preview; mag=magstep(-17.874274); input cmr10'
+ 2 (.118gf) mf '\mode=preview; mag=magstep(-16.966458); input cmr10'
+ 3 (.131gf) mf '\mode=preview; mag=magstep(-16.393225); input cmr10'
+ 4 (.160gf) mf '\mode=preview; mag=magstep(-15.296391); input cmr10'
+ 5 (.180gf) mf '\mode=preview; mag=magstep(-14.650373); input cmr10'
+ 6 (.210gf) mf '\mode=preview; mag=magstep(-13.804885); input cmr10'
+ 7 (.250gf) mf '\mode=preview; mag=magstep(-12.848589); input cmr10'
- Then ditto for the five other font families cmmi10, cmsy10, cmex10,
- rsfs10, bbold10. All the subsequent gftype and gfuntype runs just
- follow the usual format described above.
+ Then ditto for the eight other font families cmmi10, cmmib10, cmsy10,
+ cmex10, bbold10, rsfs10, stmary10 and wncyr10. And to generate other
+ .dpigf font sizes, calculate magsteps
+ }{\log1.2}) . All the subsequent gftype and
+ gfuntype runs just follow the standard format described above.
To incorporate all this font information you just generated into
mimeTeX, edit your mimetex.h file and find the table that looks
- something like static fontfamily aafonttable[] =
- { /* -------------------------------------------------------------
- family size=0, 1, 2, 3, 4, 5
- ------------------------------------------------------------- */
- { CMR10, { cmr83, cmr100, cmr118, cmr131, cmr160, cmr180 } },
- { CMMI10, { cmmi83, cmmi100, cmmi118, cmmi131, cmmi160, cmmi180 } },
- { CMSY10, { cmsy83, cmsy100, cmsy118, cmsy131, cmsy160, cmsy180 } },
- { CMEX10, { cmex83, cmex100, cmex118, cmex131, cmex160, cmex180 } },
- { RSFS10, { rsfs83, rsfs100, rsfs118, rsfs131, rsfs160, rsfs180 } },
- {BBOLD10, {bbold83,bbold100,bbold118,bbold131,bbold160,bbold180 } },
- { -999, { NULL, NULL, NULL, NULL, NULL, NULL } }
- } ; /* --- end-of-fonttable[] --- */
- Note the 36 names cmr83...bbold180 in the table. These must
+ something like static fontfamily aafonttable[] = {
+ /* ----------------------------------------------------------------------------------------
+ family size=0, 1, 2, 3, 4, 5, 6, 7
+ ----------------------------------------------------------------------------------------- */
+ { CMR10,{ cmr83, cmr100, cmr118, cmr131, cmr160, cmr180, cmr210, cmr250}},
+ { CMMI10,{ cmmi83, cmmi100, cmmi118, cmmi131, cmmi160, cmmi180, cmmi210, cmmi250}},
+ { CMMIB10,{ cmmib83, cmmib100, cmmib118, cmmib131, cmmib160, cmmib180, cmmib210, cmmib250}},
+ { CMSY10,{ cmsy83, cmsy100, cmsy118, cmsy131, cmsy160, cmsy180, cmsy210, cmsy250}},
+ { CMEX10,{ cmex83, cmex100, cmex118, cmex131, cmex160, cmex180, cmex210, cmex250}},
+ { RSFS10,{ rsfs83, rsfs100, rsfs118, rsfs131, rsfs160, rsfs180, rsfs210, rsfs250}},
+ { BBOLD10,{ bbold83, bbold100, bbold118, bbold131, bbold160, bbold180, bbold210, bbold250}},
+ {STMARY10,{stmary83,stmary100,stmary118,stmary131,stmary160,stmary180,stmary210,stmary250}},
+ { CYR10,{ wncyr83, wncyr100, wncyr118, wncyr131, wncyr160, wncyr180, wncyr210, wncyr250}},
+ { -999,{ NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL}}
+} ; /* --- end-of-fonttable[] --- */
+ Note the 72 names cmr83...wncyr250 in the table. These must
correspond to (or must be changed to) the names following the -n
- switch you specified for your gfuntype runs.
+ switch you specified for your gfuntype runs.
- If you want more than six font sizes, first build up texfonts.h
+ If you want more than eight font sizes, first build up texfonts.h
with all the necessary information. Then change LARGESTSIZE (and
probably NORMALSIZE) in mimetex.h, and finally edit the above aafonttable[]
by extending the columns in each row up to your largest size.
@@ -2831,6 +3553,39 @@ SECTION IV. APPENDICES
after reviewing mimetex.h). A new row would be required,
for example, to make another font available in mimeTeX.
+ One small problem with the above procedure is that the default
+ gftype program supplied with most TeX distributions
+ can't emit the long lines needed to display mimeTeX's larger font
+ sizes. You'll need to compile your own version from source.
+ The following instructions are for Unix/Linux:
+ First, download both
+ web-7.5.3.tar.gz and
+ web2c-7.5.3.tar.gz,
+ or more recent versions. Then untar them both,
+ cd web2c-7.5.3/ and run ./configure
+ and make in the usual way (make may fail before
+ completion if you don't have all needed fonts installed,
+ but it will create and compile gftype.c before failing). Now edit
+ texk/web2c/gftype.c and notice two lines very near the top
+ that #define maxrow (79) and similarly for maxcol.
+ Change both 79's to 1024, and then re-run make. The new
+ texk/web2c/gftype executable image can emit the long
+ lines needed for mimeTeX's larger font sizes.
+
+ Finally, the Unix/Linux bash shell script
+ texfonts.sh generates file texfonts.h
+ containing the information for all 72 mimeTeX fonts discussed above
+ (and, optionally, an extra 1200dpi cmr font used to test mimeTeX's
+ supersampling algorithm). You'll need to understand and edit this
+ script to use it meaningfully. But it helps automate mimeTeX's font
+ generation procedure in case you want to experiment with different
+ fonts. (Note that metafont emits a complaint while generating the
+ 83dpi rsfs font. Just press <CR> and it completes
+ successfully.)
+
@@ -2855,7 +3610,8 @@ function
Cut-and-paste the above sample code from this file to, say,
mimedemo.c (and fix the brackets around stdio.h). Then compile
- cc mimedemo.c mimetex.c -lm -o mimedemo
+
+ cc -DTEXFONTS mimedemo.c mimetex.c -lm -o mimedemo
and run it from your unix shell command line like
./mimedemo "x^2+y^2"
@@ -2910,8 +3666,8 @@ function
}
Cut-and-paste as before, compile like
- cc mimedemo.c mimetex.c gifsave.c
- -lm -o mimedemo
+
+ cc -DTEXFONTS mimedemo.c mimetex.c gifsave.c -lm -o mimedemo
and run it like the first example, but this time you may want to redirect
stdout
./mimedemo "x^2+y^2"
@@ -3194,7 +3950,7 @@ Footer across bottom of page
| |
