Better Way to Handle Localization?
#1
Is there a way to split up large language files?
I have a large addon, and it'd be nice to have settings.po, connection_wizard.po, notifications.po, errors.po, etc. This reminds me of the nightmare of resx resource files that are 2000 entries and a nightmare to edit, manage, and correlate to the relevant code. It could work something like getLocalizedString('connection_wizard', 32015) or something. Personally, the concept of binding resource strings to an integer is a pain to begin with. Fast, but a pain. I would really prefer to do something like getLocalizedString('connection_wizard.ip_address') or getLocalizedString('error.connection_failed_header'). My real question is, "Is there a way to more easily handle hundreds of localized strings than a single strings.po file referenced by ambiguous integer IDs that may conflict with other parts of Kodi other addons?"
Developer for Shoko and Nakamori. Long time user of Kodi, before it was even called Kodi. My XBOX died long ago, but Windows is still just as broken and necessary. I obviously watch anime, given my first comment. Video games, manga, music, you name it.
Reply
#2
Short answer, no
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#3
Fun. I don't want to wrap my own, but it's becoming more trouble than it's worth for my case to use Kodi's built in localization.

Sure, I'm fine with hard coding strings, but I'm not the only dev....
Developer for Shoko and Nakamori. Long time user of Kodi, before it was even called Kodi. My XBOX died long ago, but Windows is still just as broken and necessary. I obviously watch anime, given my first comment. Video games, manga, music, you name it.
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
Better Way to Handle Localization?00