Scene context
The system knows where a string lives and the boundary, anchor, and function around it.
Game-engine infrastructure
The Arabic branch of localization engineering.
Arabic did not need more translation inside the engine. It needed an engineering branch connecting language to scene context, layout, behavior, and validation.
One pipeline
Geb is the mother tool. One platform, one engineering context.
Geb unifies the internal modules that connect language, scene, space, layout, review, and memory. The component architecture remains inside Geb rather than appearing as disconnected products.
Parent tooling platform
Geb
Geb unifies the internal modules that connect language, scene, space, layout, review, and memory. The component architecture remains inside Geb rather than appearing as disconnected products.
- Language and bidirectional-text normalization
- Scene intelligence and spatial validation
- Right-to-left layout logic
- Visual review and evidence
- Translation memory and evaluation
Roles are described at a high level. Integration details and interfaces are available through qualified technical review.
Inside the engine
See the difference between a late fix and native infrastructure.
Move the control to compare a build that breaks direction, text, and space with one that understands Arabic inside the system itself.
Broken build
Sahure layer
Why engine-native
The defects visible in the interface begin before the image.
Traditional testing reacts to the final result. Native infrastructure operates on data, context, and layout before the issue becomes another manual ticket.
Earlier detection
Direction, clipping, and expansion are exposed before the build reaches expensive manual QA.
Repeatable validation
Checks can run after every change instead of rediscovering the same class of defect.
Traceable evidence
Each decision connects back to the string, scene, and rule that produced it.
The architecture was designed for the most complex RTL case.
That engineering foundation can extend into additional RTL languages, with Urdu identified as the next expansion path.
Arabic inside the engine. Not after it.
Live demonstrations and integration documentation are available to qualified studios and technology partners.