% LaTeX
\documentclass[leqno]{article}
\usepackage[utf8]{inputenc}
\usepackage{url}
\usepackage{graphicx}
\usepackage{amsmath}
\usepackage{amssymb}
\usepackage{amsfonts}
\usepackage{bm}
\usepackage{gellmu}
\usepackage[margin=100bp,nohead]{geometry}
\setlength{\parskip}{6bp}
\setlength{\parindent}{0bp}
\pagestyle{plain}
\thispagestyle{empty}
\title{About the XML Files Found Here}
\newlength{\centerskip}
\setlength{\centerskip}{\topsep}
\newcommand{\hsf}{\hspace*{\fill}}
\newcommand{\tdbc}[1]{\hsf\textbf{#1}\hsf}
\newenvironment{menulist}{
\begin{list}{}{
\setlength{\topsep}{0bp}
\setlength{\labelwidth}{0.03\linewidth}
\setlength{\leftmargin}{0.06\linewidth}
\setlength{\itemindent}{0bp}
\setlength{\itemsep}{-6bp}
\setlength{\parsep}{6bp}}
}{\end{list}}
\newenvironment{Menulist}{
\begin{list}{}{
\setlength{\topsep}{0bp}
\setlength{\labelwidth}{0.03\linewidth}
\setlength{\leftmargin}{0.06\linewidth}
\setlength{\itemindent}{0bp}
\setlength{\itemsep}{3bp}
\setlength{\parsep}{6bp}}
}{\end{list}}
\newenvironment{toclist}{\normalsize
\begin{list}{}{
}}{\end{list}}
\newenvironment{Toclist}{\large
\begin{list}{}{
}}{\end{list}}
\newenvironment{citations}{
\begin{list}{}{
\setlength{\topsep}{0bp}
\setlength{\labelwidth}{0bp}
\setlength{\leftmargin}{0.04\linewidth}
\setlength{\labelsep}{0bp}
\setlength{\itemindent}{-0.2\leftmargin}
\setlength{\itemsep}{3bp}
\setlength{\parsep}{0bp}}
}{\end{list}}
\begin{document}
\begin{center}\LARGE\bfseries{}
About the XML Files Found Here
\end{center}

\medskip
\par{The files in this directory are all examples under the didactic document type that is called \emph{article}. \ 
}
\par{From early days of the project until mid 2006 the translator that converted the \textsc{SGML} form of an \emph{article} to the (only) \textsc{XML} form of \emph{article} automatically generated section numbers, tables of contents, and cross-referencing information. \ 
}
\par{Since mid 2006, this stage of the standard pipeline has been split in two, and there are now two \textsc{XML} versions of \emph{article}. \   The one produced directly from \textsc{SGML} (with suffix \texttt{".xml"}) is author-level and very nearly equivalent to original source. \   It resides under a strict document type definition for the \textsc{XML} version of \emph{article} that may be regarded as suitable for authors who wish to write \emph{article} originally as \textsc{XML} source. \   With the new standard pipeline these \textsc{XML} document instances qualify as ``stand-alone'' \textsc{XML} documents. \ 
}
\par{The second \textsc{XML} form of \emph{article} (with suffix \texttt{".exml"}) is very nearly equivalent to what was previously the only \textsc{XML} form of \emph{article} in the production system. \   For maximum efficiency in subsequent generation of end formats the translator producing the second \textsc{XML} form simultaneously produces various auxiliary files containing \label{xet}(1) \textsc{XML} entity definitions (suffix \texttt{.xet})\footnote{Some of the entity definitions may be superfluous, but they cause no harm. \  (There is more than one conceivable way to generate the \textsc{XML} version of an article.)}, \label{xlb}(2) label information (suffix \texttt{.xlb}), and \label{xcn}(3) a table of contents (suffix \texttt{.xcn}) as appropriate. \ 
}
\par{The items (1) and (3) represent included entities in the second \textsc{XML} version of an \emph{article} and, therefore, must be present in order to produce conforming \textsc{XML}. \   This means that the second \textsc{XML} form of an \emph{article} does not qualify as a ``stand-alone'' \textsc{XML} instance. \  The current formatters for the \textsc{HTML} and \LaTeX{} targets make use of item (2). \ 
}
\par{In early 2002, motivated by \textsc{CSS} handling in the browser \textsl{Opera~6}, the author began very tentatively building a \textsc{CSS} style sheet for browser-based rendering of the XML version of the \textsc{GELLMU} \emph{article} document type. \   The \textsc{CSS} sheet remains very much under construction, and, at best, \textsc{CSS} is a cruder rendering vehicle for arbitrary XML tag vocabularies than a finely honed translation to standard \textsc{HTML} or \textsc{XHTML} with appropriate use of \textsc{CSS} styling. \ 
}
\par{In general, there is an expectation that a web browser with \textsc{XML} capability will render an \textsc{XML} document that is accompanied by a \textsc{CSS} style sheet, but such browsers, as a general rule, should not be expected to handle document instances except when ``stand-alone''. \ 
}
\par{In particular, the first \textsc{XML} form of an \emph{article} is the one that should be considered most suitable for \textsc{CSS}-styled rendering. \  
}
\end{document}