{"id":32,"date":"2025-06-23T13:27:01","date_gmt":"2025-06-23T13:27:01","guid":{"rendered":"https:\/\/blogs.scummvm.org\/prime\/?p=32"},"modified":"2025-06-23T13:27:01","modified_gmt":"2025-06-23T13:27:01","slug":"week-3-titanic-tetraedge-and-a-sea-of-strings","status":"publish","type":"post","link":"https:\/\/blogs.scummvm.org\/prime\/2025\/06\/23\/week-3-titanic-tetraedge-and-a-sea-of-strings\/","title":{"rendered":"Week 3: Titanic, Tetraedge, and a Sea of Strings"},"content":{"rendered":"

This week was quite busy and eventful! I had my keymapper implementations for the Supernova<\/strong><\/a> and Voyeur<\/strong><\/a> engines successfully merged, and I also completed keymapper support for Titanic<\/strong> and Tetraedge<\/strong>. In addition, I took on an extra task to help normalize all keymapper action descriptions across the project.<\/p>\n

\n

Titanic: The Most Challenging Engine So Far<\/h3>\n

Out of all the engines I\u2019ve worked on so far, Titanic<\/strong> has definitely been the most complex.<\/p>\n

Implementing the keymapper took me about four days<\/strong>, most of which were spent trying to understand how input was being handled. Unlike other engines, Titanic processes input through a system of “messages.” Key presses are encapsulated in these messages and passed around to various components that need to handle input. This indirect approach made the input flow harder to trace.<\/p>\n

Even though I\u2019m still not 100% confident I fully understand every detail of the mechanism, I eventually got the keymapper working by mimicking how raw keycodes were originally processed<\/strong>. After two days of reading and experimenting, things finally started to click \u2014 and from that point on, it was just a matter of replacing keycodes with action-based mappings and writing the action bindings.<\/p>\n

\n

Tetraedge: The Easiest One Yet<\/h3>\n

In contrast to Titanic, Tetraedge<\/strong> was a breeze. The engine only uses three keys and mouse input, so I was able to wrap up the keymapper integration in half a day<\/strong>. Always nice to have a quick win!<\/p>\n

\n

Action Label Normalization: A Multilingual Cleanup<\/h3>\n

ScummVM\u2019s GUI is actively translated into many languages by the community using Weblate<\/a>. Weblate automatically picks up strings that are explicitly marked for translation in the code.<\/p>\n

To reduce the translators’ workload, it’s important that identical strings are reused consistently across the codebase. Weblate treats strings with even minor differences \u2014 like different capitalization \u2014 as separate entries. Unfortunately, over the years, different contributors have used varying styles (sentence case, title case, etc.) for keymapper action descriptions.<\/p>\n

To help streamline translations, I went through and normalized 1100+ action labels<\/strong> to follow sentence capitalization. The task itself wasn\u2019t difficult, but it was quite repetitive. Fortunately, sev<\/strong> helped by providing a git grep<\/code> and awk<\/code>-based workflow that made identifying and editing the labels much faster. With that in place, I was able to get through the normalization process much more efficiently.<\/p>\n

\n

Wrapping Up<\/h3>\n

This week, I:<\/p>\n

    \n
  • \n

    Got my Supernova<\/strong> and Voyeur<\/strong> keymapper PRs merged \ud83c\udf89<\/p>\n<\/li>\n

  • \n

    Implemented full keymapper support for Titanic<\/strong> (the hardest one so far)<\/p>\n<\/li>\n

  • \n

    Added keymapper support to Tetraedge<\/strong> (the easiest one yet)<\/p>\n<\/li>\n

  • \n

    Normalized 1100+ keymapper action labels<\/strong> for consistent translations across the GUI<\/p>\n<\/li>\n<\/ul>\n

    Next week, I plan to keep the momentum going and tackle keymapper support for more engines. With each engine, I\u2019m getting a better understanding of the diverse input systems in ScummVM\u2014and figuring out how to adapt the keymapper to each one\u2019s quirks.<\/p>\n","protected":false},"excerpt":{"rendered":"

    This week was quite busy and eventful! I had my keymapper implementations for the Supernova and Voyeur engines successfully merged, and I also completed keymapper support for Titanic and Tetraedge. In addition, I took on an extra task to help normalize all keymapper action descriptions across the project. Titanic: The Most Challenging Engine So Far […]<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-32","post","type-post","status-publish","format-standard","hentry","category-week-3"],"_links":{"self":[{"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/posts\/32","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/comments?post=32"}],"version-history":[{"count":2,"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/posts\/32\/revisions"}],"predecessor-version":[{"id":34,"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/posts\/32\/revisions\/34"}],"wp:attachment":[{"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/media?parent=32"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/categories?post=32"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.scummvm.org\/prime\/wp-json\/wp\/v2\/tags?post=32"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}