This file gives the instruction about the format to create menus in pmwiki pages.

EXTRACT FROM phplm-manual-3.0.pdf: (page 7)
===========================================
http://prdownloads.sourceforge.net/phplayersmenu/phplm-manual-3.0.pdf?download

5.1 - Text file format Data related to the menus can be stored in a text file;
each menu item corresponds to a line, according to the following format:

[dots]|[text]|[link]|[title]|[icon]|[target]|[expanded]

Items have to be listed in the same order resulting from a depth-first search
over the tree, i.e. in the same order they appear on a completely exploded
corresponding tree menu. The | (pipe) character is used as a separator
between the fields; a different separator can be chosen using related
methods, whose documentation can be generated through phpDocumentor, as said
above. Let us consider the above mentioned fields.

[dots] - some dots to decide the hierarchical level of the item: if the
hierarchical level of a generic item is N, then this field must consist of N
dots for that item. The hierarchical level of the first item must be equal to
1, hence you have to use only one dot for the first item. If the hierarchical
level of a generic item is N, then the hierarchical level of its children is
N+1, hence this field must consist of N dots for that item and of N+1 dots
for its children. I explicitly point out that you can use also characters
that are not dots: currently, PHPLM only counts the number of characters of
this field, hence it behave just the same way if you use 3 whatever
characters instead of 3 dots, e.g. foo instead of ... . This field is
mandatory.

[text] - The text label that will be used for the item. This field is
mandatory.

[link] - The URL associated to the item. This field can be empty, i.e. items
that do not link anything are allowed.

[title] - The title attribute to be used for the anchor tag corresponding
to [link]. This field is disregarded if the [link] field is empty. This field
can be empty.

[icon] - The filename of an icon associated to the item. The directory path
for icons has not to set through the suited method, it has not to be written
in this field. According to the habit for favorite icons, such icons have to
consist of 16x16 pixels. The content of this field may be either significant
or not, depending on the menu type and of the link hierarchical
characteristics (leaf item or not); this issue will be clarified later on.
This field can be empty.

[target] - The target attribute to be used for the anchor tag
corresponding to [link] - This field is disregarded if the [link] field
is empty. This field can be empty.

[expanded] - A boolean field to specify if by default the
corresponding branch has to be expanded or not. Currently, this field is
significant only for the tree menus, and obviously, it is not significant for
leaf item. This field can be empty. I explicitly point out that, if the last
N non mandatory fields are empty, you can completely omit them, i.e. you can
omit also the separators... in other words, the separators are needed only
when and where they have to separate something :-) Note: in the menu
structure text file, you can comment out an item as it is usually done for
configuration files and scripts, i.e. simply inserting a # as the first
character of the line. W.r.t. the [link] field, if you need, using the
setPrependedUrl() method, you can set a string to be prepended to the content
of this field for each item. An example of usage of setPrependedUrl() is
provided in the example-db-hormenu.php script and commented later.
