The problem of "DOCSTR_numbers" thing is in that these interfaces are for enUS game locale only. It can be fixed by duplicating enUS locale data to the locale similar to one used by the game client.
Here's what I did to make it work with enGB and ruRU locales:
1. Opened the UI in text module of Galaxy Editor.
2. Selected "Mod -> Locale - Modify locales" and there selected which locales i want the interface to use in addition to enUS.
3. Selected "Mod -> Locale - <enUS>".
4. Selected "Mod -> Locale - Export locales" and exported enUS locale somewhere.
5. Found the location of the exported text file and renamed it so its name ends with that locale in which need to import it. For me it was "GameStrings_enGB" and "GameStrings_ruRU".
6. Selected "Mod -> Locale - Import locales" and selected this renamed file to import to the locale I wanted.
7. Saved - the most important step which I ignored at first and had to start from the beginning :D
This helped me and made me able to use these UIs while observing with English (GB) and Russian game client languages selected :)
Oh, I didn't mention that checkbox with which locales can be viewed =)
Then enUS content just needs to be copied to other locales and DOCSTR thing should be fixed.
The problem of "DOCSTR_numbers" thing is in that these interfaces are for enUS game locale only. It can be fixed by duplicating enUS locale data to the locale similar to one used by the game client.
Here's what I did to make it work with enGB and ruRU locales:
1. Opened the UI in text module of Galaxy Editor.
2. Selected "Mod -> Locale - Modify locales" and there selected which locales i want the interface to use in addition to enUS.
3. Selected "Mod -> Locale - <enUS>".
4. Selected "Mod -> Locale - Export locales" and exported enUS locale somewhere.
5. Found the location of the exported text file and renamed it so its name ends with that locale in which need to import it. For me it was "GameStrings_enGB" and "GameStrings_ruRU".
6. Selected "Mod -> Locale - Import locales" and selected this renamed file to import to the locale I wanted.
7. Saved - the most important step which I ignored at first and had to start from the beginning :D
This helped me and made me able to use these UIs while observing with English (GB) and Russian game client languages selected :)
1v1_Launch interface works good after manipulations with locale texts (:
http://i.imgur.com/ElexKw0.jpg
Oh, I didn't mention that checkbox with which locales can be viewed =)
Then enUS content just needs to be copied to other locales and DOCSTR thing should be fixed.
Probably, by adding these strings manually for each observing tournament.
http://i.imgur.com/WNAI2xS.jpg