[crossfire] Feature proposition: [img] tag

[Nicolas Weeger]

>   Fair enough.  I think my point may be more that the spec (for lack of
> better work) should be aware we may want to add extra specifiers, and while
> they client has not requirement to handle them (since we don't know what
> they are), it shouldn't suddenly break if they show up.
>
>   It could otherwise be a real pain if we decide we want to add something
> like [img popup=1], and the client is only looking for [img] and suddenly
> doesn't work right.
>
>   So in that case, an old client would still recognize that as a valid img
> tag - it wouldn't know what that popup=1 thing means, but would display the
> image just like it always had.

Have clients find "[img" then the next "]" and it'll be ok :)


Nicolas
-- 
http://nicolas.weeger.org [Petit site d'images, de textes, de code, bref de 
l'aléatoire !]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mailman.metalforge.org/pipermail/crossfire/attachments/20091128/67b826f8/attachment.pgp