2008/8/26 Linly <[EMAIL PROTECTED]>:
>
> Wow Wow Wow. So many interesting improvements. I'm esp waiting to use
> the change of pagedata plugin moving into core. In this way it almost
> can satisfy any data, info request. Great.
>
> Btw, is it possible to set multi-value to a data field? Say, for the
> tag usage like:
>
> Category: History,ChildrenBooks,PictureBook ...
Yes, except it would probably be (on page info.tags):
some.book.page: History,ChildrenBooks,PictureBook
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...
> I know there is a tags plugin already but it can not set utf-8
> values. :( So I have to look for other solution to set utf-8 tags. And
> for this purpose the datasearch should be capable to find one or two
> or all of the values in a multi-value data field.
>
> Sorry this must be no use to English users, but I think even European
> users would like.
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...
First, go to markups.php and try adding the u/U to line 45
MarkUp('links', 'links', '/\[\[(.*?)\]\]/eu', 'BOLTMlinks("$1")'); // [[ ]]
That should allow you to put utf tags in, perhaps... Then to test
that the markup is being processed, change line 438 to something like
this (temporarily):
if (BOLTconfig('BOLTtags') == 'true' && substr($x, 0, 4) ==
'tag.')
return "Hey it works!";
If this works then we only need to make sure the indexing is working
properly for utf... But let's see if we can get this far first. But
then again, the more I think about it, using the new info capabilities
makes the most sense, as it will be a fast easy way to store "info"
about a page. I always kind of thought the use of invisible links was
a bit strange.
Cheers,
Dan
P.S. I checked the php docs. It is a lower-case u for UTF-8. The
capital U is something different.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
