Wedge

Regarding the latest few commits... Wouldn't it make sense to have a function like, 'complex_string', whose purpose would be to do the common string replacements? (boardurl, scripturl...)
It wouldn't be as fast, though. But from the moment you implemented {variables}, I suppose it mattered less than having a non-dynamic list of text strings.I totally forgot that this was recent, indeed...
I don't even know why people would need to translate this, meh.

Oh, and so... What about this %Y problem?
We *could* do it in a complicated way, such as {, %Y} where everything between {} would be removed if %Y is empty, but we'd need to apply this to all occurrences, which isn't cool... (Well, of course we could simply integrate the removal in the same code that gets rid of %Y in the first place.)

$show_today = str_replace(' %Y', '', $user_info['time_format']);

->

$show_today = preg_replace('~,? %Y~', '', $user_info['time_format']);
or
$show_today = str_replace(array(', %Y', ' %Y'), '', $user_info['time_format']);

(The second one is faster. strtr() has similar performance, can be 10%-20% faster or slower, totally randomly.)

Or simply remove the comma entirely..?
I really like not having the year when it's a recent post... It's halfway between hardcoded and dynamic dates. And it saves precious space.Definitely better...We could also kill $txt['by']... Either do $txt['by_person'] = 'by %1$s', or a series of more strings that would allow for 'by <strong>%1$s</strong>', etc...
Dunno.
It's just that in Japanese, the 'by' is usually shown after the name. But I think it can be put before the name as well, if needed. It just doesn't feel as natural. (And yeah, I know, even SMF doesn't have a Japanese version... But Kyôdai Mahjongg does :P)

It's a bug that was on noisen as well.i never bothered to fix it. Shane on me :P

I'd tend to say it's more amusing/exciting to only keep the relevant entries.

The load fallback is here to stay, if you ask me. I think most people really prefer to have an English string rather than nothing.

Possibilities to explore...

- add a version number to every single language file. Increase version number whenever a change is made to the English version. Compare current version against English version to determine whether we need to load the English fallback (and warn the admin that their language file is broken.)

- store language files in a serialized array in the database. (or in the cache. I think there's already a cache level for language files. A bad one IIRC, because of the variables involved.) When caching fallback & non-fallback, check whether the English version has some extra strings, and only store those.

rev 1097
(6 files, forgot to check size)

* The PM area in the info center should use $txt['personal_messages'] rather than $txt['personal_message'] as its title. Also removed the odd duplicate, added whitespace and increased the font size for the previously smalltext details. (InfoCenter.template.php)

- Removed $txt['msg_alert_you_have'], $txt['msg_alert_messages'] and $txt['your_pms'], unused in Wedge. Or even SMF probably. (index.french.php)

- Removed support for Imeem from Aeva. That's three entries in the sitelist. Apparently they were bought out by MySpace two years ago and nobody bothered to tell me, eh eh. I suspect there are dozens more such dead websites in the list... Anyone willing to test them? (Subs-Aeva-Sites.php)

- Removed an unused parameter in setFocus(). (editor.js)

* French translation. (index.french.php, ManagePlugins.french.php)

! Undefined global in is_already_taken(). (Subs-PrettyUrls.php)

Lookin' nice :)
Maybe we could also sort by author... Or plugin type... Dunno.

Event topics are a social thing though.

I'm just pretty sure there's a way to minify these with little overhead even at the cost of limited gains.