typography

Comic book conventions are more fluid than we’re told

A while ago I attended Editors Canada’s webinar on editing comic books.

So on Sunday I went to TCAF (because I didn’t even realize TCAF was last weekend until a saw a high school friend’s Instagram post — he had a presentation on Friday) and flipped though some comic books. And what did I find out? Comic books, generally speaking, don’t really follow all the “rules” we were taught.

We were told that the “rules” wouldn’t apply to manga. But I didn’t see manga at TCAF. Comics from Europe do it differently. Comics in zines do it differently. Comics that are better described as experimental art do it differently. Even some locally produced ones, made right here in Toronto, do it differently. Some do it in a way that reminded me of how translated manga were typeset when I was small (i.e., they break even the seemingly unbreakable rule that text in English-language comics should look hand-lettered). Maybe half of all the comics I flipped through followed the “rules”; when I first found something that followed them I was actually surprised.

And you know what? Being a reader, seeing comic books that didn’t follow the “rules” didn’t bother me a single bit.

So what we were taught was a style. Apparently a fairly well-known style if what you’re aiming for is a mainstream North American aesthetic. But it’s still only a style. In the grand scheme of things, we’re talking about non-rules.

HTML q tag not compatible with North American typographic conventions

Just a few minutes ago I came to the conclusion that the q tag must not be rendered with quotation marks, and was surprised to find Stacey Cordoni’s article “Long Live the Q Tag” which came to the exact same conclusion, albeit for a different reason.

Anyway, I was editing my previous post and was looking at this:

…or he wouldn’t have suggested that I “get ready to feel unbored.”

The period being inside the quotation mark is an artefact of North American typographic rules. It’s purely visual (something I have been trying to emphasize every time this “rule” is mentioned in editorial circles), and you could argue it’s a case of kerning taken to the extreme. But logically it doesn’t make sense because what the person actually said was

Then get ready to feel unbored!

So the period doesn’t really belong. How do we mark up this fact? Of course we have the q tag, so imagine

…or he wouldn’t have suggested that I “<q>get ready to feel unbored</q>.”

which would have made perfect logical sense, and would mean “the quote doesn’t actually contain a period, but for presentation purposes the period is inside the quotes,” except it doesn’t work, because Chrome actually renders this as

…or he wouldn’t have suggested that I ““get ready to feel unbored”.”

Confused, I looked up the specification of the q tag and found that indeed, the q tag is “supposed” to be rendered with quote marks. Bummer…

Since I thought there was another tag that acts like q but rendered without quote marks, I tried to look for it, but came up empty-handed. Instead, I ran into Stacey Cordoni’s article.

The only logical way to solve the q tag problem is to make it, through CSS, render without quotation marks. But of course, if current versions of lynx really are rendering the quote marks, then this workaround doesn’t even work.

In retrospect, I realize I had come to the same conclusion years ago. The q tag is just badly designed: Being incompatible with typographic conventions aside (and useless as a workaround for illogical typographic conventions), if browsers implemented it to spec, then it’s not possible to add tags to an existing text and not mess up the punctuation.

I have no idea why the W3C designed the q tag the way it is. Didn’t they have any North American typographers—or even copy editors—on their committees?… Maybe everyone was European. Sigh.

Syndicate content