|
105 | 105 | "name": "What delimiter and encoding does it expect?", |
106 | 106 | "acceptedAnswer": { |
107 | 107 | "@type": "Answer", |
108 | | - "text": "It defaults to standard comma-separated values, and the OnlyOffice import lets you choose a different delimiter or text encoding if your file needs it." |
| 108 | + "text": "Comma, semicolon or tab are detected automatically, and so is the encoding: UTF-8 (with or without BOM), GB18030 / GBK for Chinese ANSI exports, and Latin-1 as the last resort." |
| 109 | + } |
| 110 | + }, |
| 111 | + { |
| 112 | + "@type": "Question", |
| 113 | + "name": "My CSV shows garbled characters (mojibake) in other tools — will it here?", |
| 114 | + "acceptedAnswer": { |
| 115 | + "@type": "Answer", |
| 116 | + "text": "Usually not. Mojibake means the file was saved in a legacy code page (GBK / GB18030, Latin-1) and opened as UTF-8. This converter sniffs the bytes first, so Chinese exports from Excel open correctly, and saving writes UTF-8 with a byte-order mark that Excel reads without a wizard." |
109 | 117 | } |
110 | 118 | }, |
111 | 119 | { |
@@ -244,9 +252,10 @@ <h2>How it works</h2> |
244 | 252 | <p> |
245 | 253 | The conversion is handled by OnlyOffice's x2t engine compiled to WebAssembly, which targets the common office |
246 | 254 | and text formats — Word, Excel and PowerPoint plus PDF, TXT, HTML and CSV. Because it runs in the browser tab |
247 | | - there is no upload queue and no server-imposed size cap, and your data never touches the network. It defaults to |
248 | | - comma-separated values, and the import step lets you pick a different delimiter or text encoding — and mark |
249 | | - number, date or text columns — before you save the result as XLSX. |
| 255 | + there is no upload queue and no server-imposed size cap, and your data never touches the network. The delimiter |
| 256 | + (comma, semicolon or tab) and the text encoding are detected automatically — strict UTF-8 first, then GB18030 |
| 257 | + (the "ANSI" encoding Excel uses for Chinese exports), then Latin-1 — so files that show mojibake elsewhere open |
| 258 | + with the right characters here. Mark number, date or text columns in the sheet, then save the result as XLSX. |
250 | 259 | </p> |
251 | 260 |
|
252 | 261 | <p> |
@@ -279,7 +288,14 @@ <h3>Will number and date columns be detected?</h3> |
279 | 288 | </p> |
280 | 289 | <h3>What delimiter and encoding does it expect?</h3> |
281 | 290 | <p> |
282 | | - Standard comma-separated values by default; the import lets you pick a different delimiter or text encoding. |
| 291 | + Comma, semicolon or tab are detected automatically, and so is the encoding: UTF-8 (with or without BOM), |
| 292 | + GB18030 / GBK for Chinese "ANSI" exports, and Latin-1 as the last resort. |
| 293 | + </p> |
| 294 | + <h3>My CSV shows garbled characters (mojibake) in other tools — will it here?</h3> |
| 295 | + <p> |
| 296 | + Usually not. Mojibake means the file was saved in a legacy code page (GBK / GB18030 for Chinese, Latin-1 for |
| 297 | + Western European) and opened as UTF-8. This converter sniffs the bytes first, so Chinese exports from Excel |
| 298 | + open correctly, and saving writes UTF-8 with a byte-order mark that Excel reads without a wizard. |
283 | 299 | </p> |
284 | 300 | <h3>Does the converter work offline?</h3> |
285 | 301 | <p>Yes. Once loaded it is an installable PWA, so it keeps working with no internet connection.</p> |
|
0 commit comments