It's interesting to note that the original Korean transcription already has many errors, seemingly (and impressively) corrected by LLMs later on. For example, 12 안마당 빌드 (12 courtyard build) is actually 12 앞마당 빌드 (12 frontyard build), which might have been more understandable to BW players. Similarly 투에처리 빌드 (processing-at-two build? makes no sense lol) should have been transcribed 투해처리 빌드 (two-Hatchery build).

Therefore it may also be helpful to directly feed the slang dictionary into Whisper's inference process using contextual biasing. There are lots of ways to do this, but the simplest would be to increase the probability of slang words in the dictionary in the final prediction layer of Whisper by a constant factor. This is fairly easy to implement, for example by using HuggingFace's library: https://huggingface.co/docs/transformers/en/internal/generat...

Chatgpt and Claude did an incredible job translating the korean text:

Claude:

  Today I'll teach you about the 12 Hatchery build. I'll explain the types of 12 Hatchery builds, their advantages and disadvantages, and the build orders in a simple but detailed way.
  Against Protoss, this is the build you use when you want to start with the most economic advantage. Against Terran, there are several builds you can do with 12 Hatchery, so I'll explain some of the most commonly used builds.
  The first is the two-hatchery build that starts with 12 Hatchery:
  12 Hatchery
  11 Spawning Pool
  10 Gas
  This build uses early gas, and it's often used when you want to quickly transition into a three-hatchery build with three gas bases.
  The second build is:
  12 Hatchery
  12 Pool
  12 Gas
  This build allows for moderately fast tech tree and moderately fast three-hatchery expansion. This build is commonly known as the "safe three-hatchery" build, and you can think of it as a build that enables both quick Mutalisks and quick third base.

As the author rightly points out, in its 27 years of existence, commentary around the game has become a domain specific language. Not just Korean or English.

This approach of automated scripting and using AI to understand roughly what was said and then make it coherent is really cool.

There’s a huge amount of terms that are difficult to translate (sharding? Hash?). The only real solution is to adopt them to your language, more or less adapted, which is what happens over time. But it requires a community that, to some degree, is able to cross the gap between the languages. In this case, learning English.

Talking about software development in Spanish (my native language) is a succession of imported terms from English.

I don’t think there’s a good way of doing that, and I’m interested to see how automatic translations deal with it, because the only way this can work is with a process of mixing both language in a social way and see what terms evolve from that process.

And you need, in the terms the post describes, people that know Korean at least in a non-fluent way. And the game itself, of course.