<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tristanscott Dev on Medium]]></title>
        <description><![CDATA[Stories by Tristanscott Dev on Medium]]></description>
        <link>https://medium.com/@tristanscott.dev?source=rss-0edccaff7151------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9gRxAEwGwsgeCsAb</url>
            <title>Stories by Tristanscott Dev on Medium</title>
            <link>https://medium.com/@tristanscott.dev?source=rss-0edccaff7151------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:48:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tristanscott.dev/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Generate PO Files for Game Localization in Unreal Engine]]></title>
            <link>https://medium.com/@tristanscott.dev/how-to-generate-po-files-for-game-localization-in-unreal-engine-4d35fe4c0dbe?source=rss-0edccaff7151------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d35fe4c0dbe</guid>
            <category><![CDATA[i18n]]></category>
            <category><![CDATA[unreal-engine-5]]></category>
            <category><![CDATA[localization-service]]></category>
            <category><![CDATA[l10n]]></category>
            <dc:creator><![CDATA[Tristanscott Dev]]></dc:creator>
            <pubDate>Sun, 07 Jun 2026 04:18:38 GMT</pubDate>
            <atom:updated>2026-06-07T04:18:38.745Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TQkKN2xFUeqJ6twlXZUcLg.png" /></figure><h3>A Guide to Getting Your Game Ready for the World</h3><p>This guide will walk through scanning your game for text and generating PO files to use for text translation.</p><h3>First Things First: What Is a PO File?</h3><p>A <strong>Portable Object file</strong> (PO) is a text file that holds translations between two languages. It is a standardized format that contains entries for each line of text to be translated. At a minimum each entry will contain a `msgid` and a `msgstr`. Translators work directly with these files, filling in the `msgstr` with the translated version of `msgid` .</p><pre><br>#: MainMenu.uasset<br>msgid &quot;Start Game&quot;<br>msgstr &quot;Démarrer le jeu&quot;<br></pre><p>Unreal Engine has strong built-in support for localization. It can collect all the text in your game, export it to PO files, and then import translations back in — all without you having to manually hunt down every string.</p><h3>The Big Picture: How It All Works</h3><p>Here’s the workflow at a glance:</p><ol><li>Gather Text ( Unreal scans your assets)</li><li>Export to PO Files</li><li>Send to Translator</li><li>Translator fills in translations</li><li>Import PO Files back into UE</li><li>Localized Game 🎉</li></ol><p>Now let’s walk through each step.</p><h3>Step 1: Mark Your Text for Translation</h3><p>Before Unreal can export anything, it needs to know <em>which</em> text should be translated. Unreal calls this <strong>“localizable text”</strong>.</p><h3>In Blueprints</h3><p>If you’re using Blueprints (Unreal’s visual scripting system), any text you display — in a UI widget, a dialogue box, a button label — should use the <strong>Text</strong> type, not the <strong>String</strong> type.</p><p>Why? Because Unreal only localizes the FText type. FString is just a raw string — Unreal won&#39;t touch it for localization.</p><p>When you create a Text variable or literal in Blueprints, you’ll notice a small icon (it looks like a tag or label). Make sure the text is <strong>not</strong> marked as “Culture Invariant” — that flag tells Unreal to skip it during localization.</p><h3>In C++</h3><p>If you write C++ code, wrap your strings in the NSLOCTEXT or LOCTEXT macros:</p><pre>// LOCTEXT takes a namespace and key<br>FText MyLabel = LOCTEXT(&quot;MainMenu_StartButton&quot;, &quot;Start Game&quot;);</pre><pre>// NSLOCTEXT is the same but you specify the namespace inline<br>FText MyLabel = NSLOCTEXT(&quot;MainMenu&quot;, &quot;StartButton&quot;, &quot;Start Game&quot;);</pre><p>Any string not wrapped in these macros won’t appear in your PO files. This is the most common reason for missing translations.</p><h3>In Data Tables</h3><p>If you store dialogue, item descriptions, or UI labels in Data Tables, make sure those columns use the <strong>Text</strong> type, not String or Name.</p><h3>Step 2: Open the Localization Dashboard</h3><p>Once your text is properly marked, you’re ready to start the export process.</p><p>In Unreal Engine 5 (and late UE4), go to:</p><p><strong>Tools → Localization Dashboard</strong></p><p>(In older versions of UE4 it may be under <strong>Window → Localization Dashboard</strong>.)</p><p>This opens Unreal’s dedicated localization interface.</p><h3>Step 3: Create a Localization Target</h3><p>A <strong>Localization Target</strong> is basically a named container for your project’s translations. You’ll usually just have one — called something like “Game”.</p><ol><li>Click <strong>Add New Target</strong> (or you may already have a “Game” target created automatically).</li><li>Give it a name (stick with “Game” unless you have a specific reason not to).</li><li>Under <strong>Cultures</strong>, add the languages you want to support. For example: en (English), fr (French), ja (Japanese).</li></ol><p>The <strong>source culture</strong> is your original language — usually English (en). The other cultures are your translation targets.</p><h3>Step 4: Configure What to Gather</h3><p>Now you tell Unreal <em>where</em> to look for text to translate.</p><p>Inside your Localization Target, find the <strong>Gather Text </strong>section. You’ll see options for gathering from:</p><ul><li><strong>Packages</strong> (your .uasset files — levels, blueprints, widgets, etc.)</li><li><strong>Metadata</strong> (asset names and descriptions)</li><li><strong>Source Code</strong> (your C++ files, for those LOCTEXT macros)</li><li><strong>INI Files</strong> (configuration files)</li></ul><p>For most games, you’ll want <strong>Packages</strong> and <strong>Source Code</strong> enabled. Make sure the paths point to your project’s content and source directories.</p><p>Click <strong>Gather Text</strong> when you’re ready. Unreal will scan everything and build a list of all the localizable strings it finds.</p><h3>Step 5: Export to PO Files</h3><p>After gathering, you’ll see a count of how many strings were found. Click <strong>Export to PO</strong> (or simply <strong>Export</strong>, depending on your UE version).</p><p>Unreal will generate one PO file per language, saved to your project’s localization folder:</p><pre>YourProject/<br>  Content/<br>    Localization/<br>      Game/<br>        en/<br>          Game.po       ← source strings<br>        fr/<br>          Game.po       ← empty (waiting for translations)<br>        ja/<br>          Game.po       ← empty (waiting for translations)</pre><p>The en/Game.po file contains all your source strings. The other folders contain PO files with the msgid fields filled in but empty msgstr fields — those are the blanks your translator will fill in.</p><h3>Step 6.a: Send to Your Translator</h3><p>Hand the PO files for each target language to your translator (or translation service). They can open PO files in free tools like <a href="https://poedit.com/"><strong>POEdit</strong> </a>— a simple, purpose-built editor that makes translation easy even for non-technical people.</p><p>Your translator sees a clean list of source strings and fills in the translations one by one. When they’re done, they save the file and send it back to you.</p><h3>Step 6.b: Use an Unreal Compatible Localization Provider Plugin</h3><p>Unreal provides an option to directly use a localization provider plugin to automatically generate localized text using an external automation service.</p><p>The <a href="https://www.fab.com/listings/0a9158c9-0854-4b8d-ab41-3a2b11bf5ffd">Syntactic Text Localization</a> Unreal Plugin can automatically translate 32 different languages.</p><p>Once you have downloaded the plugin and enabled it , you can select it from the Localization Provider dropdown and use it to Auto-generate the translations. An example video translating English to Spanish can be found <a href="https://www.youtube.com/watch?v=kCVfkq9ixpo">here</a>.</p><p>As your game grows, so does your text. A Localization Provider keeps your translation data in sync with that growth, letting you spot and fix layout or formatting problems without burning a translator’s time ( and budget ) on a build that isn’t ready.</p><h3>Step 7: Import the Translations Back</h3><p>Once you have your translated PO files back, drop them into the correct folders (replacing the empty ones), then go back to the Localization Dashboard and click <strong>Import from PO</strong>.</p><p>Unreal reads the files and compiles everything into its own internal binary format (.locres files). These are what the engine actually uses at runtime — the PO files are just the human-readable exchange format.</p><p>Click <strong>Compile</strong> if Unreal doesn’t do it automatically.</p><h3>Step 8: Test Your Localization</h3><p>To test a specific language in the editor:</p><p>Go to <strong>Edit → Editor Preferences → Region &amp; Language</strong> and change the <strong>Preview Game Language</strong> to your target language. Then hit Play.</p><p>Alternatively, you can launch your game with a command-line argument:</p><pre>YourGame.exe -culture=fr</pre><p>This forces the game to start in French (or whatever culture code you pass in).</p><h3>Common Gotchas (And How to Avoid Them)</h3><p><strong>“Some of my strings aren’t showing up in the PO file.”</strong> Double-check that you used FText and not FString. Also verify your gather paths include all your content directories.</p><p><strong>“The translation isn’t showing up in-game even after importing.”</strong> Make sure you clicked <strong>Compile</strong> after importing. The engine uses compiled .locres files, not the raw PO files.</p><p><strong>“My UI still shows English.”</strong> Confirm the widget text is using a Text variable, not a hardcoded String. Also check that the text node isn&#39;t set to &quot;Culture Invariant.&quot;</p><p><strong>“The translator says the context doesn’t make sense.”</strong> PO files include metadata about where each string came from (the asset name and key). If your keys are auto-generated gibberish, add a proper <strong>Text Key</strong> comment in your Blueprint or a meaningful namespace in your C++ macros. This helps translators understand the context of each line.</p><h3>A Note on Text Keys and Namespaces</h3><p>Every localizable string in Unreal has three parts:</p><ul><li><strong>Namespace</strong> — a broad category (e.g., MainMenu, InventoryScreen)</li><li><strong>Key</strong> — a unique identifier within that namespace (e.g., StartButton, ItemDescription)</li><li><strong>Source String</strong> — the actual text (e.g., “Start Game”)</li></ul><p>Good namespaces and keys make translator’s lives much easier, especially for large games with thousands of lines. Take a few minutes to set these up thoughtfully — you’ll thank yourself later.</p><h3>Wrapping Up</h3><p>Generating PO files for Unreal Engine localization is less scary than it sounds once you understand the pieces:</p><ol><li>Mark your text as localizable (FText, proper widget types)</li><li>Open the Localization Dashboard and create a target</li><li>Configure your gather sources</li><li>Gather text, then export to PO</li><li>Send to translator, get back translated PO files</li><li>Import and compile</li><li>Test in-editor or via command line</li></ol><p>The PO file format is a battle-tested, widely understood standard that keeps developers and translators working in their own comfort zones. Unreal’s tooling around it is solid — once you’ve run through it once, it becomes a routine part of your release pipeline.</p><p>Now go make your game speak every language it deserves to.</p><p><em>Have questions or ran into a specific issue? Drop a comment below — happy to help.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d35fe4c0dbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>