5/28/2023 0 Comments Poedit add source key![]() ![]() 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. Add the Translation Files from the BC DVD to Poedit’s memory.Wow! Double wow! Quick Summary (step by step below): There also other ways to notify contributors, described hereĪfter reviewing the changed strings, contributors can use the Toggle Fuzzy Translation button ( F button next to the translation) in the Translations page to remove the fuzzy flag.One handy tip I was given by Gregory Alekseev over on Twitter was to use Poedit ( Download here) to edit my translation files. They can easily order the translations by fuzzy first or choose to see only these translations using the filters at the top of the Translation page. Use it to let contributors know about the changes, and tell them to review the fuzzy translations in the languages they are assigned to. In the Project page, there is a Notify Contributors button. How to notify contributors about changed strings To update the string in the Default Reference Language in the same page, hover your mouse over the label, press T to see the translations in all the languages, click on the string you want to change and edit it. This will put a fuzzy flag on the translations in all the languages. Don't change the label, and leave the box under it that says "Set all translations as fuzzy" checked. Go to Terms, search for the key of the string you want to change, then press Save. You can also edit strings in the Default Reference Language manually, one by one, and set their corresponding translations as fuzzy. How to update strings in Default Reference Language in the Terms page If you use the import in the Translations page corresponding to the source language, choose that you want to overwrite old translations and to mark corresponding translations from the other languages as fuzzy for the updated values (this option will allow you to track the strings that need to be updated in the other languages. How to update strings in Default Reference Language using the language import Checking this option, you'll be able to track the changed strings that will need to be updated in the target languages.Īfter hitting Import File, you'll be able to delete obsolete terms (terms which are no longer in the file, but are still in the project). If you use the import in the project page, choose to Also import translations in…, select the Default Reference Language (English in the screenshot), check the box to overwrite old translations, and then select the option to mark corresponding translations from the other languages as fuzzy for the updated values. How to update strings in Default Reference Language using the project import To update changed values in the Default Reference Language, follow the steps below. ![]()
0 Comments
Leave a Reply. |