D&D Translations

Hi everyone,
Here is a rare example of someone who uses D&D Beyond but isn't a native English speaker. I do have a few questions, though; since I believe D&D Beyond is moving in the right direction, I would love to see a clearer structure and more transparency for us non-English-speaking users.

1. As I’ve mentioned before: I would really welcome a multi language version of D&D Beyond—as would many players I know personally.
2. It would be great to be able to choose the language of the books—at least for those that are already translated into the so-called FIGS languages.
3. I would like to be able to combine digital content with books in my own language so I can enjoy the same benefits.

My English is not too bad, but in a game that relies heavily on conversation, it can sometimes be difficult to translate terms on the fly—especially when it goes beyond the 1,500 most common words (and believe me: D&D goes far beyond that). I know that—as with all business matters—it ultimately comes down to money, but I would appreciate it if you could consider this point.

I believe that was one of the things they were trying to address with some back end work they are still working on. They didn't say it outright, as I remember, but they were looking into expanding language options by inserting mechanisms that would allow that. It was on a Reddit AMA from a few months ago. I can't seem to find the thread to link it. sorry.

My experience with adding I18N to software is that doing it the first time is a big job. The problem is that D&D Beyond isn't just a stream of text, it's a bunch of formatted text, and thus you need to tokenize everything that might be translated, and have your layout manager swap in the translations (either on the fly, or as saved pages).  There are additional challenges if they're trying to translate to languages with a different orientation, such as Arabic, but I don't think they are. If they have already translated books that will eliminate the need to re-translate, but not the need to set up the code to allow translation to work or to assign the correct translations to the correct tokens. This is a large amount of fairly simple but tedious work, and if they're in the process of rebuilding their backend, not something you'd do on your legacy system because then you wind up throwing away all the work you did in six months or something.