On Thu, Jun 22, 2006 at 11:37:16AM -0700, Brion Vibber wrote:
Chad Perrin wrote:
Would requiring spaces on either side of the
double dash before
converting it into an emdash improve the parsing behavior any?
No; the conversion simply needs to be smart enough not to damage markup, but to
instead operate only in plain text areas. (Additionally it probably ought to
exclude itself from areas like <pre>, <tt>, and <code>.)
That's a shame. It seemed like such a good idea, too. . . .
It
should at least solve the image name problem, since spaces in image
names should (in my honest opinion) be considered a no-no in any case.
Then again, I'm not in charge, of course.
On the contrary, spaces are highly recommended in image names. Names should be
descriptive; "Lake McFoobar viewed from Mount Baz lookout point.jpg" is
strongly
preferred to, say, "DSC000247.JPG".
Note that images' names are going to be more and more decoupled from their
physical filenames in the future; the file extension won't have to be maintained
as part of the wiki name for it and it will be possible to change names after
uploading.
Ahh, right, I'd forgotten the discussion about decoupling displayed
image names from image filenames. Mea culpa.
--
CCD CopyWrite Chad Perrin [
http://ccd.apotheon.org ]
This sig for rent: a Signify v1.14 production from
http://www.debian.org/