Thanks Tim! That is what I was expecting, but I got some cases that don't follow the format you just described.
On Thu, Aug 25, 2022 at 4:28 PM Tim Van Holder <[email protected]> wrote: > Hi Alceu, > > I would expect that in most cases, the jelly files used by Jenkins and its > plugins would already be using localized strings (like "${%Hello World}" > which will use the "Hello World" resource from the bundle matching the > jelly file's basename. > > I'm not sure why you would need any regex parsing on top of the XML > processing either (or write a grammar for Jelly when it's really XML); for > the standard set of jelly/stapler/... tags, the list of attributes that > contain "real" text should be fairly well-known. > And nested text nodes, especially for non-jelly tages, could likely always > be considered as localizable text. > > Note: perhaps it would be useful for the IDEA plugin to have an inspection > that will suggest using "${%Hello World}" instead of just "Hello World" for > well-known attributes, like title on f:entry (probably the most common bit > of localizable text in a jelly file). > Perhaps even a CodeQL-based thing on GitHub, to identify possible > localization issues. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAKxtECp2OfOKBQ88f0%3D2zw50AR%3D9TradrTr-4nx8Rz%2BFj8%2B_%3Dw%40mail.gmail.com.
