Excel File Translation Upload Error
dxdx123 opened this issue · comments
Describe the issue
There is an issue with uploading translations in the Excel file. If there are more than 4 entries, the translation cannot be uploaded, and an error message appears stating that the translation content cannot be found. Format:
source:
{"desc_list":[{"title": "基础规则","rows":["活动中，传说角色的单次邂逅出率为2%","在任意邂逅活动中，每邂逅1次，累计1次全局保底计数，全局保底计数达到100次时，<style=yellow>必定随机获得1名当期活动中的传说角色</style>。获得任意传说角色时，全局保底计数将被重置（当前全局保底：<style=yellow>{count}</style>次内必得随机传说角色）"]}]}
target:
{"desc_list":[{"title": "基本ルール11","desc":"【常設出会い】では現在実装済みの全てのキャラクターと出会う可能性があります"}]}
I already tried
- I've read and searched the documentation.
- I've searched for similar filed issues in this repository.
Steps to reproduce the behavior
Upload Excel
Expected behavior
No response
Screenshots
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
5.3.1, 5.5.5
Weblate deploy checks
No response
Additional context
No response
What error do you get exactly? Is some additional info available in Weblate logs?
This issue has been marked as a question by a Weblate team member. Why? Because it belongs more to the professional Weblate Care or community Discussions than here. We strive to answer these reasonably fast here, too, but purchasing the support subscription is more responsible and faster for your business. And it makes Weblate stronger as well. Thanks!
In case your question is already answered, making a donation is the right way to say thank you!
What error do you get exactly? Is some additional info available in Weblate logs?
When uploading 4 items：Processed 4 strings from the uploaded files (skipped: 4, not found: 0, updated: 0).
When uploading more than 5 items：Processed 23 strings from the uploaded files (skipped: 0, not found: 22, updated: 0).
After further investigation, it was found that the parsing of the csv file was abnormal and the header of the excel file was not parsed normally.
Seems like CSV dialect detection in confused by the data. We should have a way to skip that detection in this case.
Thank you for your report; the issue you have reported has just been fixed.
- In case you see a problem with the fix, please comment on this issue.
- In case you see a similar problem, please open a separate issue.
- If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.
Thank you for your report; the issue you have reported has just been fixed.
- In case you see a problem with the fix, please comment on this issue.
- In case you see a similar problem, please open a separate issue.
- If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.