I'm going to throw in a dep on bug 32987 ("The language used to render SVGs should be definable") since this would be of limited use until that's actually available.

So now that language switch for svgs works, what else is blocking this? Does it just need review and deploy, or are there other things that need to be done.

Last time I checked there were issues with the integration with Translate extension (because we've updated apis a lot lately). Those would probably come up in the review.

(In reply to comment #2)

So now that language switch for svgs works, what else is blocking this?

Would it be possible to get this extension installed on a public beta wiki?

(In reply to comment #4)

(In reply to comment #2)

So now that language switch for svgs works, what else is blocking this?

Would it be possible to get this extension installed on a public beta wiki?

See http://translatesvg.wmflabs.org.

Basically this bug is waiting on me having enough time, or someone else having the inclination, to update the TranslateSvg codebase to match developments with the Translate extension, then manage the process of testing it, etc, etc.

(In reply to Jarry1250 from comment #5)

See http://translatesvg.wmflabs.org.

Basically this bug is waiting on me having enough time, or someone else
having the inclination, to update the TranslateSvg codebase to match
developments with the Translate extension, then manage the process of
testing it, etc, etc.

So this has to happen first.
Not sure if "high priority" on this ticket reflects reality then... :-/

@all As this ticket is specifically about review and deploy of TranslateSVG extension, I created an Epic for the Wishlist project work at T201207: [Epic] SVG Translate wishlist project.