Created attachment 129941 [details] Text File, data width 58 bytes each line Text Import used incorrect data width in non-ascii character set. It should not be character but byte. In DBCS (Chinese, Japanese) one character used two bytes. Thank you. Text File, data width 58 bytes each line. Calc Text Import, data width 33 bytes(?) each line.
Created attachment 129942 [details] Calc Text Import wrong data width
Hello Dragon, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
No issue with fixed column import of utf-8 encoded CJK fonts with Version: 5.2.4.1 (x64) Build ID: 9b50003582f07ac674d6451e411e9b77cccd2b22 CPU Threads: 8; OS Version: Windows 6.19; UI Render: default; Locale: en-US (en_US); Calc: group Please post your sample document with the Windows-950 encoding. And personally, with that data set I would reduce the white space and use a "space" (or replacement while editing)) for delimited CSV import.
Created attachment 129955 [details] Import file (fixed width CSV) Text file for import.
Created attachment 129956 [details] Excel Text Import I can not use a "space" for delimited CSV import, because source file is fixed width. Some "space" (column) is no data, not delimitation. (Microsoft Excel correctly import this file.)
Confirmed. The "fixed width" Big5 encoded Traditional Chinese sample document, or similar in utf-8, are not correctly handled by the csvtablebox GUI. The ruler and column selection do not adjust char to handle multi-byte characters, so the column positions for the "fixed width" import is corrupt and can not be set. Actual import does honor the encoding and fielding as set--but the GUI (ruler and grid) have wrong layout so impossible to correctly set column widths. Testing on Windows 10 Pro 64-bit en-US with Version: 5.2.4.1 (x64) Build ID: 9b50003582f07ac674d6451e411e9b77cccd2b22 CPU Threads: 8; OS Version: Windows 6.19; UI Render: default; Locale: en-US (en_US); Calc: group On open into Calc, document correctly triggers Text Import dialog and is detected as Chinese Traditional and fixed width, but font encoding is initially identified as utf-8, change that to Chinese Traditional (Big5) and glyphs are correctly rendered to the GUI. =-ref-= http://opengrok.libreoffice.org/xref/core/sc/source/ui/dbgui/csvtablebox.cxx http://opengrok.libreoffice.org/xref/core/sc/source/ui/inc/csvtablebox.hxx
I don't think its anything to do with double byte fonts or encodings, just that we're assuming that the cjk font width is the same as the western font width
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The bug still present. It can be reproduced at LibreOffice version 6.1.0.3 (x64). Build ID：efb621ed25068d70781dc026f7e9c5187a4decd1
Mark Hung committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/621c189173b35ac7f5ce4c578f57045479c63ab6 tdf#104927 consider character width for CSV import It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6b768542ddd52573bbdb0e7b5b85ce5a9dd4551d Resolves: tdf#148054 Advance offset for all columns, tdf#104927 regression It will be available in 7.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-7-3": https://git.libreoffice.org/core/commit/1ec1e1b6f9353159376419d37ac8d8584312671e Resolves: tdf#148054 Advance offset for all columns, tdf#104927 regression It will be available in 7.3.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/479620d84a761297e013ca76fd429d938f3d2d8f Resolves: tdf#148054 Advance offset for all columns, tdf#104927 regression It will be available in 7.2.7. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.