Some strings of the add-on store GUI are not provided to translators as reported in this message.
Cause
When generating the .pot file, svn2nvda looks for .py files only in NVDA's source folder and maximum two levels below. However, after merging of https://github.com/nvaccess/nvda/pull/13985, the GUI files of the add-on store are three levels below, thus they are not taken as source when generating the .pot file.
Solution
Added one more level for the sources used by xgettext to generate the .pot file.
Testing
@seanbudd could you manually check the generated files on the server?
Check after merge that the strings are provided to translators.
Another issue found on the .pot generation
Issue
Some strings of the add-on store GUI are not provided to translators as reported in this message.
Cause
When generating the .pot file, svn2nvda looks for .py files only in NVDA's source folder and maximum two levels below. However, after merging of https://github.com/nvaccess/nvda/pull/13985, the GUI files of the add-on store are three levels below, thus they are not taken as source when generating the .pot file.
Solution
Added one more level for the sources used by xgettext to generate the .pot file.
Testing