I was updating the translation files for a project I’m working on just now, and I noticed that all the translations were deleted due to a wrongly imported CSV file. After examining Crowdin’s interpretation of the new file’s table, it seems that it didn’t recognize and separate columns by commas.
For example, it would consider this as one column, and places it on the first row:
I then used an online CSV viewer and it was able to identify and separate columns just fine.
This problem only occurred to me today since I was able to update that specific file with the commas just fine a while back. Are there any solutions / workarounds?
Jumping here, @2394425147 I’ve gone ahead and activated revision history for your account from my side, you can track changes within that file by downloading previous versions. More than sure that you will find commas as a difference.
Thanks for the advise, I think it’s working again!
Turns out, in the updated table, I had extra columns in the last row, and I think the difference between the layouts messed it up. After cleaning the cells, Crowdin was able to identify the columns and rows as usual!
Another thing I looked over was that I use Unity’s localization package (v1.0.5) to export the tables, and it somehow introduces corruption when trying to overwrite existing files, so that might be it.