Patch for LuckSystem 2.3.2 to support variable-length translations + AIR corrected-merge files (base + data)

[yoremi-trad-fr]

cd LuckSystem-2.3.2
patch -p0 < lucksystem-variable-length.patch
go build

---

lucksystem-variable-length.patch

README_GITHUB.md

INSTALL.md

FILES_MODIFIED.md

CHANGES.md

AIR.py

[wetor]

Hello, That's very kind of you, but I'm not a developer (it may seem absurd to you, but I have no knowledge of development). I used Claude AI to find and investigate bugs. I'm a visual novel translator, and it turns out that for my AIR Steam version translation project, I encountered problems when using LuckSystem. So I did my best with Claude Opus 4.5. You can add me as a collaborator if you want, I don't mind.

Yoremi

I have always wanted to use AI to fix existing issues, but the most important thing is that I currently have no games to localize, making it difficult to conduct actual testing. Untested and unstable features may cause trouble for others. As a tool serving localization enthusiasts, actual usage requirements are very important! I have added you as a collaborator. If possible, I hope you can merge these fixed changes into this repository after confirming that the functionality is normal (if you are not familiar with Git or GitHub, you can ask Claude Code to operate)

[yoremi-trad-fr]

Yes, thank you! To tell you the truth, I discovered GitHub just two months ago when I updated Rldev.
I'm a beginner, so I'll ask Claude to explain it all to me.

[yoremi-trad-fr]

Hi Wétor (I don't know where else to contact you other than here)
I'm currently porting Lucksystem to GUI,
this will be release 3 of my fork.

[wetor]

You can contact me via email (x@wetor.org).

It looks very good, but I don't recommend merging it into this repository.

I'm not sure how it's currently implemented, but I suggest that the GUI should be separated from the lucksystem executable file as much as possible. As an alternative to directly using the command line, the GUI should execute the lucksystem program through system calls, rather than embedding it into the main program code.

The primary consideration is cross-platform compatibility and code maintainability. Introducing a GUI either poses cross-platform issues (I believe a tool should at least support Windows and Linux), or it involves introducing complex frameworks, requiring effort to adapt for subsequent new features.

You can maintain a new GUI repository by yourself and include the repository link in the README of this repository.

By the way, for this PR (#35), you can click "Merge pull request" to merge the code into the main branch, and push a new tag locally to trigger an automatic build.