The bug looks like the tool scanned the switch element:

<switch transform="translate(222 162)">
  <text systemLanguage="de">Hammer</text>
  <text systemLanguage="en">Malleus</text>
  <text systemLanguage="eo">martelo</text>
  <text systemLanguage="fa">چکشی</text>
  <text systemLanguage="fi">Vasara</text>
  <text systemLanguage="fr">Marteau</text>
  <text systemLanguage="he">מאליוס</text>
  <text systemLanguage="ne">हथौडा</text>
  <text systemLanguage="ru">молоточек</text>
  <text systemLanguage="ta" transform="rotate(56.201)" x="80" y="-54" text-anchor="end">சம்மட்டியுருவெலும்பு</text>
  <text>Malleus</text>
</switch>

noticed the Tamil (systemLanguage="ta") clause with its transform attribute, and then promoted that attribute for the entire switch/all clauses. Consequently, "Malleus" would be painted at (0,0) with a rotation of 56.201 degrees. IIRC, SVGTranslate v 2.0 did such over-enthusiastic promotions.

@Glrx Do you recommend overlooking transforms entirely if they apply on one element in a switch but not others? Can we?

No, you should not overlook any transform.

Transforms and other properties in switch clauses should only be promoted (aka hoisted) if they appear on each and every clause of the switch. Such promotions must concatenate with any existing transforms rather than replace the existing transforms. Do not assume that properties on one clause exist on all other clauses. That was the mistake that SVGTranslate 2.0 was doing.

SVG files are programs, and any manipulations of the SVG should be done with the same care as optimizing compilers.

In T213937#4955334, @Glrx wrote:

No, you should not overlook any transform.

Transforms and other properties in switch clauses should only be promoted (aka hoisted) if they appear on each and every clause of the switch. Such promotions must concatenate with any existing transforms rather than replace the existing transforms. Do not assume that properties on one clause exist on all other clauses. That was the mistake that SVGTranslate 2.0 was doing.

SVG files are programs, and any manipulations of the SVG should be done with the same care as optimizing compilers.

Thanks @Glrx. @MaxSem @Samwilson Thoughts on this?