The Structorizer logfile reports some cryptic message access faults on start

[codemanyak]

The structorizer log file reports at least four translation warnings on startup:

<record>
  <date>2023-10-26T12:12:54.582567100Z</date>
  <millis>1698322374582</millis>
  <nanos>567100</nanos>
  <sequence>2</sequence>
  <logger>lu.fisch.structorizer.locales.Locale</logger>
  <level>INFO</level>
  <class>lu.fisch.structorizer.locales.Locale</class>
  <method>&lt;init&gt;</method>
  <thread>1</thread>
  <message>Loading now locale: en.txt</message>
</record>
<record>
  <date>2023-10-26T12:12:55.095301200Z</date>
  <millis>1698322375095</millis>
  <nanos>301200</nanos>
  <sequence>3</sequence>
  <logger>lu.fisch.structorizer.locales.Locales</logger>
  <level>WARNING</level>
  <class>lu.fisch.structorizer.locales.Locales</class>
  <method>setLocale</method>
  <thread>20</thread>
  <message>LANG: Error accessing element &lt;{0}.{1}&gt;!
{}</message>
</record>
<record>
  <date>2023-10-26T12:12:55.096298700Z</date>
  <millis>1698322375096</millis>
  <nanos>298700</nanos>
  <sequence>4</sequence>
  <logger>lu.fisch.structorizer.locales.Locales</logger>
  <level>WARNING</level>
  <class>lu.fisch.structorizer.locales.Locales</class>
  <method>setLocale</method>
  <thread>20</thread>
  <message>LANG: Error accessing element &lt;{0}.{1}&gt;!
{}</message>
</record>

(The latter two records are repeated once more, with increased time stamps and record numbers, of course.)

This is due to some obsolete JavaUpgrade announcements the orphaned translations for which have "survived" (i.e. were forgotten) in sevral locale files. In addition, the log text configuration is defective such that the argument substitution for "{0}" and "{1}" didn't work. This does not cause harm but maybe confusing when looking for actual starting problems.