Currently it is hard coded that the 'ago' of time ago ist AFTER the time span it refers to (e.g. 1 hour ago). For translatability (in my case german) it must be configurable in the translation string that the translation of ago is in front of the time span.

So if the source code would contain something like '@time ago' (apologize any incorrectness, I'm not a programmer) it could be translated into something like 'ago @time' and everything would be fine. The strings are listed in lines 66 up to 90.

Comments

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Title: Translatability (time ago) » Check translatability
Category: bug » task
Status: Active » Postponed

I really don't suggest trying to translate this branch, yet, considering it's not even remotely close to done. I will go over all the strings once it's ready for RC. I'll leave this active as a reminder but won't get to it any time soon.

Michelle

FrankT’s picture

FrankT commented

I only opened this issue because it has to be solved by changing the code, but I don't mind if you concentrate on translations later.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Well, the thing is that the code in question may not even exist at the end so there's no point in trying to fix things like this until everything is stable.

Michelle

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Status: Postponed » Active

Just setting this active again so it doesn't get forgotten but it's still a ways off.

Michelle

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Status: Active » Fixed

As far as I know, everything is all set to be translated and strings won't be changed unless absolutely necessary so should be good to go.

Michelle

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.