decoration
Spiekerblog
 

09. 12. 08

WordPress

As even the occa­sional vis­i­tor to these pages will notice, I have switched to Word­Press. We use that pro­gramme at Spiek­er­man­nPart­ners, so I could enlist the help of Mar­cus Scheller who imported most of the old con­tent and built the site. Some of the for­mat­ting needs a pol­ish, and all the down­loads have dis­ap­peared into the ether for now. The ether, in this case, is our server, so it only (!) requires me to find the stuff and re-load it.

As it has taken more than half a year to get this far, don’t hold your breath. I am hop­ing that the inevitable break at the end of the year will allow me to sort this out and also learn more about Word­Press features.

It is still the only blog I know that gets writ­ten by one per­son in two lan­guages. Or is it?

 

SpiekermannPartners

17 Responses to “WordPress”:


 

1

Con­grat­u­la­tions with the move, I hope that it will inspire you to write “what­ever comes to your mind”, as you promised in a older post.

 

2

cool change!
wp is great…

i added a rss feed to my face­book page of your 2 lan­guage blog
http://es-la.facebook.com/pages/USTED/34030801509

span­ish could be the 3rd : p

wp is really easy to embed pic­tures via picasa and videos via youtube,
and of course, pub­li­ca­tions via issuu…
there are many plug­gins for whatever…

good luck and keep shar­ing (sorry for my english)

best

felipe

 

3

It’s not so easy to adapt more than one lan­guage to wp. I often use plu­gin called Gengo (like here http://www.minimo.fi)

The blog looks nice, good job!

- pasi

 

4

Lovely, Mr. Spiekermann.

Some­how we con­sis­tently enter the topic of multi-lingual cms and blog sys­tems and would love to some­how get all of our results onto one page for peo­ple to use as a ref­er­en­tial resource. Per­haps that’ll hap­pen, but I’m prob­a­bly not qual­i­fied to write such a post.

A+ for effort, though!

 

5

I usu­ally don

 

6

i hope this will come out like con­struc­tive crit­i­cism ‚it is cer­tainly meant
like that.

for starters: minor html warn­ing: the meta tags are not closed prop­erly
(for this doctype).

then, the style sheet falls apart in opera…
not really a require­ment per se, it just shows that it is not robust enough…

and finally, i am some­what embarassed and sur­prised to ask about the
basic(?) typo­graph­i­cal “mis­takes” in the arti­cles, like the lack of white­space
around pic­tures embed­ded in arti­cles (e.g. Unit Rounded), the lack of “proper” sub­head­ings (e.g. the Mr. Univers arti­cle), and while lament­ing the loss of
the apos­tro­phe (in San Fran­cisco walks, 3.), some arti­cles use one quo­ta­tion
mark both for open­ing and clos­ing… also while the indented parag­prahs
work really well on paper, i think they trans­late poorly to the screen (but this is
get­ting into the ter­ri­tory of “mat­ter of taste” i guess).

it is one thing to read blogs, arti­cles from all fields of life where peo­ple igno­rant
of typog­ra­phy use inverted apos­tro­phes in place of apostrophe’s and reg­u­larly
com­mit other typo­graph­i­cal crimes, but i feel a kind of despair when com­ing
to such a professional’s blog and see sim­i­lar mis­takes. i am sorry…

please for­give an old TeX user the imper­ti­nence to come up with this…

 

7

sigh, this com­ment edit­ing box is hell for longer texts..
please ignore the white­space in front of the comma and the incor­rect line breaks…

 

8

Well, you’ve caught some of the obvi­ous short­com­ings.
1. I ”sim­ply“ moved the old con­tent over to WP from MT, and a lot of con­tent and pic­tures just didn’t fit. And my friend Mar­cus, who wrote the CSS for the new blog, gave up half way through, so a lot of things are not fin­ished while I don’t dare touch his work.
2. Nobody proof-reads this, and I have to write every­thing in two lan­guages. So there are typos and the occa­sional wrong apos­tro­phe because I get mixed up between Ger­man and US usage.
3. Space around pic­tures is an issue that needs address­ing in the CSS. It will never be totally even, but should be more. For now, I insert a line­space in new posts, but will not go back over all the old stuff.
4. What does ”proper“ sub­head­ings mean? The Univers arti­cle had exactly those sub­heads, and I sim­ply brought them over into the blog. They are two lev­els of hier­ar­chy above the text – all that is needed.
5. Eng­lish is not my first lan­guage and some of my typo­graphic styles are delib­er­ately Euro­pean.
6. Thank you for your very con­struc­tive con­tri­bu­tion. As you say, some of it is a mat­ter of taste, but some of it needs fixing.

 

9

PS:
which arti­cle uses one quo­ta­tion mark for open­ing and clos­ing? Per­haps that is intentional?

 

10

if you get back to your clients this fast, i’d like to work with you :] amazing.

btw i am also from europe so i am famil­iar with some of the more
well known euro­pean typo­graphic con­ven­tions, that was not my
issue at all, no prob­lems there as far as i can tell :]

the mis­matched quo­ta­tion mark is also in the Mr. Univers arti­cle:
”that’s not bad, but I would have done it dif­fer­ently”, but it seems
like i have found an excep­tion rather than the rule. mea culpa.

the sub­head­ings (in Mr. Univers) are sim­ply short parag­prahs in bold…
i don’t know, per­haps that was the inten­tion… i was thought by my
excel­lent teach­ers to break up arti­cles seman­ti­cally using head­ers
(h2 — h6) and unless part of some artis­tic exper­i­ment use styl­is­tic
and typo­graphic devices to sep­a­rate from the nor­mal flow of the text
(dif­fer­ent font face and white­space). but most of the entries in this
blog are really short so it’s not really an issue i guess…

(it would be nice to have a pre­view but­ton for the com­ments, but
i think i have used up all my con­tri­bu­tion points for now :-)

thank you for your attention.

 

11

the sub­head­ings (in Mr. Univers) are sim­ply short parag­prahs in bold…

No, they’re not. They are incom­plete sen­tences, with­out a full point at the end. That does not qual­ify as a para­graph. Or maybe you’re look­ing at a dif­fer­ent stylesheet than the one I see in Safari and Firefox.

 

12

sorry, i should have been more explicit what para­graph i meant: in html context.

in the html code, the “sub-headings” are made of parag­prahs,
thus seman­ti­cally iden­ti­cal to the “nor­mal text” of the article…

(i am sorry, with­out pre­view i have no idea how this exam­ple looks)

Adrian as a col­league

 

13

oh, the com­ments do not fil­ter out html, that can be even dan­ger­ous…
you might want to con­sider turn­ing fil­ter­ing on…

here is the same but replaced the angled brack­ets with [ ]

[p][strong]Adrian as a colleague[/strong][/p]

 

14

Seman­ti­cally yes, but visu­ally not. They are above the text, indented and bold. That qual­i­fies as suf­fi­cient dis­tinc­tion as head­ings to the paras they preceed.

 

15

oops: pre­cede.
Time for bed (1am)

 

16

well, i was thought not to indent headings :]

but i dont like where this is going, me lec­tur­ing a well respected pro­fes­sional,
that was never my inten­tion. who am i to talk anyway :]

sorry for the noise.

 

17

There are hardly any ”never“ rules. I have been writ­ing books about rules for long enough now that I can afford to break some of them. You are not sup­posed to indent the first line of a new chap­ter (i.e. the first para in that chap­ter or sec­tion), only the paras fol­low­ing in order to dis­tin­guish the begin­ning of a new sec­tion or chapter.

I think that indent­ing the sub­heads and the first lines makes a nice rhythm with­out too much noise. A line­space would be too dis­rup­tive with such short paras and rel­a­tively long lines. Indents may not be web-like, but they work well to indi­cate a new para. Why invent new con­ven­tions when the old ones work well?

 






 

Leave a Reply

 

© Erik Spiekermann | Spiekerblog is proudly powered by WordPress.