-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.html
80 lines (80 loc) · 6.96 KB
/
README.html
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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>remark - lazy, sleazy plain text markup</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div class="book" title="remark - lazy, sleazy plain text markup"><div class="titlepage"><div><div><h1 class="title"><a id="id2677872"></a> remark - lazy, sleazy plain text markup </h1></div><div><div class="author"><h3 class="author"><span class="firstname">[email protected]</span></h3></div></div><div><div class="othercredit"><h3 class="othercredit"><span class="othername">Generated by remark 1.1.1 Sat, 09 Aug 2003 at 14:48</span></h3></div></div><div><p class="copyright">Copyright © 1997-2003 [email protected]. All Rights Reserved</p></div></div><hr /></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="#id2679220">Preface</a></span></dt><dt><span class="chapter"><a href="#id2679233">1. Remark</a></span></dt><dd><dl><dt><span class="section"><a href="#id2679252">Building Remark</a></span></dt><dt><span class="section"><a href="#id2719669">Emacs vs. The World</a></span></dt><dt><span class="section"><a href="#id2719707">Processing Text</a></span></dt><dt><span class="section"><a href="#id2678130">Bugs and Contributions</a></span></dt></dl></dd></dl></div><div class="preface" title="Preface"><div class="titlepage"><div><div><h2 class="title"><a id="id2679220"></a>Preface</h2></div></div></div><p>
This is remark, attila's lazy, sleazy plain text markup system.
</p></div><div class="chapter" title="Chapter 1. Remark"><div class="titlepage"><div><div><h2 class="title"><a id="id2679233"></a>Chapter 1. Remark</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#id2679252">Building Remark</a></span></dt><dt><span class="section"><a href="#id2719669">Emacs vs. The World</a></span></dt><dt><span class="section"><a href="#id2719707">Processing Text</a></span></dt><dt><span class="section"><a href="#id2678130">Bugs and Contributions</a></span></dt></dl></div><p>
<span class="emphasis"><em>The idea is simple</em></span>: turn a file that looks more or less like this one
right here into DocBook XML, and thence into whatever the hell you want.
Remark supports popping out PS, PDF, and DVI output right now, with the help
of some external tools. RTF is easily possible, and HTML is coming.
</p><div class="section" title="Building Remark"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2679252"></a>Building Remark</h2></div></div></div><p>
Remark uses the standard perly build system fu:
</p><p>
<code class="literal">$ perl Makefile.PL</code>
</p><p>
<code class="literal">$ make</code>
</p><p>
<code class="literal">$ sudo make install</code>
</p><p>
If this does not work for you, please let me know. I should beef up my
dependency checking a bit, to make sure that jade or openjade is installed,
at least, but right now, I don't check. Also, if you are a BSD user, then
you might not like Makefile.PL installing stuff into /usr/bin and /usr/lib
instead of /usr/local/bin and /usr/local/lib, in which case I recommend:
</p><p>
<code class="literal">$ perl Makefile.PL PREFIX=/usr/local INSTALLDIRS=site</code>
</p><p>
instead. This will force remark into /usr/local, as Pan intended. Other
than that, there's not much to installing remark.
</p></div><div class="section" title="Emacs vs. The World"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2719669"></a>Emacs vs. The World</h2></div></div></div><p>
I am an Emacs person. This means that all of this stuff is slanted
towards Emacs users, but it's all perfectly usable by others. It's just
that the actual process of typing the text up is a bit easier if your editor
understands all the magic goobers that appear e.g. at the bottom of this
file (and in the template).
</p><p>
If you <span class="emphasis"><em>are</em></span> an Emacs person, then those goobers are very handy. They
configure your buffer such that hitting Meta-Q (fill-paragraph-or-region)
does the right thing: as long as you indent your paragraphs with two spaces
at the start, your text will stay pretty, and all of the section boundaries
will be obeyed.
</p><p>
It's also a good idea to get into the habit of ending sentences with two
spaces. Besides being good form, it also makes the sentence-based movement
operators (Meta-A, Meta-E) work properly.
</p></div><div class="section" title="Processing Text"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2719707"></a>Processing Text</h2></div></div></div><p>
The remark man page describes things fairly completely; you can also
view this same information with the command
</p><p>
<code class="literal">$ remark -H | more</code>
</p><p>
You'll notice in the text above that I used underscores to set off some
text that should be in a computer font, and that I've used stars to set
off text that should be emphasised. You can also use dollar signs, which
I intend to be used for equations ala TeX, but it doesn't quite do all
the right stuff yet... feel free to pitch in!
</p><p>
In any event, if you just point remark at a text file with no other
arguments, it will turn it into DocBook XML:
</p><p>
<code class="literal">$ remark README</code>
</p><p>
will turn this file into README.xml. From there, you can do whatever
you like, but remark knows how to do some additional post-processing,
via the <code class="literal">-R</code> option:
</p><p>
<code class="literal">$ remark -R ps README</code>
</p><p>
will turn this file into README.ps, by using the <code class="literal">jade</code> (or <code class="literal">openjade</code>),
<code class="literal">jadetex</code> and <code class="literal">dvips</code> programs, in that order.
</p></div><div class="section" title="Bugs and Contributions"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id2678130"></a>Bugs and Contributions</h2></div></div></div><p>
Bugs reports and contributions are always welcome. Please email them to
[email protected] with [remark] in the subject, so that my automatic
spam filters (go go gadget bmf! go go gadget procmail!) will know to leave
it alone.
</p><p>
There should be a TODO file in the tarball that has a list of things that
I would like to work on when I have time to spare. If you want to pitch in,
please let me know first, because I may have already started, and it would
be a waste to have us both doing the same thing without coordinating.
</p></div></div></div></body></html>