As you all know, the YaST team is lately involved in many projects not
limited to YaST itself.
So it's time to take a look to how things are moving on:
- Recent changes for YaST (just in time for Leap 15.4)
- Containerizing YaST to make it useful in container-based environments
like openSUSE Micro.
- Evolution of D-Installer
Check the whole report at
Ancor González Sosa
YaST Team at SUSE Linux GmbH
TL;DR: Use the "TRANSLATORS" tag for marking the comments for translators.
Currently we extract *all* preceding comments to the generated POT files. The side
effect is that in some cases the comment contains the license header, Yardoc comments
or even commented out code. That might be confusing for translators.
The solution is to use some special tag and instruct gettext to extract the
comments only following this special tag. We already use the "TRANSLATORS" tag
in YaST for that.
# this comment is *not* copied to the POT file
# TRANSLATORS: this comment *is* copied to the POT file
# this *is* copied as well
Unfortunately it is not used everywhere, when I tried to use it globally a lot of
comments from POT files were lost.
For that reason I have introduced the POTCOMMENTS file, similar to the existing
POTFILES used in some repositories. That file should contain the tag name passed to
gettext. I.e. it should just contain the "TRANSLATORS" value so it is the same in all
If that file is missing the old approach (all comments) is used, so it is backward
compatible and we can gradually fix the modules one by one.
See https://github.com/yast/yast-devtools/pull/166 for the implementation details
and https://github.com/yast/yast-firstboot/pull/136 as an example how it was fixed in
one YaST module.
SUSE LINUX, s.r.o.
18600 Praha 8
In SLES 15 SP3, how are the patterns and package descriptions translated?
Until SLES 12 SP5, we were modifying the package package-translations by merging the po files for a translated language and creating the package-translations-$lang.mo files
In SLES 15 SP3, I tried to do the same, merging all po files for a translated language and creating the package-translations-$lang.mo files.
Now in SLES 15 SP3 during installation, if I change the language I am not getting the translated description for the patterns.
I would really appreciate it if you could help us understand how to localize our patterns and package descriptions.