Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi, can I have some help with building betas with multiple languages?

I already have one language (Simplified Chinese) fully implemented with its own font. Now, I'm working on implementing a new language which is using a different font too. (I should pick a better font for my next project lol...)

When I export a beta for the translator to check, a crash is found in a section where it forced the font to be Simplified Chinese regardless of the selected language:

AttributeError: 'StoreModule' object has no attribute 'simplified_chineseGeneralFont'

I figure it's because brunoais_tl_automenu_lang_setup.rpy in the Simplified Chinese folder is automatically excluded, so now the line to define the font for Simplified Chinese is gone, and the string complains.

Is it possible to have the option to include languages other than the defined one when exporting beta for translators who will check it?

Thank you in advance for your time!

Sorry for not replying right away but I have been thinking about your problem.

What is your use-case where you need the simplified chinese language configuration when simplified chinese text isn't included? If the language isn't included, you shouldn't be needing it, I think.

Am I missing something here?

No worries at all!

In my case, the translator credits in credit screen remain in their original languages, thus won't be translated. Simplified Chinese translator credit text stays in Chinese letters regardless of the language set. Like, for example, I set the language to English, but that particular credit text would be in Chinese, and will call the Chinese font as well.

In that case, would it work for you if TL automenu also handles the credits the same way it handles the translation menu/list?

The consequence is that for those builds, there won't be acknowledgements for the languages that aren't shipped. Does that make sense

Well, that can be a possible solution. Though I don't really understand what you meant by 'acknowledgement for the languages that aren't shipped'. Do you mean, by removing the language def in the setup file, it can also 'hide'/comment other texts that call for it as well?

Basically that. In other words, it's as if they never existed at all.

You record the credits entry or credits information just like you have the languages with their name and then that text is used for the credits and how it's used is almost the exact same way as it is now, just that the credits information is also in the translation configuration file.

I'll make that soon to show you.