I have to keep working on this "keyword" idea, see where it goes, and maybe
write a plugin or something.
About the counting issue, I found another way. It's incredible how powerful
Boltwire is. Thanks again, by the way, for this great tool! And thank you
for the inpage modification.
I also propose to provide more useful information in the messages, like in
the following cases:
- Replace *if ($fmt == '') return 'Output format not found.';* by* if ($fmt
== '') return "Output format $fmt not found.";*
- Replace *if ($template == '') return 'Output template not found.';* by *if
($template == '') return 'Output template $template not found.';*
- Replace *if ($myrule == '') return 'Index rule not found';* by *if
($myrule == '') return 'Index rule $myrule not found*'*;*
- Replace *if (! function_exists($func)) return 'Mode not found.';* by* if
(! function_exists($func)) return 'Mode $mode not found.';*
- Replace *exit("Script not found...");* by *exit("Script $script not
found...");*
Cheers,
Tiffany
Le lundi 3 novembre 2014 21:14:42 UTC+1, Dan a écrit :
>
> Here's a few quick responses:
>
> First of all, English is a tricky language where you an have verbs and
>> nouns spelled exactly the same way. This is giving me headaches while
>> translating my website into French, and with the possibility to also use
>> the translated version of command, it is getting even worse. I tend to
>> translate commands and button texts as verbs, and action names or page
>> titles as nouns ("change" becomes something like "recent changes","create"
>> something like "new page", "register" like "registration" and so on).
>>
>
> Makes sense. Not sure this needs to be in the core, but possibly...
>
>
>> Even if you choose not to keep my separation of things, I think it would
>> be nice to introduce a list of translatable "keywords" in addition to
>> "messages" and regular "language" strings. Anything not found in the
>> "keywords" file would be look for in the "language" file.
>>
>
> Not sure what you mean. Right now, site.language.fr is mostly key words.
> You can add message strings to it if you want, but I'm mostly worried about
> buttons and headers, etc.
>
>
>> Then, I also wanted to suggest some grouping of the "actions" appearing
>> in the "top" zone by default, like "Site actions", "Page actions",
>> "Member/Account actions"; and why not a "quicklinks" system var that can
>> also appear either in the top zone or in the side one. But I can also write
>> a recipe for this.
>>
>
> I think these are easy enough to customize for the user. A recipe would be
> great.
>
>
>> Also, and please forgive me if I missed this on Boltwire's website, I
>> would love to be able to count the number of field parts using the info
>> command (and I would be even better if the info command worked also for
>> data fields, but I think this is planned for later).
>>
>
> So if you have on a page field: one | two | three, you want to return 3
> for the number of parts? You could try this extension:
>
> function BOLTinfoParts($info, $args, $page) {
> return count(explode(' | ', $info[$args[2]]));
> }
>
> then put [(info parts fieldname)]
>
> Curious what you are using this for? Is it something that could be
> commonly used? Not sure I see the value of putting this in the core.
>
>
>> And last, but not least, it would be great if the search "inpage"
>> parameter also worked for page titles, which are sometimes included in the
>> header and not in the page in itself.
>>
>
> I just modified the inpage conditional to this:
>
> function BOLTCinpage($args='') {
> global $pageLink, $BOLTid;
> $page = BOLTinit($pageLink, $args[1], $args['page']);
> $find = BOLTinit($BOLTid, $args[2], $args['find']);
> if ($args['data'] == 'true') $data = 'data';
> $content = BOLTloadpage($page, '', $data);
> if ($args['case'] == 'false') {
> $content = strtolower($content);
> $find = strtolower($find);
> }
> if (strpos($content, $find) !== false) return true;
> $find2 = BOLTurl2utf($find);
> if (strpos($content, $find2) !== false) return true;
> }
>
> So if you do [if inpage find=term data=true] it will scan for your phrase
> in either the page content or any data var. It doesn't specifically point
> out titles but it was easier than giving some option for specifying which
> fields to include for indexing.
>
> Also remember, if you are using an index, you can include the data the
> same way:
>
> forum: mode=text group=forum data=true...
>
> Cheers,
> Dan
>
>
--
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/boltwire.
For more options, visit https://groups.google.com/d/optout.
