Creating and handling fileNames.po and folderNames.po works similarly to symbolStrings.po, with the main exception that fileNames and folderNames are generated based on the pathNameTable.json instead of the library parts’ source. This also means that you need a pathNameTable.json for this to work (Creating pathNameTable.json).
If you have multiple pathNameTable.json files with different folders or file names in them, you must run the converter command separately for each one.
Run the following LP_XMLConverter command:
Windows:
<path>\LP_XMLConverter.exe pathnamestodictionary <path of pathnametable> <destination>
Mac:
<path>\LP_XMLConverter.app pathnamestodictionary <path of pathnametable> <destination>
The fileNames.po and folderNames.po files will be generated into the destination folder.
fileNames.po
fileNames.po contains the name of each library part included in your pathNameTable, and is used for translating them in the virtual file system displayed in the library part selector in each Tool Settings Dialog where a folder structure is shown (exceptions are labels, markers, and composite subelements). The translations are also applied in the Library Manager.
The raw fileNames.po file looks like this:
msgctxt "File Name"
msgid "Original File Name"
msgstr "Translated File Name"
fileNames.po works the same way as symbolStrings.po: the string translations are grouped into blocks.
msgctxt – context of the string (all of them are File Name in this case)
msgid – string to be translated
msgstr – translated version of the string
folderNames.po
folderNames.po contains the name of each folder that is used as a path in your pathNameTable, and is used for translating them in the virtual file system displayed in the library part selector in each Tool Settings Dialog where a folder structure is shown (exceptions are labels, markers, and composite subelements). The translations are also applied in the Library Manager.
The raw folderNames.po file looks like this:
msgctxt "Folder Name"
msgid "Original Folder Name"
msgstr "Translated Folder Name"
The same as fileNames.po, but here, the context (msgctxt) is always Folder Name.
Editing translations
First, creating a copy of each raw file (preferably one that reflects the language version to which the dictionary applies) is advised. Then, you can add your translations after msgstr.
Create a separate file (both fileNames.po and folderNames.po) for each language version you wish to cover in translation.