Sorry, that escaped before I was finished... If we really need a new message template, a new enum value should be set up for it and translations added to each of those 20 translation maps. (We can debate separately whether Google Translate is now adequate for creating at least the initial translations rather than having to resort to the team of human translators IBM used.)
Build and test messages haven't been internationalized and won't be. Most error messages from the Xalan code to its users Should be, for the conventional official meaning of Should. Yes, this is a bit of a nuisance. The benefits were deemed worth it; W3C was putting heavy emphasis on I18n and Apache concurred. It was expensive to achieve. Please try not to break it. If you need help dealing with the error frameworks, let me know. If you think we should move to a more standard framework, write a Jira ticket for that. The cleanest migration might be to make that the back end of the existing framework call the new favored package, then migrate the individual error messages to call that directly as we work on the code. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Joseph Kesselman Sent: Saturday, December 2, 2023 11:46:53 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Correcting a slight misunderstanding In discussion on Git, someone said "Xalan-J currently does not use any logging frameworks." That isn't quite correct. Xalan doesn't use one of the now-standard logging frameworks. But if you actually sift through the code, you'll find that most instances of System.err are either commented out, or behind debugging fences. Xalan has its own severity-level-filtered logging system, written when before those were generally adopted. (Actually, I suspect it has two; I haven't checked in as much detail but I believe xalan-test has its own, in the org.apache.qetest package hierarchy.) An additional detail to keep in mind when working on this code; Xalan's own messages run through an (equally early) i18n layer, supporting roughly 20 languages. When adding an error message, we really should be trying to run it through that system. It's simplest to use one of the message templates already there. If we really need a new message, we should look at adding a new -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant.
