(URGENT) Jing crash on Japanese Windows 11 due to output encoding differences (UTF-8), unfixable and unrecoverable now

[ronaldtse]

We had a 3.5 hour debugging session yesterday involving the @AAS-YknKawakita @AIS-RyoMukai @ReesePlews @CAMOBAP and myself.

We worked with interactively a Japanese Windows 11 machine with limited RAM (8GB) that is meant to run the build.

Jing crashes on document 001-v4 on this machine due to 2 problems:

1. Jing failed with a "mismatched encoding". This is likely due to the Windows 11 machine being in Japanese, somehow the Java Jing program's validation output does not work with the ruby-jing wrapper gem, and crashes the entire stack.
2. Jing fails with Java heap size issues because the document is too large. It is shown that 4GB of Java heap size does not work.

@CAMOBAP tested setting the Windows Command Prompt / PowerShell code page to UTF-8 which is a similar issue encountered with latexml:

• Add blog post for LaTeXML integration metanorma.org#83 (comment)

On windows important to use UTF-8 encoding in cmd. To accomplish this execute chcp 65001

But this didn't fix Jing's encoding issue either.

The only solution that worked was to skip validation (through :novalid:) entirely as done in:

• fix: temporarily disable document validation due to Jing failure on Windows #247

This task is to resolve this issue with Jing once and for all.