Djihads80/Eglantine build-142

Eglantine nx2 build 142 (5eab161)

on GitHub

What's new in this build

Build 142 of nx2 (5eab161) is build 135 plus two things you can see — the Japanese UI is now fully translated, and the downloads were renamed and given a proper table — and nothing else. No emulator code changed, so no game behaves differently from build 135 and there is nothing to retest. (Builds 136–141 have no release; the numbers are CI run ids and they skip when a run fails.)

日本語: the Japanese UI is fully translated

In build 135, 853 of the 1941 translatable UI strings still fell back to English. All 853 are translated now, and the existing strings were reworded (タッチして下さい → タッチしてください, 設定完了！ → 設定が完了しました！, and so on). This only changes what you see with the UI language set to Japanese; every other language is untouched.

Downloads: stable file names and a per-platform table

The release assets no longer carry the commit sha — eglantine-linux-x86_64.AppImage, eglantine-linux-x86_64-pgo.AppImage, eglantine-windows-x86_64.zip, eglantine-windows-x86_64-pgo.zip, eglantine-macos-arm64.zip / .dmg, and so on — and the section below is now a clickable table per platform instead of a wall of install text.

The tag already identifies the build, so this makes a link like …/releases/download/build-142/eglantine-windows-x86_64-pgo.zip predictable. Anything that built a URL from the old sha-carrying name (bookmarks, scripts, package manifests) needs updating; releases published before this build keep their old names.

Qt is still 6.8.3 — the 6.12 change was reverted

PR #285 moved the Linux and MSVC Windows builds to Qt 6.12.0. It was merged into this range and reverted again before this build, so Linux and the MSVC Windows zip are built against Qt 6.8.3, exactly as build 135, and no build was ever published with the 6.12 pin. If you were waiting on that one, it is not in here.

Nothing else changed

The whole source difference between build 135 and build 142 is two files: the release workflow and dist/languages/ja_JP.ts. No emulator code, so everything that shipped in 130, 131 and 135 — the merged nx2-experimental batch, the Fire Emblem: Fortune's Weave work, the Mario Kart World command-list copies that keep the trees drawn, the Linux RAM and ASTC work, Convert to NUP — is unchanged and unaffected.

How it works, for the technically curious

• git diff build-135..build-142 touches only .github/workflows/release-binaries.yml and dist/languages/ja_JP.ts (1494 insertions, 1329 deletions).
• ja_JP.ts: type="unfinished" messages go from 853 to 0 out of 1941, with no obsolete entries — i.e. the file is complete rather than partly English.
• The workflow now strip_sha()s each artifact name at publish time and writes its notes from a heredoc through gh release create … --notes-file notes.md, which is where the table below comes from.
• Binary sizes confirm the code is the same: the linux-x86_64-pgo AppImage is byte-for-byte the same size as build 135's (138,041,848) and the Windows zip differs by 5 KB (114,441,543 vs 114,436,395) — that is translation data, not code.

Automatic build of nx2 at 5eab161.

Linux

Linux packages come as an AppImage (self-contained, needs glibc 2.39 or newer: Ubuntu 24.04, Fedora 40, Debian 13, Arch) and a tar.gz (uses your system libraries, so Qt 6 and the usual libraries must be installed).

Windows

Windows packages are in-place zip files: extract and run eglantine.exe, or eden-cli.exe from a terminal.

macOS

The PGO builds are the same programs compiled with profile-guided optimization (clang plus Eden's profile); prefer them when your CPU supports it.