Closed 19157681683 closed 1 month ago
It seems there is something wrong in your file.
"error": "'utf-8' codec can't decode byte 0x87 in position 10: invalid start byte"
@dosu Give me a fix based on this error
Hey @crazywoola! I'm a bot here to help you with any bugs or questions you have. Let's work together to solve this!
To resolve the character encoding issue when importing the knowledge base in batches using the specified CSV file in Dify version 0.6.11, ensure that your CSV file is saved with UTF-8 encoding. This can typically be done in most spreadsheet software or text editors by selecting the appropriate encoding option when saving the file.
Here is a step-by-step guide to save a CSV file with UTF-8 encoding in common software:
File
> Save As
.Save as type
dropdown, select CSV UTF-8 (Comma delimited) (*.csv)
.Save
.File
> Download
> Comma-separated values (.csv, current sheet)
.Encoding
in the menu bar.Encode in UTF-8
.File
> Save As
and save the file.Save As
dialog).UTF-8
encoding and save the file.Additionally, ensure that your CSV file structure adheres to the required format for batch importing in Dify. The CSV file must include columns for "question" and "answer" as specified in the Dify documentation. You can refer to the batch import section in Dify's interface for more details on the required structure.
By ensuring your CSV file is saved with UTF-8 encoding and follows the correct structure, you should be able to resolve any character encoding issues when importing the knowledge base in batches in Dify version 0.6.11 [1][2].
To continue talking to Dosu, mention @dosu.
明白了,我之前使用wps打开保存csv文件,后面使用Excel保存csv文件就可以了
Many Chinese users use WPS's Excel software instead of Microsoft's Excel software. When the front-end reads CSV files, it is better to perform encoding judgment and automatic conversion
Self Checks
Dify version
0.6.11
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Expected Behavior
answer
❌ Actual Behavior
yes