Skip to content

Commit

Permalink
Use Roman numerals for page numbers of non-recipes.
Browse files Browse the repository at this point in the history
Previously the pages preceding the recipes (Introduction, Convention, etc.)
had standard page numbers, when they should have used lowercase Roman
numerals. That is now fixed.
  • Loading branch information
runpaint committed May 9, 2009
1 parent c079cdd commit 87e3f26
Show file tree
Hide file tree
Showing 6 changed files with 111 additions and 102 deletions.
2 changes: 1 addition & 1 deletion templates/layout.css
Expand Up @@ -168,7 +168,7 @@ pre { margin: 1em 1.3em; color: #600; }
/* which section uses which named page */

div.halftitlepage, div.titlepage, div.imprint, div.dedication { page: blank }
div.foreword, div.toc, div.preface { page: frontmatter }
div.frontmatter, div.foreword, div.toc, div.preface { page: frontmatter }


/* page breaks */
Expand Down
2 changes: 2 additions & 0 deletions text/01_pre/01_introduction.html
@@ -1,3 +1,4 @@
<div class="frontmatter">
<h3 id="introduction">Introduction</h3>

<p>The Vim text editor is perhaps as famous for its learning curve as it is
Expand Down Expand Up @@ -28,3 +29,4 @@ <h3 id="introduction">Introduction</h3>
<p>&mdash;<a href="http://runpaint.org/"><i>Run Paint Run Run</i></a> (<a
href="mailto:runrun@runpaint.org">runrun@runpaint.org</a>), 2009,
U.K.</p>
</div>
45 changes: 23 additions & 22 deletions text/01_pre/02_conventions.html
@@ -1,34 +1,35 @@
<h3 id="conventions">Conventions</h3>
<div class="frontmatter">
<h3 id="conventions">Conventions</h3>

<p>The following typographical conventions are used in this book:</p>
<p>The following typographical conventions are used in this book:</p>

<h4>Key Presses</h4>
<h4>Key Presses</h4>

<p><kbd>&lt;Esc&gt;</kbd> - Indicates that the named key should be
pressed.</p>
<p><kbd>&lt;Esc&gt;</kbd> - Indicates that the named key should be
pressed.</p>

<p><kbd><kbd>&lt;Ctrl&gt;</kbd>-<kbd>p</kbd></kbd> - Keys joined with a
<tt>-</tt> should be pressed simultaneously. In this example the
<kbd>&lt;Ctrl&gt;</kbd> should be held down while the <kbd>p</kbd> key is
pressed.</p>
<p><kbd><kbd>&lt;Ctrl&gt;</kbd>-<kbd>p</kbd></kbd> - Keys joined with a
<tt>-</tt> should be pressed simultaneously. In this example the
<kbd>&lt;Ctrl&gt;</kbd> should be held down while the <kbd>p</kbd> key is
pressed.</p>

<h4>Normal Mode Commands</h4>
<h4>Normal Mode Commands</h4>

<p><kbd>gqap</kbd> - The named characters should be entered in order while in
<i>Normal</i> mode.</p>
<p><kbd>gqap</kbd> - The named characters should be entered in order while in
<i>Normal</i> mode.</p>

<h4>Command-Line Commands</h4>
<h4>Command-Line Commands</h4>

<p><tt>:set spell</tt> - The command should be typed in
<i>Command-Line</i> mode. (If you're in a different mode, press
<kbd>&lt;Esc&gt;</kbd> before you type the command).</p>
<p><tt>:set spell</tt> - The command should be typed in
<i>Command-Line</i> mode. (If you're in a different mode, press
<kbd>&lt;Esc&gt;</kbd> before you type the command).</p>

<p><tt>:!<var>command</var></tt> - As above, but <var>command</var> is a variable
which should be substituted for its value.</p>
<p><tt>:!<var>command</var></tt> - As above, but <var>command</var> is a variable
which should be substituted for its value.</p>

<h4>Monospaced Font</h4>

<p>A <tt>fixed width</tt> font is used for filenames, code, and variable
names.</p>
<h4>Monospaced Font</h4>

<p>A <tt>fixed width</tt> font is used for filenames, code, and variable
names.</p>
</div>

100 changes: 51 additions & 49 deletions text/01_pre/03_contributing.html
@@ -1,49 +1,51 @@
<h3 id="contributing">Contributing</h3>

<p>This book is released under a Creative Commons Attribution-Share Alike 3.0
Unported License, and its complete text is available in a Git repository. All
contributions are welcomed. Patches are preferred, but if you're not
comfortable with Git you can use the issue tracker as described below.</p>

<h4>Issue Tracker</h4>

<p>You may report typographical errors, factual mistakes, or unclear passages
via the web-based issues tool at <a
href="http://github.com/runpaint/vim-recipes/issues"
>github.com/runpaint/vim-recipes/issues</a>.</p>

<h4>E-mail</h4>

<p>You can send patches and bug reports to <a
href="mailto:runrun@runpaint.org">runrun@runpaint.org</a>.</p>

<h4>Patches</h4>

<p>The source for this book is available in a Git repository. If you have Git
installed on your system you may clone the repository using the URL <a
href="git://github.com/runpaint/vim-recipes.git">git://github.com/runpaint/vim-recipes.git</a>.
(For an introduction to Git see the <a href="http://book.git-scm.com/">Git
Community Book</a>).</p>

<p>You'll probably want to do something like this:</p>

<pre>
<samp>$ </samp><kbd>git clone git://github.com/runpaint/vim-recipes.git</kbd>
<samp>Initialized empty Git repository in /tmp/vim-recipes/.git/
remote: Counting objects: 666, done.
remote: Compressing objects: 100% (610/610), done.
remote: Total 666 (delta 350), reused 0 (delta 0)
Receiving objects: 100% (666/666), 407.52 KiB | 35 KiB/s, done.
Resolving deltas: 100% (350/350), done.
</samp>
<samp>$ </samp><kbd>cd vim-recipes</kbd>
<samp>$ </samp><kbd>vim text/04_basics/09_configuring_vim.html</kbd>
<samp>$ </samp><kbd>git commit -a</kbd>
</pre>

<p>Then either send me a patch (<tt>runrun@runpaint.org</tt>), or post it to
the issue tracker.</p>

<p>Alternatively, if you already use <a href="http://github.com/">GitHub</a>,
fork <a href="http://github.com/runpaint/vim-recipes">the repository</a>, make
your changes, then send me a <i>pull request</i>.</p>
<div class="frontmatter">
<h3 id="contributing">Contributing</h3>

<p>This book is released under a Creative Commons Attribution-Share Alike 3.0
Unported License, and its complete text is available in a Git repository. All
contributions are welcomed. Patches are preferred, but if you're not
comfortable with Git you can use the issue tracker as described below.</p>

<h4>Issue Tracker</h4>

<p>You may report typographical errors, factual mistakes, or unclear passages
via the web-based issues tool at <a
href="http://github.com/runpaint/vim-recipes/issues"
>github.com/runpaint/vim-recipes/issues</a>.</p>

<h4>E-mail</h4>

<p>You can send patches and bug reports to <a
href="mailto:runrun@runpaint.org">runrun@runpaint.org</a>.</p>

<h4>Patches</h4>

<p>The source for this book is available in a Git repository. If you have Git
installed on your system you may clone the repository using the URL <a
href="git://github.com/runpaint/vim-recipes.git">git://github.com/runpaint/vim-recipes.git</a>.
(For an introduction to Git see the <a href="http://book.git-scm.com/">Git
Community Book</a>).</p>

<p>You'll probably want to do something like this:</p>

<pre>
<samp>$ </samp><kbd>git clone git://github.com/runpaint/vim-recipes.git</kbd>
<samp>Initialized empty Git repository in /tmp/vim-recipes/.git/
remote: Counting objects: 666, done.
remote: Compressing objects: 100% (610/610), done.
remote: Total 666 (delta 350), reused 0 (delta 0)
Receiving objects: 100% (666/666), 407.52 KiB | 35 KiB/s, done.
Resolving deltas: 100% (350/350), done.
</samp>
<samp>$ </samp><kbd>cd vim-recipes</kbd>
<samp>$ </samp><kbd>vim text/04_basics/09_configuring_vim.html</kbd>
<samp>$ </samp><kbd>git commit -a</kbd>
</pre>

<p>Then either send me a patch (<tt>runrun@runpaint.org</tt>), or post it to
the issue tracker.</p>

<p>Alternatively, if you already use <a href="http://github.com/">GitHub</a>,
fork <a href="http://github.com/runpaint/vim-recipes">the repository</a>, make
your changes, then send me a <i>pull request</i>.</p>
</div>
14 changes: 8 additions & 6 deletions text/01_pre/04_license.html
@@ -1,7 +1,9 @@
<h3 id="license">License</h3>
<div class="frontmatter">
<h3 id="license">License</h3>

<p>This work is licensed under the Creative Commons Attribution-Share Alike
3.0 Unported License. To view a copy of this license, visit <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>
or send a letter to Creative Commons, 171 Second Street, Suite 300, San
Francisco, California, 94105, USA.</p>
<p>This work is licensed under the Creative Commons Attribution-Share Alike
3.0 Unported License. To view a copy of this license, visit <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>
or send a letter to Creative Commons, 171 Second Street, Suite 300, San
Francisco, California, 94105, USA.</p>
</div>
50 changes: 26 additions & 24 deletions text/01_pre/05_credits.html
@@ -1,28 +1,30 @@
<h3 id="credits">Credits</h3>
<div class="frontmatter">
<h3 id="credits">Credits</h3>

<h4>Cover Image</h4>
<h4>Cover Image</h4>

<p>The cover photograph of <a href="http://moolenaar.net/">Bram Moolenaar</a>,
the creator of Vim, was taken by <a
href="http://sebastian-bergmann.de/">Sebastian Bergmann</a> and kindly
released under a <a
href="http://creativecommons.org/licenses/by-sa/2.0/">Creative Commons
Attribution-Share Alike 2.0 Generic License</a>. The original photograph can
be viewed at <a
href="http://www.flickr.com/photos/sebastian_bergmann/2110830017/">Flickr</a>.</p>
<p>The cover photograph of <a href="http://moolenaar.net/">Bram Moolenaar</a>,
the creator of Vim, was taken by <a
href="http://sebastian-bergmann.de/">Sebastian Bergmann</a> and kindly
released under a <a
href="http://creativecommons.org/licenses/by-sa/2.0/">Creative Commons
Attribution-Share Alike 2.0 Generic License</a>. The original photograph can
be viewed at <a
href="http://www.flickr.com/photos/sebastian_bergmann/2110830017/">Flickr</a>.</p>

<h4>CSS</h4>
<h4>CSS</h4>

<p>The Cascading Style Sheets used in the production of the book were derived
significantly from the work of others. <a href="http://diveintomark.org/">Mark
Pilgrim</a>'s stylesheet from <a href="http://diveintopython3.org/"><i>Dive
Into Python 3</i></a> was the main inspiration. In conjunction, the CSS
created by <a href="http://people.opera.com/howcome/">Håkon Wium Lie</a> and
<a href="http://www.w3.org/People/Bos/">Bert Bos</a> for their book entitled
<a href="http://www.informit.com/title/0321193121"><i>Cascading Style
Sheets: Designing for the Web, 3rd Edition</i></a>, and graciously made
available via <a href="http://www.alistapart.com/articles/boom">A List
Apart</a>, was particularly helpful. Lastly, <a
href="http://simplesideias.com.br/">Nando Vieira</a>'s <a
href="http://github.com/fnando/kitabu/tree/master">kitabu</a> project
offered ideas on how to tie it all together.</p>
<p>The Cascading Style Sheets used in the production of the book were derived
significantly from the work of others. <a href="http://diveintomark.org/">Mark
Pilgrim</a>'s stylesheet from <a href="http://diveintopython3.org/"><i>Dive
Into Python 3</i></a> was the main inspiration. In conjunction, the CSS
created by <a href="http://people.opera.com/howcome/">Håkon Wium Lie</a> and
<a href="http://www.w3.org/People/Bos/">Bert Bos</a> for their book entitled
<a href="http://www.informit.com/title/0321193121"><i>Cascading Style
Sheets: Designing for the Web, 3rd Edition</i></a>, and graciously made
available via <a href="http://www.alistapart.com/articles/boom">A List
Apart</a>, was particularly helpful. Lastly, <a
href="http://simplesideias.com.br/">Nando Vieira</a>'s <a
href="http://github.com/fnando/kitabu/tree/master">kitabu</a> project
offered ideas on how to tie it all together.</p>
</div>

0 comments on commit 87e3f26

Please sign in to comment.