L10N Support in Default Theme

[Sewar]

See #3953 for details

I think it's a good idea. Makes sense that seeing it done in the default theme would encourage people to do it in their own themes.

• The beginning of comments-popup has a naked printf, without __
• There are some places (for example "« %link" and "%s at %s", %1$s to “%2$s”"), where we could use the new _c function (see #3687)
• Some more changes, differenet from i18n have passed through your diff: some stylesheet modifications (Arabic fonts), for example.
• It is nice that the strings are in a different domain--the theme authors will be more and more inspired and will gain some know-how :-)

Very good work, Sewar! Let's hope Matt wouldn't mind letting this in.

I have updated the patch, fixed the bug in comments-popup.php file, removed CSS related fixes (the Arabic fonts) and will add them in new ticket.

About the new _c function, it looks its development didn't finished yet.

The _c() function has already landed in subversion. Just that nbachiyski propose to put the context part behind the real translatable string, instead of the current status (before the real string).

Couple of places that looks curious to me:

1. Why some of the ‘ and ’ are replaced by ' ?
2. In sidebar.php, why inserting link breaks in between middle of certain sentences but not others?

Additional patch on top of Sewar's

I have uploaded additional stuff on top of Sewar's patch:

• Header image and color page now localizable
• Mark more strings translatable and minor fixes here and there

Relates to #4817

See ​http://comox.textdrive.com/pipermail/wp-polyglots/2007-August/001414.html