what is z-babel fr?

Z-Babel is a browser-based tool that makes classic text adventure games playable in languages other than English. Text adventures are story-driven games where you type commands to interact with a world, like "take lamp" or "go north." The original games were written with terse English commands in mind, which can frustrate players who prefer their own language. Z-Babel sits between you and the game, translating your natural or spoken instructions into the exact English commands the game expects, then translating the game's responses back to you. The underlying game engine is not replaced by AI. The original adventure logic runs exactly as written inside a WebAssembly build of the Frotz and Jericho interpreter. The AI layer only handles language: translating your commands, normalizing conversational phrasing into proper parser commands, handling speech input, generating spoken narration, and localizing the interface. This means the game still behaves like the original, but you can interact with it in a more natural way. Z-Babel uses a bring-your-own-key model with Google Gemini. You provide your own Gemini API key for translation, speech-to-text, and text-to-speech. Google offers a small free tier that may cover light testing. If you play in typed English, no API key is needed. The app runs entirely in your browser: there is no server backend, and your story files, saves, transcripts, map state, translation cache, and generated speech audio all stay local. The interface supports 20 target languages plus a matching set of UI locale files that switch buttons, help text, and status messages. You can save, restore, export, import, and restart games. A map tracks explored rooms, and the app keeps both an autosave and a manual checkpoint. Voice input works by holding the left Shift key while speaking or using a Speak button, with a 15-second recording limit. For developers, the project requires Emscripten, Make, and Node.js to build. The interpreter is compiled from vendored Jericho and Frotz source into WebAssembly, and a JavaScript wrapper exposes the browser API used by the app. The full README is longer than what was shown.