Tag Archives: wordpress

Typing The Next Great Literary Epic (Or Other Long Work) Using Nothing But A Cell Phone


Because thumbs, too, can receive repetitive motion injuries. That, and legendary depictions of heroes of yore typically aren’t made in ASCII-art.

(Sent from my phone using the Android WordPress app. Yes, I’m a bit of a hypocrite. It happens.)

Let This Extraordinarily Long-Titled Thing Die

Advertisements

Multiple Interpretations Of WordPress.com’s Thumbs Rating System


See those cute little disembodied hands floating above this post? Well, they’re interactive! They’re used in “rating” a post. Plus, their red and green sleeves look just darling with my background.

Anyway, I’ve recently found myself confused as to what they rate, exactly, when it comes to a blog like this. Should I take a “thumbs down” rating as a traditional insult, like “Boo, this content/writing sucks”, or should I see it as a compliment, as in “Yeah, I hate this specific thing or ideal too!”.

Perhaps I’m overthinking it. I could abolish the rating system from the site, but I like to let readers have the ability to judge a post without necessarily leaving a comment. I could switch to a 5-star system, but, I think that’d be all I get – namely, I couldn’t change the stars into cuter, more death-oriented icons.

With that in mind, the juxtaposed appendages will stay in place for now – I’ll just have no idea how to interpret them.

Let Multiple Interpretations Of WordPress.com’s Thumbs Rating System Die

How WordPress.com’s Visual Interface Handles Bold


https://i1.wp.com/rlv.zcache.com/html_shirt-p235568310957990952qm73_400.jpgRemember, I’m cataloging annoyances. Sometimes they’re just very specific annoyances.

Anyway, this blog is generously provided to me by WordPress.com. In order to make blog posts, one can use a WYSIWYG (pronounced “wizzy-wig”) editor in order to publish blog posts. Sounds easy to use in theory, right?

Well, WordPress.com also makes you use a theme that you must pre-select upon blog creation. You can purchase an upgrade to change the CSS, but that’s not what I’m here for at the moment. Anyway, each theme handles headers, default text color, and other HTML things a little differently. And therein lies the problem.

Now, when I want something bolded in my posts, I want it to be the color that I select for it, such as white. So, when I click the little “B” in the editor, I assume it’ll do what I want it to; after all, it looks fine in the editor.

However, doing so will produce a result like this. Well, that’s not white, now is it? It should look like this. The reason this happens is due to how WordPress.com interprets “Bold”. It uses the HTML tags <strong> and </strong>, rather than <b> and </b>, causing the strange coloration.

That may not sound like much of a problem, but when I edit my posts using that interface rather than ScribeFire, I have to manually change all instances of <strong> to <b>. This is a pain for long articles.

Then again, there is a little smiley face at the very very bottom of the theme, so that mitigates this a bit.

Let How WordPress.com’s Visual Interface Handles Bold Die

Photo Credits: Here