In an attempt to make complex changes to the configuration as painless as possible, BlazeBlogger is shipped with a utility to help you with this task. To display the current value of a particular configuration option, use the blaze-config command followed by an option name:
blaze-config option
To change a configuration option, supply the new value:
blaze-config option value…
BlazeBlogger also allows you to edit all available options at once in an external text editor. To do so, run the blaze-config command with the --edit (or -e) command line option:
blaze-config -e
Note that unless the core.editor configuration option is already set, you must also specify a text editor to use by adding the --editor (or -E) option:
blaze-config -e -E editor
The rest of this section tries to cover the most common configuration tasks, and by no means serves as a full reference. For a complete list of available configuration options, refer to
Section 3.2, “blaze-config”.
Example 2.2. Configuring the Blog in GVim
To edit the configuration in the GVim text editor, run:
public_html]$ blaze-config -e -E "gvim -f"
You can set this editor as the default by typing the following command:
public_html]$ blaze-config core.editor "gvim -f"
2.2.1. General Blog Settings
In order for web browsers to correctly determine the character encoding of a blog, each web page must include an appropriate information in its header. To change this information, update the core.encoding option with a value in the form that is recognized by W3C standards:
blaze-config core.encoding encoding
Keep in mind that this option must match the character encoding you use to write the content. BlazeBlogger does not change the encoding on its own, nor does it check the value you provided. The default option is UTF-8.
To select the document type of the generated pages, use the following command:
blaze-config core.doctype type
Allowed options are
html for
HTML and
xhtml for the
XHTML standard. For compatibility reasons, the default option is to generate HTML pages.
Finally, to change the file extension of the generated pages, run:
blaze-config core.extension extension
The changes will take effect the next time you build the blog with the blaze-make command.
Example 2.3. Changing the Blog Encoding
In most cases, the use of UTF-8 is recommended. However, if you write your blog in other encoding such as ISO-8859-2 (that is, Latin-2), type:
public_html]$ blaze-config core.encoding ISO-8859-2
The option has been successfully saved.
