On Mon, 10 Jun 2024 20:12:42 GMT, Jonathan Gibbons <j...@openjdk.org> wrote:
>> This is what I've determined as well. I planned to leave these untranslated >> to reduce noise between drops as well. > > While we do not translate Java keywords (when used as such, e.g. "`class` not > allowed here"), and option names (e.g. `--class-path`) we have typically > translated other text that is not mandated by the language or tools, (e.g. > `the name of this class`, `<args>`, `<class-path>`. > > This change seems to be going backwards. > > Whatever the policy we use for translating (or not translating) parts of a > message, we should be consistent across all tools and documents. The go translation team dictates which of these segments within a file actually get updated. I can manually revert the segments if preferred, but these changes will continue appearing for future drops with the current system. I can potentially try to communicate to the other team to differentiate between keywords & option names versus some of these other words, but let me know how you'd like me to proceed with this. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/19609#discussion_r1633794362
