Post Aw9MYRnmHFINiO2jZY by fps_gbg@mastodon.social
 (DIR) More posts by fps_gbg@mastodon.social
 (DIR) Post #Aw9GJn7k7Xvdm80fuC by fps_gbg@mastodon.social
       2025-07-14T11:56:12Z
       
       0 likes, 0 repeats
       
       @peertube There seems to be a change in the #weblate update process of translation strings (now twice in a row). Unfortunately this is to the worse. The English strings are copied to the target language strings automatically which makes it much harder and works against weblates support of your workflow in many cases. Please keep the *new* target language strings empty like previously.The #deepl too many dictionaries error seems to be partially fixed though. Cheers.
       
 (DIR) Post #Aw9GJok46YB2nGwnHE by peertube@framapiaf.org
       2025-07-15T05:59:45Z
       
       0 likes, 0 repeats
       
       @fps_gbg Hello, AFAIK English strings are in the target field from the beginning if you're talking about the "angular" component.
       
 (DIR) Post #Aw9MYRnmHFINiO2jZY by fps_gbg@mastodon.social
       2025-07-15T07:09:39Z
       
       0 likes, 0 repeats
       
       @peertube Yes, there were a few in the player component as well. It feels much more clumsy to work with compared to the previous 7.x translation dumps (Dec-May). Can it be changed? Or at least deactivate the identity control "La chaîne source et la chaîne traduite sont identiques." for ```state:<translated```? We are doing consistency checks now, so we are done with July batches. Thanks.
       
 (DIR) Post #AwBZ9QM7iBvCEr5wDA by peertube@framapiaf.org
       2025-07-16T08:40:13Z
       
       0 likes, 0 repeats
       
       @fps_gbg Can you send me the dumps so I can understand their difference?We can also ignore the alerts for the specific strings that have the same translated text as the source if you give me the links (if they aren't too many?)