> Then to display the tags on a page, you would use something like:
>
> [(list "{info.tags::{p}}" fmt="...")]
>
> This may actually be easier to manage than the current tags
> recipe--all using core features. Another great application for the
> soon coming info capabilities. Then we would only need a tags function
> which scanned the tags page, and returned every page with a given tag
> in the value. Just a simple plugin for the info module. Probably far
> faster than searching the index. Yes, many advantages...
Eye opening to wait the new release.
> No, it would be good to have in general. I'm wondering what have to
> be done to get our current tags script to work with UTF... And looking
> quickly at the links markup function, it may not be that hard. If you
> care to do a bit of snooping around and tell me what you find, I could
> give you a few hints on where to look...
Not yet test the method here, however, current tags plugin using a
virtual page name of 'tag.*' to generate backlink list. It's an
elegant design. But it is no way to allow utf-8 because it use page
name as tag, am I right? Or I had miss something?
Cheers,
linly
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
