You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am really enjoying this plugin for localisation! Thank you very much for it!
However, I struggled to get it up and running with a custom localisation file. It would be great to have better documentation about it, as I had to debug the code to understand how the formats and requirements for the localisation file are.
As I wish for new developers to have an easier time when integrating this tool, I would suggest to:
Explain the required format for the localisation spreadsheet: localisation strings are only parsed after a row that start with "Polyglot"/"PolyMaster"/"BEGIN".
Explain the the parsing ends when it meets a row that starts with "END".
Explain that the custom spreadsheet needs to follow the same number and order of localised languages columns as the master sheet (plugin code relies on Languages enum's int numbers to fetch the language).
Provide a template of a localisation spreadsheet that new developers can start from.
Explain that the custom sheet needs to be a publicly available Google Spreadsheet so it can be downloaded via the Editor tool.
The text was updated successfully, but these errors were encountered:
I will make this happen very soon. We just had some troubles with this ourselves internally just yesterday someone on the team noticed that half of our localization strings were missing from the game because an END keyword had been inserted in the middle with translations, so its an undocumented feature for sure :)
Hello, I am really enjoying this plugin for localisation! Thank you very much for it!
However, I struggled to get it up and running with a custom localisation file. It would be great to have better documentation about it, as I had to debug the code to understand how the formats and requirements for the localisation file are.
As I wish for new developers to have an easier time when integrating this tool, I would suggest to:
The text was updated successfully, but these errors were encountered: