Okay, I can appreciate avoiding extra trouble for others, and it’s certainly easier for me to add the workaround translation for just this one case. I’ve now done that (with your suggestion, which was probably as good as this can be).

%{month_name} %{year} would work better for Finnish, as that would allow the month name to be inflected apart from the year (which is how the current accepted translation of this string was intended to work). OTOH, the Finnish way a ”month name + year number” combination in inflected in most, if not all (relevant) cases is like that: add a suffix to the month name, leave the year number as-is. Without workarounds, %{month_year} generally only works for the nominative case.

”Monthly Supporter since December 2018” would be ”Kuukausittainen tukija joulukuusta 2018 lähtien”, where ”joulukuu” is the month name (and the current translation for that string doesn’t correctly account for the inflection either). Finnish has 6 different locational cases alone, so yeah, Finnish inflection can be a pain :)

I’ve only come across this title string (%{taxon} from %{place} in %{month} by %{user}) on an observation page where the date is obscured to month, whereas the (more usual case of) title for non-obscured observations has already been translated to work around the inflection. Although the latter makes for varyingly clunky Finnish, at least it’s technically not incorrect, and hence that’s how the problem is usually worked around in Finnish software translations. I can figure out a similar workaround translation for this string too (that is, take your option b).

I’m still confused by the source string here using %{month}, which then gets turned into %{month_year}, requiring translators to pay attention to the explainer text in the reference, instead of just using %{month_year} in the source directly.

For some reason, instead of the %{month} here, a %{month_year} is shown instead, at least when it comes to <title> elements. So for instance, an observation from July 2020 currently has the <title> rendered as ”heinäkuu 2020ssa”, when it should be ”heinäkuussa”.

Describe the bug
The email with updates from the last 24 hours lists identifications, and mentions the name of the user having made the ID. The name is apparently supposed to be listed three times (!), but the middle occurrence is ”untranslated”, resulting in it being rendered as ”User S” for all identifications listed in the email.

Tooltip text for the ”User S” string says ”translation missing: fi.user_s_id”, as I’m using the fi locale, but user_s_id is nowhere to be found in Crowdin, nor in current en.yml, so I suspect this is independent of the locale. The reference to user_s_id is in _update_email_activity.html.

I don’t know if this is doable, but after fixing this broken reference, I’d remove the first (header) mention of the identifier from the email altogether, since it’s followed by a listing of all the new identifiers anyway, so mentioning just the last identifier’s name in the header is redundant and confusing.

Also, rather than fixing/adding the currently broken ”User S” reference in the source, I’d remove it too, since the identifier’s name is already listed (for the third time!) right after the ID.

To Reproduce

1. Subscibe to email updates.
2. Have your observations identified in the last 24 hours.
3. View the email update listing the identifications.

Observed behavior

Expected behavior
(A mockup of how the simplified view I’d prefer to receive. Sorry I didn’t have the email in English to base this on.)

Context
I’m using Gmail with Brave if that’s relevant.

The current accepted translation has a typo, making the already confusing option even more so: the word ”on” shouldn’t be there. The suggestion from Jani Järvi fixes this correctly.

Month numbers in Finnish went all haywire in the last app update, and I think this is due to `mm` which should have been MM.