Typo in Twenty Ten

[zeo]

Minor typo in Twenty Ten's comment for author meta description. "description" mistakenly spelled as "decscription".

[nacin]

Hi zeo,
Since you're finding quite a bit of minor things in 2010, I'm going to leave this ticket open after commit and any additional patches can go here. Just include a comment in addition to the patch, to trigger a notification.

Thanks for your help.

[zeo]

Add trailing slash to home_url path in 2010's searchform.php form

[zeo]

Twenty Ten: Removes unnecesary edit_comment_link() space,  , parameter. Pingback use string (Edit), like comment.

[zeo]

For this patch: ​http://core.trac.wordpress.org/attachment/ticket/13198/twentyten-edit_comment_link-spacing-text.patch, is it appropriate to have same Edit text for both comment and pingback.

Also since everything is in one single line, I think the used of   is not needed. Since the default parameter for $before, $after is empty we don't to pass anything.

Feedback? Thoughts?

[zeo]

Twenty Ten, don't need   since it's in a single line. Normal spacing should work.

[zeo]

Twenty Ten: Use get_search_query() for search title.

[zeo]

Coding standard? Add some space to comment in file: loop.php

[ryan]

(In [14389]) Typo fixes. Props zeo. see #13198

[ryan]

(In [14391]) Coding standard cleanups. Props zeo. see #13198

[zeo]

Twenty Ten: Follow standard theme guideline, expose RSS. Add under sidebar Meta.

[zeo]

devs, if any of the patches above is rejected do tell.

[zeo]

Twenty Ten: Remove extra spacing in single.php

[zeo]

In reply to nacin:
"Two spaces in a row don't render as two. For that, you need to use at least one non-breaking space."

So then why 2 of this is different? Both are in the same row.

<?php edit_comment_link( __( '(Edit)', 'twentyten' ),'  ','' ); ?></div>

<?php edit_comment_link ( __('edit', 'twentyten'), '&nbsp;&nbsp;', '' ); ?></p>

I think rather than using "an empty" non-breaking space or space, add some span tag with class edit-link:

<?php edit_comment_link( __( '(Edit)', 'twentyten' ), ' <span class="edit-link">', '</span>' ); ?></div>

[zeo]

Twenty Ten: Add space before edit-link span tag in attachment.php.

[markmcwilliams]

I went on the hunt for a bit of everything, some coding standards, and some removal of white spaces at the end! I could have done a few things zeo pointed out already? :)

[markmcwilliams]

It would appear I might have covered a couple of patches zeo has already attached, so I guess we're both thinking along the same wavelengths!

[zeo]

markmcwilliams,

yeah, but the deeper i go more issue arise especially with this "coding standard" thingy etc. There's no specific guidelines AFAIK. space, whitespace, non-breaking space, tab, newline etc.

I issue a separate ticket #13243 but got closed.

[nacin]

(In [14433]) Twenty Ten spacing and string cleanups. props zeo, markmcwilliams. see #13198. Add a twentyten_credits filter, props nathanrice, fixes #12804. Also clean up the generator/credits string.

[nacin]

Ok.

I have gone through each individual patch and committed I think everything that I felt should be committed. Everything else I either missed, or deliberately skipped. (I skipped the RSS feed sidebar patch.)

In the future, please, as you find more things, add onto the patch. The most recent patch on the ticket ideally should have contained all previous fixes as well, at least per contributor.

Also, I removed   from continue reading, though the idea was not to wrap whitespace there. Ideally, we should be using white-space:nowrap. However, we did not use nbsp consistently (half "Continue reading" links didn't have them), so I simply removed them.

Please re-open if you find anything else like this before 3.0 is shipped (no need to spawn new tickets). Thanks for your help.

[dimadin]

My patch fixes several printf i18n issues. But there are some left in loop.php:

• "Tagged "
• "Posted in "
• comments_popup_link and plurals (see #13187 )

[dimadin]

Fixing some printf i18n issues

[nacin]

Yeah, we have some pretty ugly strings in Twenty Ten still.

The general guideline is manageable strings and as few HTML tags as possible. Going through the diff:

• attachment.php change is fine. (removing space)
• footer.php -- I don't like this. (See guidelines )
• single.php diff 1 -- this is really ugly either way. maybe Nikolay can advise.
• single.php diff 2 -- We may need to add context to that, such %s is defined as an author specifically.
• single.php diff 3 -- Looks okay. Don't think we need context here.

I'm going to assign this to Nikolay.

[dimadin]

• footer.php - well, I don't like current solution either since it's not so i18n friendly
• single.php diff 1 - we already have that code in loop.php, I just copied it (and tested, of course)

[nacin]

single.php -- Fair enough, it looked familiar. I let Nikolay know about this ticket so he can do a review of all Twenty Ten strings.

footer.php will have two relevant strings: "Semantic Personal Publishing Platform" and "Proudly powered by %s". I don't see how that's not i18n friendly, aside from not also adding contexts of "WordPress" to both of them (which I think is unnecessary).

[zeo]

About footer.php I think it's better to have:

Proudly powered by <a href="http://wordpress.org/" title="Semantic Personal Publishing Platform" rel="generator">WordPress</a>.

[zeo]

Miscellaneous. Whitespace, coding standard?, enhancement, i18n

[nbachiyski]

(In [14523]) I18n fixes in Twentyten footer. Props zeo, see #13198

[nbachiyski]

(In [14532]) Twentyten attachment.php copy and i18n fixes. Props dimadin and zeo. See #13198

• Removed the Post a comment link, since it's not present on any other single post page
• The text and link to the full-size image weren't clear and hard to i18n. Changed to Full size is 3872 × 2592 pixel, where the size is the link
• Whitespace fixes

[nbachiyski]

(In [14533]) Move vcard span out of the translatable string. See #13198

[nbachiyski]

(In [14535]) I18n fixes for header.php in Twentyten. Props zeo. See #13198

[doc_nl]

More string errors in loop.php:141,144 single.php:27,29,44,47

whitespaces before " which gives problems with l18n and glotpress

[nbachiyski]

(In [14541]) Clean up loop i18n. Props zeo, see #13198

• Take out tags from strings
• Extract two common and complicatd strings into functions
• Whitespace

[nbachiyski]

(In [14544]) Various twentyten i18n fixes. Props zeo, dimadin. Fixes #13198

[doc_nl]

Loop.php:122 stil has 'Tagged ' which breaks i18n

[nbachiyski]

(In [14552]) Do not cut the Tagged <tags> phrase in half. Fixes #13198

[zeo]

the get_template_part() block need to be indent or tab. My previous attachment.php patch contains the fix plus few other more that u left out.

For example, see twentyten category.php vs tag.php

And also: comments.php line 19.

Sorry that my patch is combined in one file and not clear in some part, nacin asked me to ;)

[zeo]

dev-feedback needed in [10910] see: ​http://core.trac.wordpress.org/attachment/ticket/10910/10910-cancel_comment_reply_link.patch and my comment.

[nacin]

(In [14688]) Remove unnecessary and out-of-place Twenty Ten filter. Also, tabs not spaces. see #13198.

[nacin]

I have looked at cancel_comment_reply_link. I don't see much wrong with small there honestly, it's rather semantic for that usage. I would not want to add arguments to a core function this late in the dev cycle, either. Let's stick with what we got.

Anything else we've missed here or anything else you find, please create a new patch. It's tough to fix based on line numbers referenced in comments or what we didn't commit in a previous patch, but really really easy to commit new patches.

[zeo]

Replying to nacin:

I don't see much wrong with small there honestly, it's rather semantic for that usage.

I usually can agree with you but not on this matter. It's semantically wrong. The small element spec has changed (HTML4 vs HTML5). Wrapping it inside h3 heading is the worst. This is how the document outline looks like:

<heading>Leave a Reply Cancel reply</heading>

Like I suggest in #icantremembertheticketno moved the cancel_comment_reply_link() outside heading. Put it somewhere like next to Submit button. A good example would be like the placing of Discard button used in Google Groups.

If can't make it in 3.0, will open again for discussion in future release.

[zeo]

Don't need to escape 2 times? Invalid parameter. see: esc_html($text)

[ryan]

[14790]

[ryan]

Resolving this ticket as fixed. Please open new tickets for additional issues.

[nacin]

(In [14791]) Better escaping in 2010 attachment.php. fixes #13198, see [14789].

[zeo]

Add some meta-nav love. Wrap the left/rightward arrow entity with span to match elsewhere.

[nacin]

(In [14936]) Add textdomain. see #13198.