{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreica7fhfjzgc7aw6wwi2y4qlzrnlv3pcdcl2jvm6ouwdjkgekw6xly",
    "uri": "at://did:plc:ldoygu7hgowosknnh3w7hczb/app.bsky.feed.post/3mf6kmlmwndk2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreifkkixgoxxly4q3a34qypzy4kjv7yop2egx2wejqzbt6zm53gqrkm"
    },
    "mimeType": "image/webp",
    "size": 8094
  },
  "path": "/menu-translation-and-propagation-while-translating/",
  "publishedAt": "2026-02-18T05:54:00.000Z",
  "site": "https://whateverthewindbrings.com",
  "tags": [
    "semantic formula"
  ],
  "textContent": "One of the defining features of working with menus is, usually, the repetition. I mean, yeah, item and skill lists don't repeat and can be a real pain to translate, but when you get to descriptions and effects, you can use a \"semantic formula\" to keep it all following the same structure, no matter how the source looks. If you do your homework and start adding terminology to the Term Base with the proper settings, it gets even better, as the CAT Tool will try to scramble sentences together using information that had human input while replacing the terminology the TB has.\n\nWhat this means is: it gets really easy to autocomplete boring and repeatable structures using inputs and information you have complete control over, which can speed up the process or, at least, make it easier than retyping whole sentences again and again to fix minor differences. It's easier to propagate, and there's less chance of a big screw-up if you need to do a mass replace. You _know_ the text, you _know_ the structure, and you _know_ the terminology, so any issue can be dealt with before it propagates even further through the project.\n\nYou know what can't do that? \"AI\" and machine-translated content. Since everything is already \"translated\" through means the translator has no control over, they have to edit line by line, because mistakes are already propagated and it's dangerous to make a mass replace not knowing which lines it can affect. And fixing a badly-translated project (which is what \"post-edition\" really is) takes way, way more time than translating something _correctly_ right from the start and fixing mistakes as soon as they show up.\n\nWith a neatly organized project, with a good project manager, good guidelines, and good teamwork, a translation can actually go faster _and_ keep a high-quality without having to pay pennies to an overworked translator rushing to make an overnight delivery.\n\nThat is, of course, assuming that the people paying for the job want their intellectual property handled with care.",
  "title": "Menu translation and propagation while translating",
  "updatedAt": "2026-02-18T06:01:19.659Z"
}