You can get a LaTeX style file, 'larch.sty', and a macro file defining a bunch of mathematical symbols, 'larchmath.tex', by anonymous ftp from the following URL. ftp://ftp.cs.iastate.edu/pub/larch/tex The documentation for 'larch.sty' says that it is to be used with LaTeX 2.09. However, it can be used with LaTeX2e. To do so, put the following lines at the start of your LaTeX input.

There’s no straightforward answer to this question. Many people swear by Plain TeX, and produce highly respectable documents using it (Knuth is an example of this, of course). But equally, many people are happy to let someone else take the design decisions for them, accepting a small loss of flexibility in exchange for a saving of brain power.

LaTeX is a program written in the programming language TeX. (In the same sense, any LaTeX document is also a program, which is designed to run ‘alongside’, or ‘inside’ LaTeX, whichever metaphor you prefer.) Both exist because writing your documents in ‘raw’ TeX would involve much reinventing of wheels for every document. They both serve as convenient aids to make document writing more pleasant: LaTeX is a far more extensive aid.

First you need to convert the NCGM file to PostScript with the following type of command: ctrans -d ps.color -simulatebg gmeta > gmeta.ps Convert this PostScript file to encapsulated PostScript using a filter of some kind: ps2epsi gmeta.ps gmeta.epsi (ps2epsi is a utility based on GhostScript which takes an input PostScript file and generates a new output file which conforms to Adobe's "Encapsulated Postscript Interchange" format, called EPSI.

A great many, including at least these: amslatex, amstex, autofont-mktexpk, autofont-mktextfm, chkdelim, chktex, detex, disdvi, doamslatex, doamstex, dolatex, doslitex, dotex, dvi2text, dvi2text, dvi2tty, dvialw-type1, dvialw, dvibit, dvibook, dvica2, dvican, dviconcat, dvicopy, dvidot, dvidsk.sh, dvihl8, dviimp, dviinfo, dvijep, dvijet.sh, dvikyo, dvilzr, dvipdf, dvips-type1, dvips, dviselect, dvitodvi, dvitype, etex, fig2ps2tex.

We recommend that you have at least TeX 3.14 and LaTeX 2.0.9. Also, we assume that you have dvips on your system to convert dvi files to postscript files.

You can get the MIT releases of the LSL checker using the world-wide web, starting at the following URL. http://www.sds.lcs.mit.edu/spd/larch/lsl.html You can also get the MIT release by anonymous ftp from the following URL. ftp://ftp.sds.lcs.mit.edu/pub/Larch/LSL/ Iowa State, the Larch/C++ group has made available later beta releases of the LSL checker that fix problems with its profligate use of space. You can get the sources for Unix and Windows 95 executables from the following URL.

You are looking in the wrong place. Since WinEdt is not a TeX system, it is not the cause for your problems. You should have a look in one of the below mentioned LaTeX FAQs or ask in a LaTeX related newsgroup. WinEdt Startup and Profiles3.1.1. Is there a Command Line Switch to start WinEdt with a document and with the caret on a specific line?3.1.2. How can I set up WinEdt to open only the file that I double click?3.1.3. What is it all about with %B and %b and how can I check their values?3.1.4.

The TeX program itself is a macro compiler. This engine is always required when processing any of the macro systems described below. TeX input consists of a stream of mixed commands and text. Commands can be defined for many purposes, not the least important of which is to permit input to be structured in a logical manner, allowing an author to concentrate on content rather than on typographic appearance. The most popular such macro set is LaTeX.

Usually this means that some particular style file is missing. Use the gripe command to complain about about it and it will be added in very short order, or, an alternative package may be suggested. In the meantime, you can see if you can find the required .sty style file for download (e.g. from TUG ) and save it in the same directory as your LaTeX document. If your $PAGER variable is set to "less" sometimes the man command will truncate a man page. This is a truly ancient bug.

We do offer Publishing Companion, which is software for converting Word to LaTeX. However, the output of a document written in LaTeX will always be better than one converted from Word. The features of Word are not sufficient to produce high-quality technical documents.

Latex is a milky white liquid composed of rubber particles dispersed in water. This material is whipped with air to form a foam, which is cured to make our mattresses.

The Macros feature allows you to create boilerplate text that you can paste into any message with the click of a mouse. The title should be short because it will show up in a pull-down menu. Make sure it is distinctive enough that you will remember which title belongs with which macro. In the Macro 1 field, enter the text you want to be able to paste. If your boards allow HTML, you can use HTML tags in the field.

First you need to get your graphic as an encapsulated PostScript file. You can do this using the direct PostScript driver or using ctrans to first convert your NCGM to PostScript and then using some kind of filter (like ps2epsi which is a utility based on GhostScript) to convert that to an encapsulated PostScript file. If you want to resize the figure, you can do so with one or both of the TeX commands: \epsfxsize=dimen \epsfbox{gmeta.epsi} epsfysize=dimen \epsfbox{gmeta.

You are almost always better off using the LaTeX version of things as they are far easier to work with. In addition, many journals have their own LaTeX style files that they distribute for use in publications and using LaTeX will prepare you well.

Without a doubt, using AucTeX in Emacs or XEmacs. Next in preference comes Lyx (see above). All other approaches will be tedious.

If you want it to be portable, probably not. So you can either convert it to encapsulated postscript (eps) using a graphics program like Gimp, or use a program called jpeg2ps, which puts an eps wrapper on the jpeg file. This means you can treat it like a postscript file (as long as you have at least postscript 2, which is pretty much everywhere these days). So this is essentially like putting it directly in.

There is a program called detex that can be used to strip away TeX and LaTeX commands, but it is not a great solution (it is designed to be a pre-processor for a spelling checker). Maybe the best solution is to generate a postscript file and then use ps2ascii to convert from postscript to ascii. From the man page: ps2ascii uses gs(1) to extract ASCII text from PostScript(tm) or Adobe Portable Document Format (PDF) files.

It can deal with any file type. It's up to the individual viewer to ensure they have the correct software to view the file though. We will be working on implementing viewers for the most common non-standard formats. Yes. Every item in the repository is assigned it's own permanent unique identifier. There are a number of different UID formats such as DOIs but we use CNRI's Handle system.

Answer. You will find out, that much LaTeX-knowledge can be reused. For example, you can start a section by typing \section[return] or you get α1 by typing $\alpha_1$. Note that there are even shorter ways provided, for example $a[tab]$ gives you an alpha as well, so you might want to migrate after a while. Styles like article, book or seminar, as known from LaTeX, are provided as well. Furthermore, many Emacs shortcuts like C-x C-s for saving a file, or C-_ for undo will work.

Answer. This question is due to a fundamental misunderstanding about TeXmacs. Indeed, TeXmacs is not based on TeX/LaTeX, although it does support (not yet perfect) conversion to and from LaTeX. Furthermore, in theory at least, there is actually no need anymore to look at something like the TeX source, since TeXmacs is guaranteed to be fully WYSIWYG. Conversion to LaTeX may only be useful, when transmitting an accepted paper to the publisher of a journal. Answer.

Here are two LaTeX macros for the word "C++". They prevent line breaks between the "C" and "++", and the first packs the two "+"s close to each other but the second does not. Try them both and see which one you like best. newcommand{\CC}{C\nolinebreak\hspace{-.05em}\raisebox{.4ex}{\tiny\bf +}\nolinebreak\hspace{-.10em}\raisebox{.4ex}{\tiny\bf +}} Here are two more LaTeX macros for the word "C++".

The main difference between LSL and a Larch BISL is that in LSL one specifies mathematical theories of the operators that are used in the pre- and postcondition specifications of a Larch BISL. Thus LSL is used to specify mathematical models and auxiliary functions, and the a Larch BISL is used to specify program modules that are to be implemented in some particular programming language.

The Larch Shared Language (LSL) (see [Guttag-Horning93], Chapter 4, and [Guttag-Horning-Modet90]) is a language for specifying mathematical theories. LSL is a kind of equational algebraic specification language [Guttag75] [Guttag-Horning78] [Goguen-Thatcher-Wagner78] [Ehrig-Mahr85] [Futatsugi-etal85] [Mosses96] [Loeckx-Ehrich-Wolf96]. That is, specifications in LSL mainly consist of first-order equations between terms.

Besides this FAQ, the best place to look is probably your own computer system. You should have a manual page for the LSL checker, if it's installed on your system. Try the Unix command man lsl to see it. You should also look for a directory (such as '/usr/larch/LSL') where the installation of LSL is found. In that directory, you will find a subdirectory 'Doc', where there is some documentation on the checker. See section 2.

The sections of an LSL trait are determined by the LSL grammar [Guttag-Horning-Modet90]. (See section 2.3 Where can I get a checker for LSL?, for a more recent grammar, which is found in the file 'Doc/lsl3_1.y', for version 3.1, and 'Doc/lsl3_2.y', for version 3.2.

LSL trait denotes a theory, which is a collection of true formulas (of sort Bool). This theory contains "the trait's assertions, the conventional axioms of first-order logic, everything that follows from them, and nothing else" (see [Guttag-Horning93], p. 37). For a brief introduction to these ideas, see Chapter 2 of [Guttag-Horning93]; for general background on equational logic, see [Ehrig-Mahr85] or [Loeckx-Ehrich-Wolf96].

Technically, no; all functions specified in LSL are total (see section 2.14 What is the meaning of an LSL specification?). Thus every operator specified in LSL takes on some value for every combination of arguments. What you can do is to underspecify such an operator, by not specifying what its value is on all arguments. For example, the operator head in the handbook trait List (see [Guttag-Horning93], p. 173) is underspecified in this sense, because no value is specified for head(empty).