In general, I'd say that there are three different approaches to localizing Hype documents:
-
Separate .hype documents for each localization
- pros: documents are smaller, simpler solution, can change element layout per localization as much as you need
- cons: you still need some controlling document where locale is decided, you have to change all documents when there's any change you want to make
-
Separate scenes for each localization within one document
- pros: working with just one document, can reuse unlocalized content via symbols
- cons: file size/loading size is bigger, you either need to change all scenes when there's a change you want or be really smart about how you use symbols for unlocalized content
-
Same scene for all localizations, replacing strings dynamically via javascript
- pros: working with just one document, document is small, you only need to change things once
- cons: you have to store localizations somewhere, your elements need to make sure they can properly fit all localizations since you can't do different layouts, images can be a bit trickier to work with, previewing is sometimes hard
#3 is the approach that @Photics template takes. It is generally what I strive to use out of the gate, but not appropriate in all circumstances.
There's also other examples in the forums when searching for localization/translation.