Appearance
Getting Started
Current phase
Runtime and editor scripts now live in:
Assets/HyperMegaPixel/POLocalization/Runtime/ScriptsAssets/HyperMegaPixel/POLocalization/Editor/Scripts
Project defaults:
- Settings and temp data in
Assets/HyperMegaPixel/POLocalization/... - Runtime languages in
StreamingAssets/Languages
Configure
Use Project Settings > Hyper PO Localization to configure paths and extraction/export behavior. Use Extraction Preset to switch between different regex/raw-data configurations without losing project-specific setup.
Core references
- Documentation index:
Documentation/README.md - Quick start (EN):
Documentation/QuickStart_EN.md - Quick start (ES):
Documentation/QuickStart_ES.md - Runtime methods (EN):
Documentation/RuntimeAPI.md - Runtime methods (ES):
Documentation/RuntimeAPI_ES.md - Poedit workflow (EN):
Documentation/PoeditSetup.md - Poedit workflow (ES):
Documentation/PoeditSetup_ES.md - FAQ (EN):
Documentation/FAQ.md - FAQ (ES):
Documentation/FAQ_ES.md - Extraction attributes (EN):
Documentation/ExtractionAttributes.md - Extraction attributes (ES):
Documentation/ExtractionAttributes_ES.md
Run the sample demo
- Open
Tools/Hyper PO Localization/Samples/Install Basic Demo. - After installation, open
Tools/Hyper PO Localization/Samples/Open Basic Demo Scene. - Press Play and use the UI to switch languages, modify inventory count, and cycle dialogue lines.
The showcase scene includes:
- Context translation (
menu/Openvshud/Open) - Plural forms for inventory counts
- Formatted dialogue strings (
Bring me {0} apples.)
Regex Setup
Regex rules control how text is extracted from serialized assets:
- Built-in rules are used for known asset classes.
- Built-in defaults are intentionally Unity-focused. Add third-party/framework types with
Add Typein your extraction preset. - Per-type custom rules can override or append built-in rules.
Fallback Regex Patternsare used for other translatable asset types.Raw-Data Scan Typescontrols which asset types are parsed as serialized text.- The first non-empty capture group in each regex match is treated as the extracted string.
Use the built-in Regex Tester in Project Settings to verify and refine patterns safely. See Documentation/RegexRules.md for detailed regex recommendations and troubleshooting.