Background

As the wide use of this mod in modpacks, problems have came out that most quests are hard-encoded in one language(usually English). Though i18n is available, it's sometimes annoying to use it, and it's not easy to maintain localization.

Sometimes, players don't want to know accurately what it is, but what the long descriptions are talking about. So I hope a feature could be added to betterquesting: machine translation to the current language.

Conception

As I've imagined, followed by the original text, a machine-translated text can be displayed. For quest name and questline name, they can be wrapped by brackets, and for quest/questline description, they can start with a new line.

Examples

For example(from english to simplified chinese using google translation):

1. Quest(line) name
   The beginning ---> The beginning(一开始)
2. Quest(line) description

At the beginning, you should get one wood to craft a workbench.

--->

At the beginning, you should get one wood to craft a workbench.
一开始，你应该买一块木头来制作一个工作台。

Though it's not accurate, it's enough for most players to realize what it means.

Configuration

If this feature can be added to the mod, I think it's necessary to make it able to be stopped. Also, a boolean key on whether to reverse the sequence of the original text and the machine-translated text can be added to serve people of different habit.
And for people in mainland china, if you're going to use google translation, they can only access https://translate.google.cn/. https://translate.google.com is blocked.

Great idea !!!!!!

Although BQ doesn't have auto-translations, it does support quest localisations via resource pack lang files.

@Funwayguy I know it, but many pack makers don't know it, or don't want to use it, and we've made great efforts(such as GTNH and FTBC) to push it. Also, due to the great workload of translating a whole questbook, those projects are always abandoned(such as FTBC, its chinese localization only supports 1.3.1(see its last commit). The contradiction between the lack of localizers and the need of players make this idea.

Hmm. I could probably setup some tools to manage and generate lang translations via web services but it'll be tricky to work into the legacy code and uniquely identify every entry automatically.