Grrrr
Well, they've finally gone and done it: Google has forced the new and "improved" Blogger composition interface on us. It's a little better than the first go-round, but it's still a step down from the old (i.e., functional) interface.
If you are a contributor, there are several quirks you'll have to get around. The most obvious is that there is no longer a "hybrid" HTML/composition mode. It means that if you compose in HTML as I do, you'll have to insert the codes for everything. For example, if you want a paragraph break such as this...
...you'll have to insert a double carriage return code. This is accomplished thus:
(less than sign)br(greater than sign)
(less than sign)br(greater than sign)
Replace the text in parentheses with the actual symbol. Oh, and to get those two lines of text on separate lines, you'll need a single carriage return code at the end of the first line. See, that's much easier to use, isn't it?
I really, intensely dislike people who insist on "fixing" things that aren't broken. In my experience, they're usually liberals... Oh, excuse me: "Progressives."
If you are a contributor, there are several quirks you'll have to get around. The most obvious is that there is no longer a "hybrid" HTML/composition mode. It means that if you compose in HTML as I do, you'll have to insert the codes for everything. For example, if you want a paragraph break such as this...
...you'll have to insert a double carriage return code. This is accomplished thus:
(less than sign)br(greater than sign)
(less than sign)br(greater than sign)
Replace the text in parentheses with the actual symbol. Oh, and to get those two lines of text on separate lines, you'll need a single carriage return code at the end of the first line. See, that's much easier to use, isn't it?
I really, intensely dislike people who insist on "fixing" things that aren't broken. In my experience, they're usually liberals... Oh, excuse me: "Progressives."
0 Comments:
Post a Comment
<< Home