• Without modifying the source code, it’d be cool if we could specify between <abbr> and <acronym>

    <abbr> is shorter and looking at the current HTML 5 spec, it has no <acronym>

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • I’ve been thinking about this for a while but I’m not convinced that the average user will understand the distinction between <abbr> and <acronym>, or will care enough about semantic HTML to use it.

    However I’m still thinking about it.

    Personally, using the Acronym plugin myself, I don’t think there needs to be a distinction made. The only difference is in the code, < abbr > and < acronym > act exactly the same way when you look at it on the page that is displayed, so there’s no use to do so.

    However, I would REALLY like to see a piece that will allow for import/export for a list of acronyms in the plugin. I’ve got a HUGE file that has all the acronyms I have come across that I’d love to just import into the database, instead of entering them manually for each and every one.

    Also I don’t know how this is addressed, but how are multiple meanings of the same acronym handled?

    Thread Starter Steven Vachon

    (@prometh)

    <abbr> and <acronym> may be read differently with screen readers. I haven’t tested, though.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: Acronyms] <abbr> instead of <acronym>’ is closed to new replies.