On Mon, Nov 18, 2013 at 1:08 PM, Hakan Tandoğan <[email protected]> wrote: > there is the big Messages.properties, of which only one per plugin seems to > exist.
No, one per package. > Is there a way to put every translatable resource into Messages.properties? I would rather ask if there were a way to split up Messages.properties per class, or better yet keep the English version right in the source code so no separate file is needed at all. @NbBundle.Messages in NetBeans sources works this way and it is more convenient when writing code. As a translator, you can use the Translation plugin to avoid manually editing internationalization files. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
