Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options
Translation problem: Activity.Join.FullHeadline
Howdy!
I am creating a Spanish locale for Vanilla -yeah, I know there are three or four versions already, we'd join efforts- and I've just stumbled upon a nice problem with some strings, namely:
$Definition['Activity.Join.FullHeadline'] = '%1$s se ha unido.';
$Definition['Activity.Join.ProfileHeadline'] = '%1$s se ha unido.';
It's all fine if we're talking about another user, but when a user enters his/her own profile and reads "Tú se ha unido"... Well, that's awful, grammatically speaking.
So. Is there a way to differentiate $username from $own-username?
Cheers,
Fabrizio
I am creating a Spanish locale for Vanilla -yeah, I know there are three or four versions already, we'd join efforts- and I've just stumbled upon a nice problem with some strings, namely:
$Definition['Activity.Join.FullHeadline'] = '%1$s se ha unido.';
$Definition['Activity.Join.ProfileHeadline'] = '%1$s se ha unido.';
It's all fine if we're talking about another user, but when a user enters his/her own profile and reads "Tú se ha unido"... Well, that's awful, grammatically speaking.
So. Is there a way to differentiate $username from $own-username?
Cheers,
Fabrizio
Tagged:
1
Comments
I suggest make function FormatActivityHeadline locale dependent. And FormatDate too.