anchor.diff:        As you can see, _unlike_ the blog entries in the <tt>input/</tt> directory, blog entries in the <tt>entries/</tt> directory do not have to worry about their original file name influencing the output file name. As a result, you can organize your blog entry files however you want.
   
         For example, I like to put all blog entry files related to Ruby programming within the <tt>entries/code/ruby/</tt> subdirectory. The names of these subdirectories do not have any special meaning to Rassmalog, so you can name them however you like.
  -
  -    <% section "plugins/" do %>
  +    <% end %>
  +
  +    <% section "<tt>plugins/</tt>", "manifest.plugins" do %>
         This directory contains Ruby source files which define additional Rake tasks for Rassmalog.
   
         <% pluginFiles.each do |file| %>
  -        <% section file do %>
  +        <% section "<tt>#{File.basename(file)}</tt>", file do %>
             |_. Command |_. Description |
             <% `rake -f #{file} -T`.split(/\r?\n/)[1..-1].each do |s| %>
             | <%= s.split('#').join(' | ') %> |
             <% end %>
   
             <noformat><%=
  -            File.read(file)[/\A.*?(?=^#--)/m].gsub(/^# ?/, ' ').to_html
  +            File.read(file)[/\A.*?(?=^#--)/m].
  +            gsub(/^# ?/, '').indent_to_pre.to_html
             %></noformat>
           <% end %>
         <% end %>
  
positive.code:   <% section "Manifest", 'manifest' do %>
      Now that Rassmalog is installed on your system, let us examine its installation directory. Inside, you will see (among other things) the following items:
  
      * <tt>rassmalog.rb</tt>
        - the core of Rassmalog.
  
      * <tt id="manifest.doc">doc/</tt>
        - documentation for Rassmalog users
  
        * <tt>doc/guide.erb</tt>
          - source code of this user guide
  
      * <tt id="manifest.config">config/</tt>
        - directory that contains all configuration files.
  
        * <tt>config/blog.yaml</tt>
          - the primary configuration file for your blog.
  
        * <tt>config/feed.erb</tt>
          - template for generating RSS feeds for the blog.
  
        * <tt>config/html.erb</tt>
          - template for generating a complete HTML web page.
  
        * <tt>config/chapter.erb</tt>
          - template for generating HTML for lists of tags and archives.
  
        * <tt>config/section.erb</tt>
          - template for generating HTML for individual tags and archives.
  
        * <tt>config/listing.erb</tt>
          - template for generating the recent/all lists of blog entries.
  
        * <tt>config/entry.erb</tt>
          - template for generating HTML for a blog entry.
  
        * <tt>config/format.rb</tt>
          - defines how text is transformed into HTML.
  
        * <tt id="manifest.lang">config/lang/</tt>
          - directory that contains translations of English text used in the core of Rassmalog. These translations do not include English text used in the templates (<tt>config/*.erb</tt>) because those are already separate from the core of Rassmalog.
  
        <% langFiles.each do |file| %>
          * <tt><%= file %></tt> <%= File.readlines(file)[0].chomp.scan(/\(.*\)/)[0] %>
  
        <% end %>
  
      * <tt id="manifest.output">output/</tt>
        - directory that contains your generated blog.
  
      * <tt id="manifest.input">input/</tt>
        - directory that contains (1) source files for blog entries and (2) additional resources, such as images and stylesheets, that are used by your blog. Everything inside this directory, except source files for blog entries, is automatically copied into the <tt>output/</tt> directory (relative paths are preserved) when your blog is generated.
  
        A blog entry source file's name must end with a <tt>.yaml</tt> extension. By default, a source file's corresponding output file has (1) the same name and relative path as the source file but (2) ends with a <tt>.html</tt> extension.
  
        For example, the <tt>input/foo/bar/moz.yaml</tt> source file's corresponding output file is <tt>output/foo/bar/moz.html</tt>. You can override this default behavior by adding the "*output_file* parameter":#param.output_file to your blog entry.
  
        * <tt>input/styles/screen.css</tt>
          - the default CSS stylesheet provided with Rassmalog.
  
        * <tt>input/styles/print.css</tt>
          - the default CSS stylesheet provided with Rassmalog.
  
        * <tt>input/rassmalog/entry.yaml</tt>
          - reference of the blog entry file format.
  
      * <tt id="manifest.entries">entries/</tt>
        - directory that contains blog entry source files whose output files are *automatically calculated* by Rassmalog.
  
        A blog entry source file's name must end with a <tt>.yaml</tt> extension. By default, all source files in this directory will have a corresponding output file with a name in the form: "_date_-_name_.html".
  
  
negative.code: 
      For example, if you have an RSS feed file named <tt>feed.xml</tt> then you would import it into Rassmalog like this:
  
      pre. rake import < feed.xml
    <% end %>
  
    <% section "Creating RSS feeds" do %>
  