Codeberg/Community
54
325
Fork
You've already forked Community
12

Wrong relative date 'yesterday'/'gestern' shown #2131

Open
opened 2025年09月10日 22:30:15 +02:00 by bttr · 4 comments

Comment

When today is September 10th, then September 8th should not be shown as 'gestern' ('yesterday'), but 'vorgestern' ('two days ago' or 'the day before yesterday').

Before 24 h pass it is shown wrong.

grafik

After 24 h it is fine.

grafik

Same here:

grafik

grafik

### Comment When today is September 10th, then September 8th should **not** be shown as 'gestern' ('yesterday'), but 'vorgestern' ('two days ago' or 'the day before yesterday'). Before 24 h pass it is shown wrong. ![grafik](/attachments/ec479f61-09d9-4c95-8c37-9953de20e907) After 24 h it is fine. ![grafik](/attachments/61bf5d59-1d13-436e-ab11-3673890eb707) Same here: ![grafik](/attachments/2ccaff14-5f14-45d4-82fc-aa8ebc6a2422) ![grafik](/attachments/f2aa62ae-35b8-46bf-b00f-c4783badcd8a)
Author
Copy link

This 'last week'/'letzte Woche' at #2130 (comment) too:

grafik

If today is September 23rd, then 'last week' is from September 15th to September 21st, but not September 10th.

This 'last week'/'letzte Woche' at https://codeberg.org/Codeberg/Community/issues/2130#issuecomment-7101955 too: ![grafik](/attachments/ac020ae4-2251-4364-9dd3-a34552f3e332) If today is September 23rd, then 'last week' is from September 15th to September 21st, but not September 10th.

A issue in forgejo was opened about this: forgejo/forgejo#9411, do you feel this issue represent your issue/concern?

A issue in forgejo was opened about this: forgejo/forgejo#9411, do you feel this issue represent your issue/concern?

This forgejo issue doesn't represent this one, but the fix described therein probably fixes it. The problem is [0], where everything between 24 and 48 hours (2 days minus one unit) is marked as 1day.

Do you want us to make a new bug report to forgejo for this, @Gusted?

[0]

if (days === 1 && pageData.DATETIMESTRINGS['relativetime.1day']) {
This forgejo issue doesn't represent this one, but the fix described therein probably fixes it. The problem is [0], where everything between 24 and 48 hours (2 days minus one unit) is marked as 1day. Do you want us to make a new bug report to forgejo for this, @Gusted? [0] https://codeberg.org/forgejo/forgejo/src/commit/dc5580525e29dd88133183e0d89533e195e1bdf9/web_src/js/webcomponents/relative-time.js#L170

@kad-hollac1 wrote in #2131 (comment):

The problem is [0], where everything between 24 and 48 hours (2 days minus one unit) is marked as 1day.

That's sort of the same problem already described in forgejo/forgejo#9411 I would say that the wording mismatches.

@kad-hollac1 wrote in https://codeberg.org/Codeberg/Community/issues/2131#issuecomment-8362230: > The problem is [0], where everything between 24 and 48 hours (2 days minus one unit) is marked as 1day. That's sort of the same problem already described in forgejo/forgejo#9411 I would say that the wording mismatches.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2131
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?