Michael Eriksson's Blog

A Swede in Germany

Wordpress and more post-by-email distortions

with one comment

I have already written about how WordPress distorts quotation marks in “post by email” texts, and why this is idiotic. However, these are not the only artificial problems caused by WordPress. For instance, I have long noticed that line-breaks are often added or removed compared to the display of my HTML original, e.g. in the list entries in my recent blogroll update. Looking at the actual HTML code, I can see that WordPress has simply removed closing paragraph-tags (p) before a closing-listentry tag (li), which is very poor style. Not only does the result indisputably display differently* in my browser, but good code does not rely on implicit closures of that kind.

*Unlike in my original, very preliminary observations, when I first experimented with post-by-email. Then, I had mainly (or exclusively?) seen a removal of tags around the asterisks that I use for footnotes, which indeed did not seem to affect display. (At least in my browser and with the fonts used—there is always a risk that the situation is different in other circumstances.)

Another issue is that I write “Wordpress” (as I attempt here; let us see whether it is changed) with a small “p”, but that this somehow always turns out as “WordPress” (with a capital “P”). WordPress might have its own preferred spelling, but it has no right to impose it on me, especially since the word could conceivably refer to something else in some context (possibly, within a book by Jasper Fforde?). Certainly, there are a few* people who disapprove strongly of such unconventional casing, and imposing something that it disapproves of in such a manner would be doubly unethical—with strong parallels to a recent text on distortion of literary works. Or what about a text (e.g. this one) discussing the spelling, which is now unable to quote the word in variant forms? Or what about an attempt to quote something that someone else said, which simply did not use the preferred-by-Wordpress spelling?

*I am not one of them, but I have sufficiently strong opinions in other areas that I can sympathize and put myself in their shoes in this scenario.

Moreover: What guarantees do we have that no more insidious changes take place (or later will take place)? What if someone decides that words like “nigger” and “fuck” are to be auto-censored*, that all spelling be converted to U.S. conventions to suit the broadest spectrum of readers, or that all occurrences of “he” be automatically replaced by “they” to ensure PC conformity? Also note that there is no notification whatsoever as to what changes have been made, which leaves the blogger the choice between blind trust and entirely disproportionate checks and/or manual corrections.

*In the context of forums, such auto-censorship is relatively common, and often applied in an utterly idiotic manner. For instance, words like “analyst” can be turned into “****yst”, because the filters do not differ between a stand-alone “anal” and “anal” as part of a larger word with an entirely different meaning. (The question aside, whether “anal” is worthy of censorship in any context.) On the other hand, they are typically foiled by variations like “f*ck” or “F-U-C-K”, the censorship of which would be much less unreasonable (but still disputable!) than a plain-text “anal”.

This is all the more annoying, since one of the reasons that I use post-by-email is to avoid the extreme fuck-ups that WordPress causes through its GUI*.

*Cf. e.g. the current state of a text dealing with “Google’s ideological echo chamber”, where a post-by-email malfunction forced me to correct the text in the GUI—with very weird layout results. (Actually, this might be yet another example of consistent idiocy: I used the HR-tag, which has over-time been redefined from meaning “horizontal ruler” to “general content separator”. Because my original posting attempt was cut off exactly where the HR-tag was, I suspect that WordPress has imposed an even further going private semantic of “end of post”, which would yet again be an inexcusable meddling contrary to reasonable assumptions. However, I have made no further experiments with said tag in conjuncture with WordPress.)

The only reasonable solution is to respect the actual words and code of the blogger.

Disclaimer:
In order to avoid additional complications through possible WordPress interference, some of the above formulations are less explicit than they would be in another context, e.g. in that I speak of “paragraph-tags (p)” where I would normally have included an explicit tag example.

Advertisements

Written by michaeleriksson

January 7, 2019 at 10:31 pm

One Response

Subscribe to comments with RSS.

  1. […] at the actual results of the WordPress-spelling issue just mentioned, it seems that all-but-one occurrence of “Wordpress” were indeed turned into […]


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s