A user, groove6j, reported an issue with relative timestamps in the Latvian language pack, where timestamps showed “0h” or “0 days” for a period of time. Moin asked for the affected language and groove6j confirmed it was Latvian. Moin suggested the issue might be due to incorrect translations for zero and provided a link to the relevant code. Replacing “0” with “%{count}” solved the problem, as confirmed by groove6j. Moin requested that the translations be updated on Crowdin, which was acknowledged by groove6j.
When a user makes a post, the timestamps everywhere show 0h, or after 0 days for some period of time (only while the date is relative). When I switch to another language, it’s all fine. I can’t figure out which strings should be changed. Any ideas?