Twenty Twelve: Author name is always displayed even on a single author blog

[iamtakashi]

Not like Twenty Ten and Twenty Eleven, Twenty Twelve displays author name on a single author blog.

Creating twentytwelve_entry_meta() in a child theme allows users to overide the output but I've heard a feedback pointing that it's overkill to get some privacy.

Like Twenty Ten and Twenty Eleven, wrapping each piece of the entry meta including prepositions such as "in", "on", and "by" provides flexibility but it certainly adds complexity.

Do you guys think Twenty Twelve also should hide author name on a single author blog like Twenty Ten and Twenty Eleven do? If so what's the best approach?

[nacin]

I wasn't really aware that hiding the name when there is only one author is a privacy thing. Makes sense, but I had always assumed it was to de-clutter the theme and not show redundant information, which for a single-author blog looks sterile or at least impersonal.

Also note that Twenty Eleven doesn't hide the HTML. It does this:

.single-author .entry-meta .by-author {
	display: none;
}

And .single-author is outputted using twentyeleven_body_classes().

[lancewillett]

Related to #21768 in terms of extra markup for hiding things with CSS.

[lancewillett]

I like this approach for single-user blogs — not hiding the HTML output so that an author can choose to display it they'd like.

@iamtakashi Want to cook up a patch for Twenty Twelve?

[iamtakashi]

Replying to lancewillett:

@iamtakashi Want to cook up a patch for Twenty Twelve?

Sure. I'll make a patch today.

[iamtakashi]

Hiding author name on a single-author blog with CSS.

[lancewillett]

In [21761]:

Twenty Twelve: hide author name on single author blogs, using is_multi_author() -- fixes #21759, props iamtakashi.

[nacin]

Not sure this is translatable as a full sentence. Twenty Eleven doesn't appear to be much better.

[westi]

Replying to lancewillett:

In [21761]:

Twenty Twelve: hide author name on single author blogs, using is_multi_author() -- fixes #21759, props iamtakashi.

Please can we not put the span in the translatable string.

In unnecessarily breaks all previous translations and is something that doesn't need translating.

It would be better to add the span around the replacement string before passing it to sprintf as this keeps the translation "simple"

[SergeyBiryukov]

Replying to westi:

It would be better to add the span around the replacement string before passing it to sprintf as this keeps the translation "simple"

21759.3.diff​ is an attempt to do that, but it wouldn't allow swapping %3$s and %4$s, which is bad.

Adding the span to $author alone doesn't seem feasible without adding new placeholders in this case, since it needs to include "by".

21759.4.diff​ adds new placeholders, not sure if it looks better than [21761].

[21761] is flexible enough, I guess I'd prefer to leave it as is.

[SergeyBiryukov]

Replying to nacin:

Not sure this is translatable as a full sentence. Twenty Eleven doesn't appear to be much better.

In Twenty Eleven, the string was much more sophisticated:
​http://core.trac.wordpress.org/browser/tags/3.4.1/wp-content/themes/twentyeleven/functions.php#L580

twentytwelve_entry_meta() looks better in that sense.

[lancewillett]

Replying to westi:

Please can we not put the span in the translatable string.
It would be better to add the span around the replacement string before passing it to sprintf as this keeps the translation "simple"

Can you suggest how you'd do it better with a patch? I'm not sure moving the span elements out is better because the " by " glue piece should be in the sentence, not in a replacement string.

[lancewillett]

Seems to me we're deciding between three options:

1. HTML in the translatable string
2. Splitting out the " by " English string into its own translation

3.

Westi said:

In unnecessarily breaks all previous translations and is something that doesn't need translating.

This theme is not yet live except for on WP.com, so changing the string isn't a huge deal in my opinion. After 1.0 is on Extend we'll freeze strings as much as possible.

The third option keeps it clean but adds a bunch of sprintf placeholders, which just looks terrible from a code bloat perspective.

[lancewillett]

Discussed all the options with SergeyBiryukov and Obenland in IRC today, and we all agreed that the way it is now is the most transparent.

Closing as fixed since it worksforus.