![]() ![]() It should show your Destination language from the XLF. The main window is columns of Source and Target.(I might recommend this XLIFF Sync extension if you don’t already use it) Simple do File -> Open to open your XLF file. You’ll need to create the XLF file for your project and target language. If all goes well, your Stored Translations should jump by over 40,000. Select the XLF file from BaseApp you located earlier and it’ll take a bit to import the translations. (You can find use for the Import from TMX and Export to TMX functionality to share a prepared Memory Database with coworkers, perhaps?). But, the more vital part, we can Manage the memory database.įor now, we’ll make use of the Import translation files… option. Then, change tabs to Translation Memory and you should see something like so:įor me, I’d uncheck the Use suggestions from online collaborative TM setting, as I’m not using Pro. Under the File menu, you’ll want to Select Preferences. In my examples below, I’ll use Swedish (for my region).īack in Poedit, we’ll see the initial starting screen: Extract the language(s) you need and pop the XLF file you need somewhere you can find. For example, in the 16 CU3 BC On Prem installer, the BaseApp source is located in a collection of ZIP files inside Applications\BaseApp\Source. You’ll want to fetch the Translation source files from the BC DVD. Easy enough – leave it open and we’ll come back to it. ![]() The installation is super simple, just Terms and no options. Poedit is open source (there’s a Pro version you can use to hook into online services) and free to use for commercial purposes. Add the Translation Files from the BC DVD to Poedit’s memory.Wow! Double wow! Quick Summary (step by step below): One handy tip I was given by Gregory Alekseev over on Twitter was to use Poedit ( Download here) to edit my translation files.
0 Comments
Leave a Reply. |