Thank you for your interest in contributing!
Language files live in the lang/ folder as .psd1 files.
- Fork this repository
- Copy
lang/en-US.psd1tolang/YOUR-CULTURE.psd1- Example:
lang/ja-JP.psd1for Japanese,lang/ar-SA.psd1for Arabic - Use the standard Windows culture code (language-REGION)
- Example:
- Translate all values — keys must remain in English
- Open a Pull Request with title:
[Lang] Add ja-JP translation
The launcher (launch.ps1) and all scripts auto-detect the system language via (Get-UICulture).Name.
If your culture code is not in the supported list, add it to the $_supported array in each script.
Use lang/en-US.psd1 as your translation template. Every key must be present.
Open an Issue with:
- Your Windows edition and build number
- Which script you ran (
win11_HOME,win11_LTSC, etc.) - What happened vs what you expected
- Attach the log file from your Desktop (
win11_HOME_YYYY-MM-DD_HH-mm.txt)
- Open an Issue first describing the bug
- Fork and apply your fix
- Pull Request must reference the Issue:
Fixes #123 - Include the Windows edition and build you tested on
Open an Issue with tag [Feature Request].
New features are implemented by the maintainer — suggestions are welcome and will be evaluated.
- PowerShell scripts must run as SYSTEM via PowerRun
- All user-facing strings must use
$Lang.KeyNamefrom.psd1files - Technical log messages (while script runs) stay in English
- Test on real hardware before submitting
- Direct pushes to
main— all changes go through Pull Requests - Changes to
.ps1logic without an associated Issue - New features without prior discussion
Maintainer: Dedo
Project: github.com/DedoOS-win/Titanium-OS-Suite