(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

The recommendation should say whether the file extension is required or not. It would seem that it is not required.

The next revision of the recommendation should say how to specify an alt text.

The next revision should make clear whether it is possible to use an arbitrary URL for the image source as in [[some link|{{Image:http://example.org/flower}}]].

The choices of braces is a bit unfortunate, since it makes it a tiny bit harder than necessary to explain the use of braces. -- AlexSchroeder

This syntax obviously collides with the principle of I18N "Avoiding Text Tags". -- RadomirDopieralski, 2006-09-04

Well, if the name of the image is considered to be "Image:foobar.jpg", as is the case with Wikipedia, for example, then there is no collision. On a Finnish site it might be called "Kuva:foobar.jpg". This might or might not point to the same file.

My point is that the {{ } -syntax is enough. The whatever entity is referenced is then interpreted according to the rules of the wikiengine, and inserted into the page, if possible. We don't need a separate syntax for images; it's up to the wikiengine to determine how to insert the referenced object. And, since each wikiengine has its own way of referring to objects (e.g. by convention, Wikipedia places images in the Image: namespace; JSPWiki uses the file suffix to determine if an attachment is an image, and others use things like MIME types to determine the image-ness of an object) we should just treat the contents between the braces as an URI, which could be interpreted as relative within the wikiengine, or maybe as an absolute URL. It's up to the wikiengine vendor to guide the user to inserting the right text...

-- JanneJalkanen, 05-Sep-2006

Wow. The example was really misleading, because I didn't interpret it that way! Oddmuse will inline an image called foo using [[image:foo]] where the "image:" prefix is not part of the image name at all. I'll change the example. -- Alex

(removed my misguided proposal here) --ChuckSmith

Uhm, I think you're making the same mistake that I did: As Janne explains above, in your example, "Image:myimage.png" is the name of the image. "Image" just happens to be the namespace for images on Wikipedia. Thus, the two braces alone are an indication that something (such as an image) is to be inlined.

As for using double square brackets: For Oddmuse, I use [[image:myimage.png]] to inline images, so I wouldn't be against it. I'm just afraid of making many changes now. Was the image topic something that wasn't discussed at all at the workshop? If it was discussed, then I say we should not change the syntax. — AlexSchroeder

I've been wondering if this could be extended to allow inlining of a larger set of types, like [[myflash.swf]] for inlining a flash video. I think the main problem is determining the mime type of the thing being embedded, so can determine what XHTML needs to be generated. -- JaredWilliams

Add new attachment

Only authorized users are allowed to upload new attachments.

« This particular version was published on 06-Dez-2006 14:57 by 62.252.32.15.