2. Users
3. eloquence

Currently it's the number 1. I think "the selected source" or similar would be a bit more elegant for the singular, post-1.8.0.

John, correct me if I'm wrong, but I believe this is due to technical limitations. This dialog is displayed with and without JavaScript, and as a result, the string is rendered before the selection count is known. We could theoretically progressively replace it if JavaScript was enabled, but then we're blocked by lack of client-side pluralization support in our current JavaScript code to actually add a plural form.

tl;dr I think the best we could do here is something like "account(s)" and I'm not sure that's better than what we have right now.

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.

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.

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".

@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.

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

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

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

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.