To add ?lang (language) attribute

[r-martins]

Some badges are displayed always in english.
For example:

It would be nice if we could specify that "yesterday", "month", "tested" are displayed in another language.

[PyvesB]

Hello @r-martins 👋🏻

Thanks for the idea, it does sound like a reasonable ask. @LitoMore @jNullj what do you think?

[LitoMore]

This seems like a reasonable requirement, but i18n is often not easy to maintain in the long term. We need to think about how we can keep all formats and translations up to date.

I think this requirement might be better suited to them implementing it using an endpoint badge themselves.

[jNullj]

The first question that comes to mind, does this feature aligns with project goals/should it be added here and not by third party?

• adding multiple translation could be seen as a form of breaking consistency
• i think it's reasonable to assume the vast majority of devs use English very often and are somewhat confident using it, so maybe keeping English as our only supported language will reduce fragmentation in badges style while not hurting accessibility too much.
• on the other hand it makes shield more accessible and feel more natural to a local community, and will reduce inconsistency endpoint solutions may introduce.
• While accessibility is not directly mentioned as a project goal, imo it's a plus.

please note this is a practical point of view, in another timeline the dominant language in dev space could have been any other language.

So while we might go one way or the other, shields always had strong customization for badges, if we already allow users to customize so much, it goes with project spirit to add this feature, that's why after going over the above for/against I tend to think this should be added.

Assuming we have a consensus that this would be in the scope of shields:
With more pressing changes and some backlog, I'm not sure that this is the best time to introduce this change.
We may start by making an issue to both direct users to use the endpoint badge (as suggested by @LitoMore ) while also using it to measure how large of an impact adding this can have for users, by looking at how many users upvote the request (we may reduce notifications by setting a goal and asking users to use upvote emoji before this goal is met).

If we don't see growing support we can later close the issue and convert the instructions into a page at https://shields.io/docs

Let me know what you think.

[PyvesB]

Overall agree with your observations. Creating an issue sounds like a good start.

[PyvesB]

I did find one existing issue related to this, though it's quite specific and could benefit from a more generalised approach: #10986