<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <HEAD> <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9"> <TITLE>Linuxdoc Reference: Inline Tags</TITLE> <LINK HREF="Linuxdoc-Reference-9.html" REL=next> <LINK HREF="Linuxdoc-Reference-7.html" REL=previous> <LINK HREF="Linuxdoc-Reference.html#toc8" REL=contents> </HEAD> <BODY> <A HREF="Linuxdoc-Reference-9.html">Next</A> <A HREF="Linuxdoc-Reference-7.html">Previous</A> <A HREF="Linuxdoc-Reference.html#toc8">Contents</A> <HR> <H2><A NAME="inline"></A> <A NAME="s8">8. Inline Tags</A></H2> <P>Here the abstract <EM>inlines</EM> are broken down until only true and usable tags will remain. Let's recall: <HR> <PRE> <!entity % inline " (#pcdata | f| x| %emph; |sq| %xref | %index | file )* " > </PRE> <HR> Inlines don't have a influence to paragraphing, sectioning or document classing. Just modifying text within it's normal flow. <P> <P> <H2><A NAME="emph"></A> <A NAME="ss8.1">8.1 Emphasizes</A> </H2> <P> <HR> <PRE> <!entity % emph " em|it|bf|sf|sl|tt|cparam " > </PRE> <HR> <P>The <EM>emphasizes</EM> are gathering the tags for emphasizing inline text. <P> <P>The different types of emphasizes are: <P> <DL> <DT><B><CODE>em</CODE> -> The Emphasize Tag</B><DD><P>I hate to be redundant but I have to say: The <EM>emphasize</EM> tag you place for emphasized text. Normally it's mapped to italic letters. So if you write <CODE><em/a emphasized text/</CODE> it will be mapped to <EM>a emphasized text</EM>. <P> <DT><B><CODE>it</CODE> -> The Italic Tag</B><DD><P>The <EM>italic</EM> tag you place for a cursive mapping. If you write <CODE><it/a italic text/</CODE> it will be mapped to <I>a italic text</I>. <P> <DT><B><CODE>bf</CODE> -> The Boldface Tag</B><DD><P>The <EM>boldface</EM> tag you place for a bold mapping. If you write <CODE><bf/a bold text/</CODE> it will be mapped to <B>a bold text</B>. <P> <DT><B><CODE>sf</CODE> -> The Swissfont Tag</B><DD><P>I know that Tom Gordon from GMD is telling that this is the <CODE>sans serif</CODE> tag. My interpretation of the sf is <EM>swissfont</EM> wich for me is more easy to remember. This is mapping the inlined text to a font wich is out of the helvetica family. So <CODE><sf/a swissfont text/</CODE> will be mapped to <SF>a swissfont text</SF>. <P> <DT><B><CODE>sl</CODE> -> The Slanted Tag</B><DD><P>I think I skip the explanation. <CODE><sl/a slanted text/</CODE> will be mapped to <I>a slanted text</I>. <P> <DT><B><CODE>tt</CODE> -> The Terminaltype Tag</B><DD><P>Text tagged with <EM>terminaltype</EM> will be placed inline, just like all the other text within a paragraph. It will not be included into source output if you are workink as described in section <A HREF="Linuxdoc-Reference-12.html#litprog">Literate Programming</A>, even if it's looking like typed code. <CODE><tt/a terminal typed text/</CODE> will be mapped to <CODE>a terminal typed text</CODE>. </DL> <P> <P> <H2><A NAME="sq"></A> <A NAME="ss8.2">8.2 Short-quote Tag</A> </H2> <P>Normally this one could be viewed the same level like one of the <EM>emphasize</EM> tags, but the definition of the linuxdoc dtd is placing it same level like the emphasizes, and so I do. <P>The <CODE>shortquote</CODE> tag is a inline quotation, not forming an own paragraph. The text <CODE><sq/a short quote/</CODE> is mapped to "a short quote". <P> <P> <H2><A NAME="f"></A> <A NAME="ss8.3">8.3 Formula Tag</A> </H2> <P>The <EM>formula</EM> tag allows us to note down a mathematical formula within the normal text, not appearing in an own line. So the text <CODE><f>x=y<sup>2</sup></f></CODE> will be displayed as x=y<SUP>2</SUP>. See <A HREF="Linuxdoc-Reference-9.html#formula">Mathematical Fomulas</A> for the tags valid within the <EM>formula</EM>. <P> <P> <H2><A NAME="x"></A> <A NAME="ss8.4">8.4 External Tag</A> </H2> <P>The <EM>external tag</EM> is passing the tagged data directly through the parser, without modifying it. E.g. to LaTeX. <P> <P> <P> <HR> <A HREF="Linuxdoc-Reference-9.html">Next</A> <A HREF="Linuxdoc-Reference-7.html">Previous</A> <A HREF="Linuxdoc-Reference.html#toc8">Contents</A> </BODY> </HTML>