Java, Jsp, Servlet, Tomcat, J2Ee Hosting, Sun Java Developing, Java Web Server Blog

amstex The American Mathematical Society uses this as their official typesetting system. Many mathematical publications use this macro set. amslatex Adds amstex features to LaTeX. eplain Includes macros for indexing, table of contents, and symbolic cross-referencing. lamstex Can be used with amstex to provide many features that are compatible with LaTeX. texinfo Macros used by the Free Software Foundation to produce software manuals. Text output from these macros can be used with the Red Hat Linux info command. You can create a TeX/LaTeX file using any text editor. After the text and macros (formatting instructions) are created, you can run the tex command (or one of several other related utilities) to format the file. The input file is in the form filename.tex. The output is generally three different files: filename.dvi This is the device independent output file that can be translated for use by several different types of output devices (such as PostScript). filename.log This is a log file that contains diagnostic messages. filename.aux This is an auxiliary file used by LaTeX. The .dvi file that is produced can be formatted to output the document to the particular device you are using. For example, you could use the dvips command to output the resulting .dvi file to your PostScript printer (dvips filename.dvi). Or you could use the xdvi command to preview the dvi file in an X window. Creating and formatting a LaTeX document Because LaTeX is the most common way of using TeX, this section describes how to create and format a LaTeX document. A LaTeX macro (often referred to as a command) appears in a document in one of the two following forms: string{option}[required] First there is a backslash (), which is followed by a string of characters. (Replace string with the name of the command.) Optional arguments are contained in braces ({}), and required arguments are in brackets ([]). ?{option}[required] First there is a backslash (), which is followed by a single character that is not a letter. (Replace ? with the command character.) Optional arguments are contained in braces ({}), and required arguments are in brackets ([]). Each command defines some action to be taken. The action can control page layout, the font used, spacing, paragraph layout, or a variety of other actions on the document. The minimum amount of formatting that a LaTeX document can contain is the following:
If you are looking for affordable and reliable webhost to host and run your business application visit our ftp web hosting services.

Figure 6-6: Set how text is justified and put in columns with the use of the tbl command’s .TS and .TE macros. The PIC macros (.PS and .PE) enable you to create simple diagrams and flow charts to use in Groff. PIC is really only qualified to create simple boxes, circles, ellipses, lines, arcs, splines, and some text. The following is an example of some PIC code that could be included in a Groff document: .PS box invis “Start” “Here”; arrow box “Step 1″; arrow circle “Step 2″; arrow ellipse “Step 3″; arrow box “Step 4″; arrow box invis “End” .PE After the .PS, the first line indicates an invisible box (invis) that contains the words Start Here, followed by an arrow. That arrow connects to the next box containing the words Step 1. The next elements (connected by arrows) are a circle (Step 2), an ellipse (Step 3), another box (Step 4), and another invisible box (End). The .PE indicates the end of the pic drawing. If these lines appeared in a document called memopic.mm, you could preprocess the PIC code and print the file using the following command: $ groff -Tps -l -mm -p memopic.mm Figure 6-7 shows an example of this drawing: Figure 6-7: Create simple flow diagrams with the pic command’s .PS and .PE macros. Cross-Reference For information on the eqn, tbl, or pic command or formatting markup, see their respective man pages. Text processing with TeX/LaTeX TeX is a collection of document formatting commands used primarily to produce scientific and mathematical typeset documents. The most common way to use TeX is by calling a macro package. The most popular macro package for Tex is LaTeX, which takes a higher-level approach to formatting TeX documents. TeX and LaTeX tools are contained in the tetex-latex package. Note The tetex-* packages described in this section are not installed by default in a Red Hat Linux workstation install. The required packages are contained on CD-2 that comes with this book. TeX interprets the LaTeX macros from the latex format file (latex.fmt). By default, the latex.fmt and plain.fmt format files are the only ones that are automatically built when the TeX package is installed. Besides LaTeX, there are other macro format files that you can use with TeX, including:
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.

.BR Bold, then roman (alternating) .DT Set default tabs .HP Begin a hanging indent .I Italics .IB Italics, then bold (alternating) .IP Begin a hanging tag. Used to describe options. Use .TP with long tags. .IR Italics, then roman (alternating) .LP Begin paragraph (same as .PP) .PD Set distance between paragraphs .PP Begin paragraph (same as .LP) .RB Roman, then bold (alternating) .RE End relative indent (used after .RS) .RI Roman, then italics (alternating) .RS Begin relative indent (use .RE to end indent) .SB Small text, then bold (alternating) .SM Small text. Sometimes used to show words in all caps. .SH Section head .SS Subheading within a .SH heading. .TH Title heading. Used once at the beginning of the man page. .TP Begin a hanging tag. Similar to .IP, but .TP begins text on next line, rather than same line as tag. Creating a letter, memo, or white paper with Groff Memorandum macros (which are used with the -mm option of Groff) were once popular among UNIX users for producing technical documents, letters, and memos. Although more modern word processors with a variety of WYSIWYG templates have made mm outdated, in a pinch mm can still be a quick way to create a typeset-style document in a text environment. To format and print a document with mm macros, use the following command line (assuming your default printer is a PostScript printer): $ groff -mm -Tps -l letter.mm The following is a simple example of how to use mm macros to produce a letter: .WA “Christopher T. Craft” 999 Anyway Way Anytown, UT 84111 USA .WE .IA John W. Doe 111 Notown Blvd. Notown, UT 84111 .IE .LO RN “Our telephone conversation” .LO SA “Dear Mr. Doe:” .LT In reference to our telephone conversation on the 4th, I am calling to confirm our upcoming appointment .FC “Yours Truly,” .SG In this example, the .WA, .IA, .IE, .LO, .LT, .FC, and .SG macros are used. The .WA macro begins the writer s address and the .WE ends the address. The .IA begins the recipient s name and address and .IE ends the recipient s address. The .LO RN adds an In reference to: line to the letter that is followed by the text Our telephone conversation. The .LO SA is used to add a salutation line. The .LT indicates that the document is in letter format.
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.

Figure 6-1: Simple markup is required to create man pages. Tip Most man pages are stored in subdirectories of /usr/share/man. Before you create a man page, refer to similar man pages to see the markup and the headings they include. In man1 are commands; man2 contains system calls; man3 has library functions; man4 has special device files (/dev/*), /*); man5 has file formats; man6 has games; man7 has miscellaneous components, and man8 has administrative commands. Most man pages begin with commented lines (.”) that contain descriptive information about the component. Often, information about the GNU license is commented out at the beginning. The first command is the title command (which uses the .TH macro), which includes the title of the man page, section number, source of the component (such as the distribution or kernel name), and the title of the manual. Section headings begin with the .SH macro. Every command should have at least a NAME, SYNTAX, and DESCRIPTION section heading. Your man page may have different types of information, such as environment variables, bugs, or files. A few other kinds of macros are also used in the man page. The .IP macros format indented paragraphs for things such as options. The man page also contains some lower-level font requests; for example, fB says to change the current font to bold, fI changes the font to italic, and fR changes it back to regular font. (This markup is better than asking for a particular font type because it just changes to bold, italic, or regular for the current font.) Figure 6-2 shows what the waycool man page looks like after it is formatted with the man macros and sent to your printer by the following command: $ groff -man -Tps -l waycool.1 Figure 6-2: Man page formatting adds headers and lays out the page of text. Table 6-1 lists the macros that you can use on your man pages. These macros are defined in the tmac.an macro file (usually located in /usr/share/groff/tmac). They are also described on the man(7) manual page (type man 7 man to view that page). Table 6-1: Man Macros Macro Description Macro Description .B Bold .BI Bold, then italics (alternating)
You want to have a cheap webhost for your apache application, then check apache web hosting services.

dvi Produces output in TeX dvi format, which can be output on a variety of devices using commands described later. X75 Produces output for an X11 75 dots/inch previewer. X100 Produces output for an X11 100 dots/inch previewer. latin1 Produces typewriter-like output using the ISO Latin-1 character set. Formatting and printing documents with Groff The best way to try out Groff is to try formatting and printing an existing Groff document. Start by using any man pages on your Red Hat Linux system (such as those in /usr/share/man/*). (Those man pages are compressed, so you may want to copy them to a temporary directory and unzip them to try out Groff.) The following command lines copy the chown man page to the /tmp directory and unzips it. After that, the groff command is used to format the chown man page in plain text so you can page through it on your screen. $ cp /usr/share/man/man1/chown.1.gz /tmp $ gunzip /tmp/chown.1.gz $ groff -Tascii -man /tmp/chown.1 | less In the previous example, the chown man page (chown.1.gz) is copied to the /tmp directory. Then the man page is unzipped (using the gunzip command). Finally, the chown man page (chown.1) is output in plain text (-Tascii) using the man macros (-man). The output is piped to the less command, so you can page through it on your screen. Instead of piping the output to less ( | less), you could direct the output to a file (> /tmp/chown.txt). To format a man page for typesetting, you could specify PostScript or HP LaserJet output. In this case, you don t want to format the document to your screen. You should either direct the output to a file or to a printer. Here are a couple of examples: $ groff -Tps -man /tmp/chown.1 > /tmp/chown.ps $ groff -Tlj4 -man -l /tmp/chown.1 The first example creates PostScript output (-Tps) and directs it to a file called /tmp/chown.ps. That file can be read by a PostScript previewer (such as ghostscript) or sent to a printer (lpr /tmp/chown.ps). The second example creates HP LaserJet output (-Tlj4) and directs it to the default printer (-l option). If your default printer is a PostScript printer, use -Tps instead. Creating a man page with Groff Before HOW-TOs and info files, man pages were the foundation for information about UNIX (and UNIX-like) systems. Each command, file format, device, or other component either had its own man page or was grouped on a man page with similar components. To create your own man page requires that you learn only a few macros (in particular, man macros). Figure 6-1 is an example of the source file for a fictitious man page for a command called waycool.
You want to have a cheap webhost for your apache application, then check apache web hosting services.

man The man macros are used to create Linux man pages. You can format a man page using the -man option to the groff command. (The man macros are discussed further in the section on creating a man page with groff.) mm The mm macros (memorandum macros) were created to produce memos, letters, and technical white papers. This macro package includes macros for creating a table of contents, lists of figures, references, and other features that are helpful for producing technical documents. These macros were developed and used by AT&T and UNIX System V versions of UNIX. You can format an mm document using the -mm option to the groff, nroff, or troff commands. me The me macros were also used for producing memos and technical papers. This macro package was popular with Berkeley UNIX systems. This macro package is still in use in some places today. You can format an me document using the -me option to the groff command. Groff macro packages are stored in /usr/share/groff/tmac. You can look in these files to see what macro definitions look like. The man macros are contained in the tmac.an file, mm macros are in tmac.m, and me macros are in tmac.e. The naming convention for each macro package is tmac.xxx, where the xxx is replaced by one or more letters representing the macro package. In each case, you can understand the name of the macro package by adding an m to the beginning of the file suffix. Tip Instead of indicating -man or -mm on a command line to specify a macro package, you can use -mandoc. This causes Groff to choose the appropriate macro package for the file. When you run the groff formatting command, you can indicate on the command line which macro packages you are using. You can also indicate that the document should be run through any of the following commands that preprocess text from special formats for equations, pictures, or tables: eqn This preprocessor formats macros that produce equations in groff. pic This preprocessor formats macros used to create simple pictures in groff (mostly line drawings). tbl This preprocessor formats macros that produce tables within groff. The formatted Groff document is output for a particular type of device. The device the document is intended for can be a printer, a display program, or (in the case of plain ASCII text) your shell window. Here are the output forms supported by Groff: ps Produces PostScript output that can be printed on a PostScript printer or displayed on a PostScript previewer. lj4 Produces output for an HP LaserJet4-compatible printer or other PCL5-compatible printer. ascii Produces plain text output that can be viewed from a Terminal window. (This is how you produce nroff output with the groff command.)
Note: If you are looking for cheap and reliable webhost to host and run your mysql application check mysql web server services.

Hardcore UNIX/Linux users tend to edit files with either the vi or emacs text editor. These text editors have been around a long time and are hard to learn, but efficient to use. (Your fingers never have to leave the keyboard). The emacs editor has some native GUI support, though it will run fine in a Terminal window. There are also GUI versions of vi and emacs that add menu and mouse features to those editors. These are GVim (gvim command) and Xemacs (xemacs command) editors, respectively. Some of the other, simpler text editors that can run on your graphical desktop are: gedit (gedit command) This text editor, which comes with Red Hat Linux, is the lightweight text editor for the Gnome interface. A menu bar lets you create, open, or save files. It also has simple edit functions (cut, copy, paste, select all, and find). Settings let you set indentations and word wrap. A plug-ins feature lets you select various special functions, such as a spell checker and a diff feature (to compare the contents of the document with another document). You can start gedit from the Start menu by selecting Programs Applications gedit. For more information about gedit, go to http://gedit.pn.og/. Advanced Editor (kwrite command) This text editor includes a menu bar to quickly create, open, or save files. It also has simple edit functions (cut, copy, paste, undo, and help). Other edit features let you set indentations, find/replace text, and select all text. This comes with the KDE desktop, so you can access it by selecting KDE menus Editors Advanced Editor. Text Editor (kedit command) This is another fairly simple text editor. Its features include the ability to open files from your file system or from a Web address (URL). It also includes a convenient toolbar and a spell checker. It comes with the KDE desktop, so you can access it by selecting KDE menus Editors Text Editor. Text processing with Groff The nroff and troff text formatting commands were the first interfaces available for producing typeset quality documents with the UNIX system. They aren’t editors; rather, they are commands that you send your text through, with the result being formatted pages: nroff ( Produces formatted plain text and includes the ability to do pagination, indents, and text justification, as well as other features. troff ( Produces typeset text, including everything nroff can do, plus the capability to produce different kinds of fonts and spacing The troff command also supports kerning. The groff command is the front-end for producing nroff/troff documentation. Because nroff and troff were so popular with UNIX, they were used to produce the documentation for most UNIX systems. That tradition continues to a small extent with Linux in that Linux man pages are formatted and output in Groff. Therefore, most of the examples here help you create and print man pages with Groff. People rarely use primitive nroff/troff markup to create documents. Instead, there are several common macro packages that simplify creating nroff/troff formatted documents. The most popular macro packages are:
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.

Documents with straightforward page layouts work well with Linux documentation tools. For example, a technical book with a few flow charts and images can be easily produced and maintained using Red Hat Linux documentation tools. Letters and memos are also easy to do with these tools. And, of course, Red Hat Linux man pages (which provide separate write-ups for every command, file, and device in Linux) and other Linux documentation are created with these tools. Additionally, Linux likes PostScript. Though many people think of PostScript as a printer output language, it is really more of a programming language (that is, you could write PostScript code directly, if you had the courage). Some document-processing software only includes print drivers for PostScript (although you can get around that problem using conversion programs). Also, many documents on the Web are distributed in PostScript (.ps) format. The drawback to the traditional Linux document tools is that they are not intuitive. Though there are some easier front-ends to LaTeX (see the description of LyX later on), if you are creating documents in a text editor, you will need to learn what macros to type into your documents to format them. This is not as easy as just clicking a style or selecting fonts from a pop-up window. You also need to know which formatting and print commands to use and how to use them. Note For many years, the UNIX system documentation distributed by AT&T was created in troff/nroff formats, which predate Groff. The documents used separate macro packages, man pages, and guide material. Using a source code control system (SCCS), thousands of pages of documentation could be ported to different UNIX systems. Today, Red Hat Linux still includes the same tools to work with man pages. Creating Documents in Groff or LaTeX You can create documents for either of Linux’s Groff (troff/nroff) or LaTeX (TeX) styles of publishing using any text editor. Red Hat Linux comes with several of these text editors, or you can download lots of others from the Internet. See the Choosing a Text Editor sidebar for information on different text editors. The process for creating documents in Groff and LaTeX is generally the same. Use the following steps: 1. Create a document with any text editor. The document will contain text and markup (macros) to indicate how the document is to be formatted. 2. Format the document using a formatting command that matches the style of the document that you created (for example, with groff or latex). During this step, you may need to indicate the type of output device the document is intended for. If the document contains special content, such as equations (eqn command), tables (tbl command), or line drawings (pic command), you may also need to indicate how the file is to be preprocessed. 3. Send the document to an output device. The output device may be a printer or program that displays the page on your screen. If you are used to a word processor with a GUI, you may find either of these publishing tools difficult to work with. In general, Groff is useful if you need to work with or create your own man pages for Red Hat Linux. LaTeX may be useful if you need to produce mathematical documents, perhaps for publication in a technical journal. Choosing a Text Editor
You need excellent and relaible webhost company to host your web applications? Then pay a visit to Inexpensive Web Hosting services.

3. Do you need to exchange documents with other groups? Some organizations are set up to accept documents that use a particular document format. If you need to hand your work to such an organization, you may have your hands tied when it comes to changing how you do your work. Even if you can import a document from another format, you may not be able to convert the document back cleanly. And though your co-workers may accept a one-time conversion, converting each time you send and receive a document can become tedious. 4. Does your organization need to keep running while you change over? Most businesses can t afford to stop working while their documents are converted. The changeover to Red Hat Linux from a Windows 9x/2000 operating system can bring all work to a halt if upgrades don t go smoothly. If you have the resources, a transition period where some Red Hat Linux systems are brought up in parallel, instead of replacing all existing systems, enables work to go on if something goes wrong. Cross-Reference You can read about one person s experience replacing a small office s Windows 95/98 systems with Linux and Star Office in Star Office Wars. The document is located at: http://users.smileys.net/~leonb/StarOffice-wars.html. 5. Are you comfortable fiddling to make things work? To get the formatting right when you are using Groff or LaTeX, you usually have to reformat a few times. That either entails using a tool such as Ghostview (which can be slow) or running back and forth to the printer. You may also want to set up shell scripts to run your formatting and printing commands. All this requires some fiddling. If you, or the people who need to work with the document system you set up, are not comfortable with fiddling, you may want to stick with a commercial word processor. Running tools such as LaTeX (the editor) and Ghostview (the viewer) side by side can get you closer to the WYSIWYG experience. 6. Do you need special features, such as color separations? Most of the advanced publishing features are not yet available in Red Hat Linux. Some professional publishing operations have noted, for example, that there are no Linux tools for doing color separations or some of the other advanced photographic image manipulations. Attributes of Linux publishing Some attributes of the traditional Linux publishing tools make them particularly well suited for certain types of document publishing. As noted earlier, Groff and LaTeX (which is based on TeX) come with Red Hat Linux and are very popular among technical people. There are several reasons why technical people take well to the traditional UNIX/Linux document tools: You can easily manipulate files that are in plain text. Using tools like perl, sed, and grep, you can scan and change one document or hundreds of documents with a single command or script. Scientific and mathematical notation is supported. With geqn, you can create complex equations that can be output with Groff. LaTeX and TeX are particularly suited for technical notation. Some mathematical publications require LaTeX. Editing can be faster because traditional Linux documents are created with a text editor. You can usually get better performance out of a text editor than a word processor. Some people who learn the vi or emacs text editor don t miss a mouse at all. Plus there are X-based text processors today that incorporate many word processing features (such as spell checking and menus for editing functions).
From our experience, we can recommend PHP5 Web Hosting services, if you need affordable webhost to host and run your web application.

1. Do you want to see the layout as you create the document? Most of the document publishing tools that come free with Red Hat Linux have you work with plain text files. Even graphical editors, such as the LyX LaTeX editor, won t show you an exact screen representation of the printed document. Within each text file, you indicate formatting by adding macros. The macros are interpreted when you either display the document (using programs such as Ghostview or Acrobat) or print the document. In other words, you can t see what the document will look like as you write it. If you prefer a WYSIWYG (What-You-See-Is-What-You-Get) document system, I recommend commercial graphical word processors for Linux, such as Anyware Office, WordPerfect, or Star Office. In addition to enabling you to see the layout, these software applications tend to have simplified ways of integrating text with graphics, tables, and other document elements. They also support conversion programs from many popular document formats. See the section on attributes of Linux publishing to understand the characteristics of each type of document processing system. 2. Are you working with a set of documents that need to be converted? If you or your organization is currently using a word processing system to create documents, it is not a trivial task to move those documents to Red Hat Linux. In particular, if your documents are complex (including multiple columns, forms, or other items), or if there are many documents to convert, the conversion process can hurt your workflow. Here is a list of document elements that don t always convert cleanly: Multiple columns Forms Breaks (page breaks, section breaks, and column breaks) Tables Styles (you might lose the markup during conversion) Tip Before committing to converting all the documents in your organization to a Linux platform, test converting a few first. Make sure that the documents you test contain many of the most complex elements used by your co-workers. In particular, look for the elements shown in the previous list. Red Hat Linux comes with a set of tools for converting documents and images from a variety of formats to other formats. Likewise, most WYSIWYG word processors enable you to import and export different document and image formats. In general, the older the document format, the better it will convert. That is because later word processing formats contain more complex features that are harder to cleanly convert. See the section on converting documents for information about Red Hat Linux tools for converting different document formats.
We recommend cheap and reliable webhost to host and run your web applications: Coldfusion Web Hosting services.