Grouping by namespaces to make it compatible with translation

[techana]

This is a good plugin, but it a lacks an essential feature in my opinion! The auto-generated list should have the ability to group or sort pages by their namespaces.

In my wiki, each page has a number of translations. A page shares the same tags with other pages in different languages. When a reader clicks on a tag in one page, the pagelist plugin lists all pages having that tag, but without distinction between their namespaces! It would be better to group the pages using the topmost namespace, i.e.: en, it, de, etc. In case this is too much to ask, then at least add the ability to show namespaces for the listed pages, e.g.: en:nsp1:page1, de:nsp1:page1, etc., and sort them accordingly.

Thank you!

[techana]

As a temporary fix, I edited the script "helper.php" and added the following to line #488 (for the version at the time of this writing):

// produce output
- $content = '<a href="' . wl($id) ...
+ $content = str_replace(":", " : ", substr($id, 0, strrpos($id, ":") + 1)) . '<a href="' . wl($id) ...

Note that the function str_replace() is not required here. It is only used to add spaces around the colons; as this would make it easier to read namespace paths.

[fiwswe]

No comment on the usefulness or correct implementation of your feature request.

But it would be better to use CSS for formatting. So instead of replacing ':'with ' : ' you could replace it with something like <span class="pathsep">:</span> and then define CSS for e.g. .pathsep {margin-left: .4em;margin-right: .4em;} even better, don't include the : in the replacement at all. Then CSS could be used to show a → or a ▸ for example:

$content = str_replace(':', '<span class="pathsep"></span>', …

.pathsep {
    margin-left: .4em;
    margin-right: .4em;
}
.pathsep:before {
    content: "▸";
}

[techana]

Thank you for the suggestion. I'm aware that dokuwiki has the option to use slashes instead of colons for namespaces separation. So, hardcoding the colons in the code is not a good practice.

[Klap-in]

Could you give an example of the syntax you use for creating a list (with the tag plugin?)?
What kind of results do you have? So probably it helps me to describe the page/namespaces structure, or make a screenshot?