fix: 兼容GBK不间断空格

This commit is contained in:
2026-08-07 16:34:18 +08:00
parent 8d681118ea
commit 8a3c273a04
5 changed files with 15 additions and 4 deletions
+1 -1
View File
@@ -48,7 +48,7 @@ After the database succeeds, the same eleven result columns are uploaded as GBK
The filename time comes from normalized `metric_time`, never the server clock. If the database already contains the target time but its history CSV is missing or empty, the script exports that time from the database and repairs the history file without reprocessing source data.
All generated CSV files use GBK without a UTF-8 BOM, including the seven converted source files, the merged summary, and the uploaded history file. `manifest.json` remains UTF-8 JSON.
All generated CSV files use GBK without a UTF-8 BOM, including the seven converted source files, the merged summary, and the uploaded history file. Source non-breaking spaces (`U+00A0`) are normalized to ordinary spaces because GBK cannot encode them; other unsupported characters still fail the run instead of being silently replaced. `manifest.json` remains UTF-8 JSON.
CGI is generated with fixed rules: