Wowfunhappy wrote:I have long wished that type styles operated similarly to capitalization. Not in terms of data storage under the hood—I'm not suggesting that bold letters should be an entirely different unicode sequence—but in terms of... if caps lock isn't enabled, and I'm not holding down shift, my word processor will never decide to make my text uppercase.
In other words, ⌘B should work like caps lock, except for bold characters instead of uppercase characters. When my bold cursor is enabled, anything I type becomes bold, and vise versa when bold is disabled. My computer should never make the switch for me—it only ever causes problems.
As far back as I remember, ⌘B to start and end bold typing is how this works. However, if you click inside an already-bold section and start typing, your new typing will also be bold. This comic's problem: If a bold space is left, and you click "inside" the bold tag, your new text is bold. This is precisely how early WYSIWYG HTML editors worked - they didn't delete the start and end tags (for bold, italic, underline) when the text inside was deleted. You had to include a tag in the selection to get both deleted, and how could you tell unless you were editing rich text while also viewing source? If not, you could potentially start typing inside an existing tag and get unexpected formatting.
Randall's fear is not unfounded.
My habits, I think, solve the problem. If I select a word, mark bold, decide I don't like it, I ⌘Z (undo). If later I need to remove bold, I select surrounding text, mark all bold and immediately mark unbold.