Some translations are not correclty applied #14347

New Issue

GiteaMirror · 2025-11-02T11:10:31-06:00

GiteaMirror commented

2025-11-02 11:10:31 -06:00

Originally created by @Simandara on GitHub (Apr 8, 2025).

Description

Some rare translation are not correctly applied, whenever they have a proofread translated value. This issue is to investigate where the translation fails and be able to more broadly identify other instances.

This bug is quite rare from what I saw.

for this specific case,

While the key has been translated (here, both in French and Italian) and approved

Gitea Version

1.23.6

Can you reproduce the bug on the Gitea demo site?

No!

Operating System

Docker/Linux

How are you running Gitea?

From official Docker image

Originally created by @Simandara on GitHub (Apr 8, 2025). ### Description Some rare translation are not correctly applied, whenever they have a proofread translated value. This issue is to investigate where the translation fails and be able to more broadly identify other instances. This bug is quite rare from what I saw. for this specific case, --- ![Image](https://github.com/user-attachments/assets/a2a8df44-401a-424d-8509-b0a14a0baba9) --- ![Image](https://github.com/user-attachments/assets/d268e717-7c2f-4339-99e9-df4295d7d195) --- While the key has been translated (here, both in French and Italian) and approved ![Image](https://github.com/user-attachments/assets/9b3fb3e0-cd3d-4917-ac51-bf0709b57fc6) ### Gitea Version 1.23.6 ### Can you reproduce the bug on the Gitea demo site? No! ![Image](https://github.com/user-attachments/assets/1cf5bce6-51e2-42a1-b85c-5782a84cac39) ### Operating System Docker/Linux ### How are you running Gitea? From official Docker image

GiteaMirror added the issue/needs-feedback type/bug labels 2025-11-02 11:10:31 -06:00

GiteaMirror closed this issue

2025-11-02 11:10:31 -06:00

GiteaMirror commented

2025-11-02 11:10:32 -06:00

@wxiaoguang commented on GitHub (Apr 22, 2025):

Usually the translations are not backported to stable versions, because Crowdin only has the "main" branch translation resources, they may differ from the stable version's.

So in 1.24 (at the moment "main-nightly") should have these translations.

@wxiaoguang commented on GitHub (Apr 22, 2025): Usually the translations are not backported to stable versions, because Crowdin only has the "main" branch translation resources, they may differ from the stable version's. So in 1.24 (at the moment "main-nightly") should have these translations. * https://dl.gitea.com/gitea/main-nightly/ * https://hub.docker.com/r/gitea/gitea/tags?name=nightly

GiteaMirror commented

2025-11-02 11:10:32 -06:00

@Simandara commented on GitHub (Apr 22, 2025):

If I understand correctly, if a change is made at a given time while the main is on a next iteration than current (let's say 1.24 and 1.23.7), it would be actually applied to when that next is released to docker. Backporting implie manual work by the devs, I guess?

Thus, the right way to track an issue with a translation is to check on the demo instance (or main-nighlty) if the bug occurs as well. Am I right ?

@Simandara commented on GitHub (Apr 22, 2025): If I understand correctly, if a change is made at a given time while the main is on a next iteration than current (let's say 1.24 and 1.23.7), it would be actually applied to when that next is released to docker. Backporting implie manual work by the devs, I guess? Thus, the right way to track an issue with a translation is to check on the demo instance (or main-nighlty) if the bug occurs as well. Am I right ?

GiteaMirror commented

2025-11-02 11:10:32 -06:00

@Simandara commented on GitHub (Apr 22, 2025):

I think, regarding my issue, I can close it, as it will be fixed on 1.24.

However, we can see on the screenshot that the times are in english, should I open another issue ?

@Simandara commented on GitHub (Apr 22, 2025): I think, regarding my issue, I can close it, as it will be fixed on 1.24. However, we can see on the screenshot that the times are in english, should I open another issue ?

GiteaMirror commented

2025-11-02 11:10:32 -06:00

@wxiaoguang commented on GitHub (Apr 22, 2025):

Thus, the right way to track an issue with a translation is to check on the demo instance (or main-nighlty) if the bug occurs as well. Am I right ?

Yes.

However, we can see on the screenshot that the times are in english, should I open another issue ?

IIRC the duration of "work time tracking" is not translatable at the moment (from beginning, since long time ago, Feature: Timetracking (#2211)). The related code is func SecToHours on current main branch.

@wxiaoguang commented on GitHub (Apr 22, 2025): > Thus, the right way to track an issue with a translation is to check on the demo instance (or main-nighlty) if the bug occurs as well. Am I right ? Yes. > However, we can see on the screenshot that the times are in english, should I open another issue ? IIRC the duration of "work time tracking" is not translatable at the moment (from beginning, since long time ago, Feature: Timetracking (#2211)). The related code is `func SecToHours` on current main branch.

GiteaMirror commented

2025-11-02 11:10:33 -06:00

@Simandara commented on GitHub (Apr 22, 2025):

then 'ill close this issue.

@Simandara commented on GitHub (Apr 22, 2025): then 'ill close this issue.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14347