Here's a simple explanation of how to verify the accuracy of translated content in your local environment.
The content translated on Crowdin is in plain text format, and needs to be compiled into a .mo file for use by the program. Therefore, I also need to install a compiler. I usually use: poeditIts Pro version is subscription-based, but the basic features are free.
Once you have downloaded and installed the software, connect it to your Crowdin account, and you will be able to use it to access all the projects you are participating in on Crowdin.


Once you open the project in Poedit, it will automatically download the files from CrowdIn to your computer. This allows you to then edit and compile the translation content locally.
Also, I would like to mention that when translating files with entries containing multiple parameters, the order of those parameters is important. For example, the following will result in an error:

Compiling the .mo file is also very simple; you can just select it in the "File" menu. The only thing to note is that the filename of the compiled file should be changed to fldigi.mo.

Next, we apply the compiled .mo file to fldigi and check if our translation is correct.
First, of course, you need to download and install it. FldigiThe fldigi software itself supports multiple languages, but currently does not include a Chinese option. We can consider taking over existing language options first. The "UI language" setting can be found in the "Configure/Configure Dialog/UI/General" section, which is where you select the interface language.
Italy has long been known as "Europe's China," and I find you particularly appealing, so I choose you.

Next, we need to replace the Italian MO file with the MO file that we compiled. The file path is in the `fldigi` installation folder's `locale\it\LC_MESSAGES` directory. Place our compiled file there, and then reopen `fldigi`. Is it now showing a Chinese interface?

You can now start playing with joy!

Once the translation is further refined, we can first upload the .mo files to our own cloud storage for general users to use. After the translation rate reaches 90%, we can then apply to merge them into the code.
73