/usr/share/doc/udo-doc-en/html/001004.html is in udo-doc-en 6.4.1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<!-- last modified on 2005/08/09 -->
<html lang="en">
<head>
<title>
The guide to UDO: Once upon a time
</title>
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
<meta http-equiv="Content-Language" content="en">
<meta http-equiv="Content-Style-Type" content="text/css">
<meta http-equiv="Content-Script-Type" content="text/javascript">
<meta name="Generator" content="UDO 6.4 PL1 for Linux">
<meta name="Author" content="Dirk Hagedorn">
<link rel="chapter" href="001.html" title="Introduction">
<link rel="chapter" href="opensrc.html" title="Open Source">
<link rel="chapter" href="003.html" title="Installation">
<link rel="chapter" href="004.html" title="Usage">
<link rel="chapter" href="005.html" title="The syntax of UDO">
<link rel="chapter" href="006.html" title="Tips & tricks">
<link rel="section" href="001001.html" title="Preface">
<link rel="section" href="001002.html" title="What UDO can('t) do for you">
<link rel="section" href="001003.html" title="Do you need UDO?">
<link rel="section" href="001005.html" title="Contact addresses">
<link rel="section" href="001006.html" title="Thanks">
<link rel="appendix" href="_a.html" title="Frequently asked questions">
<link rel="appendix" href="_b.html" title="Bugs">
<link rel="appendix" href="_c.html" title="Error messages">
<link rel="appendix" href="_d.html" title="This & that">
<link rel="appendix" href="_e.html" title="History">
<link rel="appendix" href="_f.html" title="Command index">
<link rel="start" href="index.html" title="Begin of the document">
<link rel="home" href="index.html" title="Begin of the document">
<link rel="contents" href="index.html#UDOTOC" title="Contents">
<link rel="toc" href="index.html#UDOTOC" title="Contents">
<link rel="first" href="001.html" title="Introduction">
<link rel="prev" href="001003.html" title="Do you need UDO?">
<link rel="previous" href="001003.html" title="Do you need UDO?">
<link rel="next" href="001005.html" title="Contact addresses">
<link rel="last" href="_f016.html" title="---">
<link rel="copyright" href="aboutudo.html" title="UDO6">
</head>
<body>
<a href="index.html"><img src="udo_hm.gif" alt="Home" border="0" width="24" height="24"></a>
<a href="001.html"><img src="udo_up.gif" alt="Introduction" border="0" width="24" height="24"></a>
<a href="001003.html"><img src="udo_lf.gif" alt="Do you need UDO?" border="0" width="24" height="24"></a>
<a href="001005.html"><img src="udo_rg.gif" alt="Contact addresses" border="0" width="24" height="24"></a>
<hr>
<h1><a name="Once_20upon_20a_20time">Once upon a time</a></h1>
<p>It was autumn 1994 when I wrote some little programs for which I
needed an ASCII manual, an online help and a printed documentation.
</p>
<p>In all cases I began writing the ASCII manual. In a copy of it I
inserted hypertext commands. Finally the ASCII manual was imported
into a text processor, layouted and printed. It didn't take a long
time for me to recognize that this was an inefficient work: if there
were any changes in one of the files both the others had to be changed
in the same way. And if there were lots of changes it was necessary to
start the whole procedure right from the beginning.
</p>
<p>When I finished these manuals I said to myself: "Oh no, Dirk,
there <i>must</i> be another and easier way to get different versions
of one text file!".
</p>
<p>January 1995 I started to think about a new text format with the
project name "UDO" (as the abbreviation for
<b>U</b>niversal <b>DO</b>cument). The UDO syntax should be easy to
learn and flexible enough and so I decided to create a syntax like
LaTeX. Next to this I began writing the software that was able to
convert this new text format into ASCII, ST-Guide and LaTeX: UDO was
born!
</p>
<p>At this time UDO was really a small program with only some
features. The syntax contained about 10 commands and the source code
was about 10 KB large. Nevertheless this small hack was of a great
help for myself and the upper described horror scenario was history.
</p>
<p>Since this time UDO has been growing up day by day. UDO now
supports many different text formats, it offers a large variety of
layouting commands, it's available for different operating system and
the size of its source code and documentation is now a hundred times
larger than it was in former days.
</p>
<p>In these two years UDO has become to an operating system
independent, very powerful and — proverbially said —
universal tool.
</p>
<hr>
<a href="index.html"><img src="udo_hm.gif" alt="Home" border="0" width="24" height="24"></a>
<a href="001.html"><img src="udo_up.gif" alt="Introduction" border="0" width="24" height="24"></a>
<a href="001003.html"><img src="udo_lf.gif" alt="Do you need UDO?" border="0" width="24" height="24"></a>
<a href="001005.html"><img src="udo_rg.gif" alt="Contact addresses" border="0" width="24" height="24"></a>
</body></html>
|