Firmware Programmer for updating Language table using POEdit and PO/POT files

This is not a programming project more of a formatting project but a firmware developer may be very familiar with the process from working on devices sold internationally. We need someone to take our language table in excel and create the PO files. I have pasted more information regarding the project below. Our table has 9 languages with 60 or so terms so I am assuming we need 9 PO files but I am a marketing guy so I am not 100% on what needs to be done. I have copied the procedure below. Please only apply if you are familiar with this. In order for you to complete the translation work, someone there must use the translations from the .xls Language Table and merge them into the POT/PO file format. The proper instructions for doing this are as follows: TRANSLATIONS For language translations, we use GetText PO (Portable Object) files which is an internationalization and localization (i18n and l10n) system commonly used for writing multilingual programs. Files: POT – Portable Object Template. This is the file that you will get when we extract the strings from a project (see attached). This is also the file you will send to translators. PO – Portable Object. This is the file you should receive back from the translators. It’s a text file that includes the original strings and the translations localized to the specific country and language. It should be kept on your end so when I send a new POT file, you will merge the POT file with the existing PO file. MO – Machine Object. This is the “database” used to look up strings on a machine level and return the translation, if any. We use the GetText utility that extracts all the strings from our code and places them into a POT file. When starting a new translation, the translators will start with the POT file and end up with the PO file that gets sent back to me. I then converted the PO file into a MO file. The MO file is then added to the next release and loaded onto the machine to be used when its language is selected. I still have to review the translations in the PO file to make sure the translations follow our character and line limitations for our displays. If I do have to tweak the PO files, I always send the fixed PO back to you so you can replace your copy with the fixed version. When updating existing translations, the translators should take the latest PO file for the country and language to be translated and use the POT file to update the English strings. The translator will then have to go through the translations and make sure the existing translations are still accurate as well as translate any new strings. Since PO / POT files are so popular, there are several excellent tools for translating them. The best known tool, also free, is a program called POEdit. www.POEdit.net. It will take the POT file and merge the difference with an existing PO file or generate a new one if none exist. When merging, it highlights the differences between the PO and POT file and shows what has changed and what still needs to be translated. Translators: Download POEdit from the following link: [login to view URL] 1. Open POEdit 2. File -> New a. Select the language code for the country that you are translating for (ex: Polish (Poland)) b. Click OK 3. Catalog -> Update from POT File… a. Browse to and select the [login to view URL] file that was emailed from programmer. b. Ignore catalog modified warning by clicking Don’t Save. 4. Translate each line as appropriate. 5. Click Save (please name file to match the language it is translating) 6. Email the PO file that was just saved. NOTE: this process must be repeated for each language.