Reproduction Steps
1) Create some project with a TextLabel
2) Insert a manual line break in the TextLabel text. Ex: line1\nline2
3) Play the project to force the string to be injected in the Localization Portal
4) Export it to a .cvs file (Localization | Roblox Creator Documentation)
Expected Behavior
The generated .csv file should ignore the internal line breaks of each sentence.
Actual Behavior
The internal line breaks of each sentence are being exported, which leads to corruption in the final .cvs file format.
For example, I have a lot of sentences generated within my game where I force a line break \n.
In the translation portal, this sentence appears without the line break (originally, there is a \n before the word FECHADO):
But when exporting to a spreadsheet, the line break is there, causing a corrupted file output:
The highlighted sentence above was incorrectly broken into 2 lines (because the internal \n was not removed), making it impossible to import the spreadsheet correctly.
Issue Area: Studio
Issue Type: Other
Impact: High
Frequency: Constantly
1 Like
Just to reinforce the problem reported above, it is simply IMPOSSIBLE to work with spreadsheets in the current model that is exported by Studio, when there are line breaks inserted within the text.
Studio should make some provisional adaptations before exporting, such as changing the generated CRLF characters to a string like \n.
In this way, the actual line breaks would be preserved, i.e., one line for each actual item.
Ex:
Currently, if my text has an internal line break, e.g. MyLine1\nMyLine2, Studio should NOT replace anything there and export exactly as is, ie:
,,,MyLine1\nMyLine2
But currently Studio is breaking the line at 2, generating a corrupted CSV file:
,,,MyLine1
MyLine2
After a lot of research, I managed to find a solution.
First, I highlight that the problem was with my Excel 2016, which cannot correctly interpret line breaks within texts.
I found this article that shows the solution:
Google Sheets CAN INTERPRET LINE BREAKS.
So here I will leave the step by step to make it easier for other users who encounter the same problem as me:
- In Studio, download the CSV:
- Open Google Sheets and create a new blank sheet
- Import the CSV file generated by Studio (File → Import → Upload) and select Comma as separator
- You will see that the lines are no longer incorrectly broken (as in the case of Excel 2016 that gave rise to this bug report):
- Now make all the changes you want and then (File → Download → CSV)
- Finally, just import the downloaded file back into Studio (
Update with new content from CSV).
