Consider using <nolink> and <separator> instead of plain "nolink" in special items

Traditionaly the Drupal interface uses <xxxx> in menu paths when referring to special items. That's the case with <front>. Some modules that provide special paths also work this ways (example: Menu First Child).

Using <xxxx> has some advantages:

• It makes clear and stand out that the menu item is special in some sense, not an ordinary path
• It avoid conflicts with existing paths (e.g. currently you cannot have a page at "/nolink" or "/separator")

So I think it would be good if the module used <xxxx> instead of plain xxxx.

Sorry for not providing a patch, but I'm just too busy now. I didn't look at the code yet, but I think that the change would be trivial. The biggest effort would be to create an upgrade procedure that change all e.g. "nolink" instances to "<nolink>" so that existing users can upgrade the module seamlessly.