alt Attribute > Caption
Would it be possible for a future release of to keep the alt attribute as an alt attribute (or perhaps make it an option in Preferences)?
I ask because I'm a technical writer and all of my screenshots are on their own line, but I don't want captions, just the alt attribute.
I'm not sure what the best way is to tackle this at the moment, so if anyone has suggestions, I'm excited to see them! For now, I think I'll add the alt text below the image and then cut it and paste into the HTML code with a little TextExpander magic. I'm not smart enough (yet?) to figure out how to use regex to find and delete all instances of <figure> … </figure> and <figcaption> … </figcaption> without removing the <img src= …> in between.
Please consider this a vote for your "alternative plan … to use what currently generates the title attribute to instead generate the alt attribute in all instances…."
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Fletcher on 14 May, 2019 08:11 PM
The easiest workaround at the moment is to simply convert the figure into a regular image by including "something else" in the paragraph, such as a non-breaking space.


Instead of ` ` you can also use `\ ` to result in same thing.
Thanks,
Fletcher
--
Fletcher T. Penney
Manager, Founder
MultiMarkdown Software, LLC
[email blocked]
2 Posted by sylvaticus on 15 May, 2019 05:04 PM
Ahhh…I had a whole bunch of stupid text here (now deleted) because like an idiot, I only read what you wrote and didn't try it out.
So, adding at the end of the line worked as expected.
When I tried adding a backslash + space, it didn't: a backslash appeared beneath my image. But when I typed just the backslash, a weird character appeared (don't know what to call it, but it looks like backwards L on its side.
Doing that worked too, and typing "\" is must faster than typing " ".
Thank you!! That's a way better workaround!!
Support Staff 3 Posted by Fletcher on 15 May, 2019 05:10 PM
Glad it worked, and I do recognize this is a workaround and not an ideal solution.
But one thing at a time, right?
:)
Fletcher
--
Fletcher T. Penney
Manager, Founder
MultiMarkdown Software, LLC
[email blocked]
4 Posted by sylvaticus on 15 May, 2019 05:14 PM
NO NO!!! I'm thrilled at the workaround!
As a wise man said, "All you can do is all you can do."
This workaround makes it SO much easier than what I was going to do, and I completely agree with the choices you made for MultiMarkdown 3!
As far as I'm concerned, the workaround is good enough that I have no problem waiting for this to come off the back burner in the distant future. I suspect there could be formatting challenges if space is tight (tables come to mind), but as you say, "One thing at a time."
I have another suggestion if it's not too awful. I make that after our team stand up. :-)
THANK YOU!
Fletcher closed this discussion on 26 Jun, 2019 10:59 PM.