buhtz commented 2025年11月24日 11:19:11 +01:00

Comment

This is a re-post original posted at upstream Weblate.
The maintainers there are asking details specific to the Weblate instance of Codeberg.

The question is if Codeberg is using any modifications of the original Weblate that might cause the issue I am describing. Or do you have any other idea?

Hello,

I am project maintainer and using Codeberg's Weblate (v 5.14) instance for translation.

In the last weeks I have several false positive checks. One example is this about "Mismatched full stop", but both strings does have a full stop at their end.

https://translate.codeberg.org/translate/backintime/common/fr/?checksum=1538b281a7b15f29

As screenshot

[画像:image]

Do you have any idea what it could be? Do I misuse something. Or is it a server configuration that could have been changed (I am not the server admin).

Or might this be a bug in a new version? I am not aware when Codeborg made the last update.

Regards,
Christian

EDIT

Please let me add other checks.

Double space

https://translate.codeberg.org/translate/backintime/common/tr/?checksum=9ca2daa8f40ca29c
image

Reused translation

https://translate.codeberg.org/translate/backintime/common/tr/?checksum=85c131640a5af658
image

### Comment This is a re-post original posted at [upstream Weblate](https://github.com/orgs/WeblateOrg/discussions/17040). The maintainers there are asking details specific to the Weblate instance of Codeberg. The question is if Codeberg is using any modifications of the original Weblate that might cause the issue I am describing. Or do you have any other idea? Hello, I am project maintainer and using Codeberg's Weblate (v 5.14) instance for translation. In the last weeks I have several false positive checks. One example is this about "Mismatched full stop", but both strings does have a full stop at their end. https://translate.codeberg.org/translate/backintime/common/fr/?checksum=1538b281a7b15f29 As screenshot <img width="1140" height="540" alt="image" src="https://github.com/user-attachments/assets/081adb75-3837-4034-9add-4cf0143cfcfb" /> Do you have any idea what it could be? Do I misuse something. Or is it a server configuration that could have been changed (I am not the server admin). Or might this be a bug in a new version? I am not aware when Codeborg made the last update. Regards, Christian # EDIT Please let me add other checks. ### Double space https://translate.codeberg.org/translate/backintime/common/tr/?checksum=9ca2daa8f40ca29c  ### Reused translation https://translate.codeberg.org/translate/backintime/common/tr/?checksum=85c131640a5af658 

jrtcdbrg commented 2025年11月28日 14:28:26 +01:00

I can confirm this issue of false positives in validation and add the following:

• has been around last ca 3-4 weeks
• started first in Hosted Weblate and thereafter in Codeberg Translate (this may point to version updates)
• I have seen couple of different false positives, among them most popular are "Mismatched full stop" and "Translation contains double stop"
• happens mostly after translation, i.e. you finish a translation and in couple of hours and/or one day or two it shows up (like a backend process has run meanwhile)
• seems to affect projects that you have translated very recently
• coincided with the change of behavior of the Weblate - earlier when you made an error that was caught by validation, you saw the error message immediately, but now there is a very noticeable pause (like 5 seconds) when you see the error message and can fix it
• it may well be, that some of these remarks are not related to the issue

I can confirm this issue of false positives in validation and add the following: - has been around last ca 3-4 weeks - started first in Hosted Weblate and thereafter in Codeberg Translate (this may point to version updates) - I have seen couple of different false positives, among them most popular are "Mismatched full stop" and "Translation contains double stop" - happens mostly after translation, i.e. you finish a translation and in couple of hours and/or one day or two it shows up (like a backend process has run meanwhile) - seems to affect projects that you have translated very recently - coincided with the change of behavior of the Weblate - earlier when you made an error that was caught by validation, you saw the error message immediately, but now there is a very noticeable pause (like 5 seconds) when you see the error message and can fix it - it may well be, that some of these remarks are not related to the issue

Gusted commented 2025年11月29日 17:11:59 +01:00

@buhtz wrote in #2231 (comment):

The question is if Codeberg is using any modifications of the original Weblate that might cause the issue I am describing. Or do you have any other idea?

Codeberg uses vanilla weblate (via Docker) with a minimal amount of patches that don't affect any workings of the translation checks: https://codeberg.org/Codeberg-Infrastructure/weblate-docker/src/branch/main/patches

It's quite likely the bug is in Weblate. CC @Bubu

@buhtz wrote in https://codeberg.org/Codeberg/Community/issues/2231#issue-2724207: > The question is if Codeberg is using any modifications of the original Weblate that might cause the issue I am describing. Or do you have any other idea? Codeberg uses vanilla weblate (via Docker) with a minimal amount of patches that don't affect any workings of the translation checks: https://codeberg.org/Codeberg-Infrastructure/weblate-docker/src/branch/main/patches It's quite likely the bug is in Weblate. CC @Bubu

Bubu commented 2025年11月29日 18:04:57 +01:00

I updated to weblate 5.14.3 just now. I haven't seen anything in the changelog that looks like a direct fix for this, but it could still have been fixed. @buhtz could you check if the problem still exists?

I updated to weblate 5.14.3 just now. I haven't seen anything in the changelog that looks like a direct fix for this, but it could still have been fixed. @buhtz could you check if the problem still exists?

Bubu commented 2025年11月29日 18:05:29 +01:00

@jrtcdbrg Do you know if this has been reported to the weblate project yet?

@jrtcdbrg Do you know if this has been reported to the weblate project yet?

buhtz commented 2025年11月29日 18:32:36 +01:00

@jrtcdbrg Do you know if this has been reported to the weblate project yet?

https://github.com/orgs/WeblateOrg/discussions/17040

> @jrtcdbrg Do you know if this has been reported to the weblate project yet? https://github.com/orgs/WeblateOrg/discussions/17040

nijel commented 2025年12月01日 09:24:03 +01:00

@jrtcdbrg and @Bubu can you match the period when this started to happen with Weblate upgrades on Codeberg? This would make it easier to identify what might be causing this. As this is apparently not bound to a specific check, it has to be some core functionality that changed the behavior in an unexpected way.

@jrtcdbrg and @Bubu can you match the period when this started to happen with Weblate upgrades on Codeberg? This would make it easier to identify what might be causing this. As this is apparently not bound to a specific check, it has to be some core functionality that changed the behavior in an unexpected way.

Bubu commented 2025年12月02日 01:38:27 +01:00

@nijel I deployed weblate 5.13.5 on Oct 12th, then 5.14.0 on the October 30th, and then to 5.14.3 two days ago, as noted above.

@jrtcdbrg's 3-4 weeks ago could match up with the 5.14.0 deployment.

@nijel I deployed weblate 5.13.5 on Oct 12th, then 5.14.0 on the October 30th, and then to 5.14.3 two days ago, as noted above. @jrtcdbrg's 3-4 weeks ago could match up with the 5.14.0 deployment.

nijel commented 2025年12月02日 15:19:32 +01:00

https://github.com/WeblateOrg/weblate/pull/17129 should fix this.

https://github.com/WeblateOrg/weblate/pull/17129 should fix this.

jrtcdbrg commented 2025年12月12日 12:23:06 +01:00

I do not know if fix has been deployed or not (or some other remedy applied), but I have not seen false positives for a week or so neither in Hosted Weblate nor Codeberg Translate.

Probably it is a separate issue, but the same time an UI problem has appeared in Hosted Weblate but not in Codeberg Translate - the "Nearby strings - ... - History" toolbar loses focus upon saving the translation and reverts always to first value.

I do not know if fix has been deployed or not (or some other remedy applied), but I have not seen false positives for a week or so neither in Hosted Weblate nor Codeberg Translate. Probably it is a separate issue, but the same time an UI problem has appeared in Hosted Weblate but not in Codeberg Translate - the "Nearby strings - ... - History" toolbar loses focus upon saving the translation and reverts always to first value.

nijel commented 2025年12月12日 13:30:09 +01:00

The fix is deployed on Hosted Weblate, but IMHO not yet on Codeberg (because it was not yet released).

As for the translate tabs, that's indeed a regression caused by the frontend rewrite; https://github.com/WeblateOrg/weblate/issues/17289 tracks that. Don't hesitate to report such issues directly to our issue tracker 😃.

The fix is deployed on Hosted Weblate, but IMHO not yet on Codeberg (because it was not yet released). As for the translate tabs, that's indeed a regression caused by the frontend rewrite; https://github.com/WeblateOrg/weblate/issues/17289 tracks that. Don't hesitate to report such issues directly to our issue tracker 😃.

jrtcdbrg commented 2025年12月13日 12:52:25 +01:00

Thanks for feedback and all the best success in what you do. As I have no plans to create GitHub account, then reporting here was somewhat intentional.

I'll keep an eye on how #17289 develops then. This UI bug really slows down high-volume translators.

Thanks for feedback and all the best success in what you do. As I have no plans to create GitHub account, then reporting here was somewhat intentional. I'll keep an eye on how #17289 develops then. This UI bug really slows down high-volume translators.