new locations for string translations

[Alceu Rodrigues de Freitas Junior]

Hi,

After some manual checking on the Jenkins interface, I found a new location with Properties/Jelly files that requires translations: core/src/main/resources/hudson/model/AllView.

This is an example of modified (still not released) version of jtt:

Got warnings for core/src/main/resources/hudson/model/AllView/noJob_pt_BR.properties:
    Missing 'anonymousDescriptionSignUpEnabled'
    Missing 'learnMoreDistributedBuilds'
    Missing 'setUpAgent'
    Missing 'setUpCloud'
    Missing 'startBuilding'
    Missing 'noJobDescription'
    Missing 'anonymousDescription'
    Missing 'setUpDistributedBuilds'
    Missing 'createJob'
    Unused 'Welcome\ to\ Jenkins!'

Those locations are not being considered by translation-tool.pl or a current release of jtt. Does anybody know why this directory wasn't being considered before?

Both programs only consider a Properties file that matches the following regular expression: Messages\.properties$.

Thanks in advance,

Alceu

[Winter, Markus]

There is a noJob.groovy, so this view is not using jelly, my guess is there are more such places

 

From: jenkin...@googlegroups.com <jenkin...@googlegroups.com> On Behalf Of Alceu Rodrigues de Freitas Junior
Sent: Dienstag, 15. November 2022 17:58
To: Jenkins Developers <jenkin...@googlegroups.com>
Subject: new locations for string translations

 

Some people who received this message don't often get email from alceu.fr...@gmail.com. Learn why this is important

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2886c932-0987-4bdc-b535-096c81100808n%40googlegroups.com.

[Alceu Rodrigues de Freitas Junior]

I did an exercise here, trying to find Properties files that should be the originals in English because their filenames matches \.properties$ and don't have a known language code as a suffix (after the extension is removed).

If I didn't messed up (there are many cases to manually check), the number of files that require translation just increased a lot (~50%):

        Translation Status

    Status         Total      %
    -----------------------------
    Done           2120     57.12
    Missing        1200     32.33
    Unused         382      10.29
    Empty          0        0
    Same           9        0.242
    No_jenkins     0        0

Total of files: 913

Those are not even considering the cases where there Groovy files that don't have a respective Properties file (i.e., they have the English string directly put into them).