On Mon, Sep 8, 2008 at 6:35 PM, alinome.net <[EMAIL PROTECTED]> wrote:
>
>> Does PHP have a way to scan the graphic file and generate these numbers or
>> something? It might be nice to fix this. I like pages that load this way
>> better.
>
> Yes, it's easy:
> http://es2.php.net/manual/en/function.getimagesize.php
Good to know. I'll look into it.
> could
> be cleaned by the function (or produce an error message).
Yes, that was my only point, it needs to be cleaned. The same thing
would be possible in [^ ^] if it weren't cleaned.
>> > {{dir/image_file|alt_text|parameters}}
>> It looks nice!
>
> I think it's better the sintax to be as consistent as possible. Easier
> for the
> users. Images and files are very similar to links, so they can share
> the
> syntax. The most used parameters in both cases are the link text and
> the alt
> text, that's why they are specified wiki style, by position. Alt texts
> are very
> important for usability. It's easier and more "wikily" to type
> {{photo.jpg|Alien}} than {{photo.jpg alt=Alien}}, and also it's easier
> {{films/photo.jpg|Alien}} than {{photo.jpg dir=films alt=Alien}}...
I agree this has appeal. I'll think about it some... Remember the
upload markup is not only for images, but any kind of upload. And some
won't have an alt parameter. Like {{boltwire2.32.zip}}. And I REALLY
don't like break sites all over BoltWire land by making a majore core
change like this. But, it's definitely a nice option for a WikiCreole
plugin, and it might make it into core eventually.
> the image parameters. I had tried to use {vars} in links and it didn't
> work:
>
> $BOLTvar['$en'] = '<span lang="en" xml:lang="en">';
> $BOLTvar['$en_end'] = '</span>';
>
> [[anypage|some words in other language and {en}these words in
> English{en_end}]]
>
> I get the <span> rendered as text :-( I have not searched why yet.
> That's why I
> thought an image with parameters wouldn't work inside a link.
Actually the fact you are getting <span> shows the variables are being
substituted. Evidently the < is being escaped in the link output.
Probably necessary for various reasons... I've noticed the <span> tag
breaks a few things here and there. Perhaps an extra line break is
being inserted or something. I'm not sure.
>> The problem with the wiki-creole syntax is BoltWire's extensive use of
>> variables like this {id}. As these are processed before links
>> {{image}} would turn into {} after the {image} markup failed to find a
>
> I didn't think about that! Oops. I'll see what can be done. Perhaps
> just to
> ignore "variables" whose name inside the outer {} is {something}. By
> the way,
> there's more { and } in another WikiCreole markup:
One option is to process {{}} before {} and then use a function to
translate that into [^ ^] for BoltWire's handling later, at the
appropriate time. It might work pretty easy. Essentially it lets
BoltWire keep doing all the heavy lifting--you just translate one
syntax to the other. And sites using [^ ^] will continue to work as
well.
> {{{ text not rendered by the wiki engine }}}
This will be less trouble as text should be probably be escaped before
variables are processed anyway.
I'm really looking forward to a quality WikiCreole plugin. If we can
get one, I'd be inclined to add it to core with a simple configuration
option to turn it on/off. Would be cool.
Cheers,
Dan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
