how frequently does the letter "e" appear in:
the basic usage is similar to wml::des::navbar. most normal navbars should also work with navbar-fh.wml.
the preparation for splicing is mostly done by navbar:render (something may happen during the definition if a language is defined with the short attribute, but navbar-fh.wml should take care of this). navbar-fh.wml produces splices for all languages that are defined when navbar:render is called.
the txt, alt and hint attributes of navbar:button take a syntax that is similar to languages defined with the short attribute. in addition, a default value may be specified similar to the lang:star: syntax.
the attributes url and img of navbar:button now have a syntax similar to lang:star:href:, except that the character # is used for language substitution, since * is already used for the img attribute. if the url or img given is relative, the link will be set to the default page, unless the language specific page exists. as a result, you may have to run wmk -f twice if you add a version of a page in a new language. if you don't use the automatic button creation facility you better take care that at least the default images exist, if you use images at all.
otherwise, the first specified language will be used as the default, ore the whole string if navbar-fh.wml can't find anything it understands.
note that all these attributes should only contain plain text and no other tags!
there is a new attribute defaultlanguage to navbar:define if set, the default values of all parameters are used for this language, instead of the properly substituted ones. say, you have a button with img=ind.#.*.png|ind.*.png, and you generate slices for de, en and es. this will normally give you html-files with references to ind.de.n.png, ind.de.o.png, ind.en.n.png and so on, if these images exist or are created, and to ind.n.png etc. otherwise. if you set defaultlanguage=de, all occurences of ind.de.*.png etc. will also be replaced by ind.*.png. similarily you can have <name>.html for the german pages and <name>.en.html for the english pages, and in case a page is not available in all languages, things should fall back to the default language fairly automagically.
this may or may not be a useful feature depending on your requirements. i implemented it because my site is mostly all german and i didn't want to change the existing urls of the type <name>.html to <name>.de.html when i translated some of my pages.
there is an attribute languages to navbar:render, which allows you to produces navbars for splices in languages that are not defined in your document. it's probably pretty useless, but it was easy to implement, and you never know.
user
In the text, there are two hundred and forty-one "e"s.
assistant