Release 0.3.1 Changes

Changed user interface
Editors now face a slightly different user interface. Users who haven't logged in do not see the standard editing commands.
Compilation on the fly
Pages are now compiled on the fly, that is, if (for whatever reason) the source of a page is present, but the compiled output is not, the page is compiled and displayed, the result being cached. In former releases, a page wouldn't show up at all if the compiled version was not available, resulting in many time consuming sychronizations to make sure that this is not the case after administrators had upgraded to a new software release or imported files from whatever source. After pages, i. e. sources, are created or modified, pages are still compiled and saved as source code as well as compiled versions.
HTML-support for locale files
Locales may now contain arbitrary HTML-entities (&xxx;) so that the character encoding for the locale file (the file holding the localized text messages) could theoretically remain plain ASCII.
Non-breaking space
The sequences [_] and [ ] evoke a non-breaking space.
Directory hashing
Customized directory hashing takes place by the means of a (pretty fast) user-space hash function. This allows Pie to handle thousands of files without the underlying operating system to suffer from a loss of performance.
Customized file name encoding
File names are now encoded, with special characters (anything but [0-9A-Za-z_]) being escaped. This allows for any character to be used in the names of pages and files. See configuration option nameencode.
Optional vertical bar to indicate alternate link texts
Since page names may now contain spaces (and other characters specified in pagepattern), a different character to mark the beginning of alternate text in links is required. The vertical bar (|) serves this purpose.
Page groups
Pages (and files) can now be grouped as Wiki groups. Note that this requires a different addressing scheme for local resources.
Introduction of editing commands
The page compiler now supports a number of commands that trigger special behaviour depending on the context the command appears in. In fact, many ordinary features, such as page links, are now special cases of commands.
Anchors via commands
The usage of inner-page anchors has changed once more: They are now called upon via the anchor: command.
Configuration option imagepattern removed.
Images now require explicite evocation via [image:MyImage.ext] and are not recognized by their file names any more. In fact, without determined to be displayed, images are just ordinary files.
Double brackets
Double brackets are saved for links to documents, that is, links to local pages and URLs pointing to internet resources. E-mail addresses, images, media components and ordinary files are instantiated via special commands. Note that web URLs and e-mail addresses are still recognized within continuous text.
(Even more) customized link rendering
The customization of how links are rendered no longer takes places in the code of the library, but in the configuration. You don't have to rewrite the code any longer, but just adapt the switches in the global configuration. Refer to pagelink, filelink, et al.
Renaming resources
Pages and files may now be renamed with violated dependencies being displayed.
Manual classes for spans
Text spans and images can now be assigned a specific class to determine their appearance. Being CSS-classes, these classes have to be declared in the server's global CSS-file.
Support for bold, italic and underlined text
These terrible products of the modern world of typesetting can now be embedded into your documents. However, the preferred way is still not to use them, but to rely on emphasized and strongly emphasized text instead.
Lots of documentation
The online documentation as well as the comments in the code library have been extensively extended, or, in the latter case, brought into being for the first time.
Pie powered