Running the pre-translate again, with the Only fill in exact matches option unchecked, it’ll have more interesting results.Īs an example, I know in my test extension, I have a field named “Decimal Places”. In my test case I’m using, I get 140 perfect matches, so my job is already 46% done now. This first pass, we’ll use the Only fill in exact matches option, then click Pre-Translate. I like to show off how clever using Pre-translate is first by using the “Exact Match” method. In my example, as soon as I open it, I know I have 0 of 300 done. This area shows you the ‘Notes’ from the XLF file, which BC generates to let you know what object/field/property is the context.Each row in section 1, when you click on that row, you’ll see matches with weighted % chances (and handy Ctrl-1, Ctrl-2, etc shortcuts) This area will show you ‘Suggestions’ from the Translation Memory.The editing area – you can manually enter/edit translations here, as well as ‘flag’ translations as “Needs work” with the toddle switch between the two.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.
0 kommentar(er)
