Username eloquence
Full name Erik Moeller
Translations made 25
Suggestions made 0
Pending suggestions Browse pending 0
Screenshots uploaded 1
Last login Oct. 16, 2020, 10:10 p.m.
Registration date Oct. 31, 2018, 1:18 a.m.

Projects

SecureDrop

Activity in last 30 days

Activity in last year

Recent changes

Yes, I agree it's best to translate this example. Is there a technical reason you're commenting on it? As far as I can tell, the whole string is ready for translation.

2 weeks ago

Hi @kingu, I'd just like to state clearly on behalf of the SecureDrop team that the code of conduct applies to all SecureDrop-related work, including translations. While we can refine details of it, its existence is not up for debate, and radical changes like the ones you proposed in https://github.com/freedomofpress/securedrop-i18n/pull/4 are not going to happen.

3 months ago

This string refers to the flyout that appears when you click the shield icon (not when you mouse over it), which in fact still says "Advanced Security Settings".

3 months ago

@AOLocalizationLab.:The website you linked to merely makes the point that exclamation marks are rarely used in academic writing, which this is not; it's what the website calls an "emphatic declaration" in the context of UI copy. "Sorry." "Sorry!" and "Sorry" all have a different emotional tone in English, and sometimes we may choose one over the other, depending on the tone that seems most appropriate in a given context. But I don't think it's a huge deal either way, so if others also prefer "Sorry." in this context, I'd be happy to change it.

3 months ago

That's an intentional design choice in this case, to make the message less formal and more friendly.

3 months ago

There is an explanation in Weblate now for this string. The demo site will be back soon (within the next 3 months).

3 months ago

This text appears on a button, so it's intentionally short. There's a fair bit of explanatory text around it.

3 months ago

Hi @ebonsi, I am not sure that changing the capitalization in the source string would be advisable here. The reason is that converting case in code or via CSS can have unpredictable results in certain languages. As Mozilla advises on https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_content_best_practices :

In general, localizers should make the decision about capitalization. If you want to display WARNING, add a string with that capitalization, and explain it in the localization note.

On that basis I think it may be preferable to keep these strings all-uppercase, but I defer to the experts like @erinm.

3 months ago

I've added an explanation in Weblate to avoid confusion about the verb tense.

3 months ago

Thanks @robbpa, I've added that to the explanation section in Weblate.

3 months ago
Browse all changes for user