Dne 23. 02. 22 v 16:30 Tommi Nieminen napsal(a):
2) In YaST, some strings do not appear to be translated in the UI even while they *are* translated in Weblate. It looks like the translatable source strings in Weblate do not exactly match those actually used in YaST. For example, desktop-file-translations/update-desktop-files-yast (both master and SLE-15-GA) have the source text:
“Choose the repositories for installation of software packages (CD, network, etc.), add the community repositories”
…but this is NOT the form that you can see in YaST UI. Instead, the string is:
“Choose the repositories for installation of software packages (CD,network,etc.),add the community repositories”
(i.e., there are no spaces after the commas).
This is another story. YaST translation is a bit complicated: - Package is submitted, making a translation tag. - Jenkins robot collects strings from all YaST packages and commits it to GitHub. - GitHub Weblate webhook informs Weblate to fetch latest translation sources. - Translators translate. - Weblate pushes translations to GitHub. - yast-translations needs to be picked and submitted to the yast2-trans package, either by robot or by human. - Once the new translation package appears, translations should be in place. That is why the YaST translations round trip is a bit slower, and in general, it can take a month or even more to be translated. Any of the steps above can break, and if the translation will not appear, the path of the translations needs to be inspected. Where it was lost? -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.com Křižíkova 148/34 (Corso IIa) tel: +420 284 084 060 186 00 Praha 8-Karlín fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76