Steps To Reproduce: 1) Open an existing comma-delimited .csv file 2) Make some changes 3) Click File > Save If you open the file in a text editor, you will see that delimiters have changed from comma to fixed width. If you are editing a .csv file that will be imported into another application or database then this can cause massive problems. Tested on Ubuntu 11.10 / LibreOffice 3.4.3
NOT reproduced with LOdev 3.5.0beta2 4ca392c-760cc4d-f39cf3d-1b2857e-60db978 Ubuntu 10.04.3 x86 Linux 2.6.32-37-generic Russian UI Can you try with 3.5?
I also could not reproduce with the beta version of 3.5 but that version is not released for some time yet.
Yes, I mean beta or daily. Marked as FIXED. If you report this bug as most annoying fix may be will be ported to 3.4.6.
Opening a Comma delimited CSV in versions up to 3.5.5 resulted in the delimiter being modified to a Semicolon. In branches 3.6.x and 4.x the delimiter is modified to a Tab. This is probably related to Locale, but should NOT change the delimiter (or at least warn)
Similar issue in Mint 15, Mate. Double click on csv file, which *is* comma delimited, edit. As soon as saved, comma has been changed to tab separated. Caused havoc with a CVS repository of data, espcially in a multi platform environment. I either have to save as ods, remove the existing .csv file, then save as again to fix OR do a regex replace in vi. Using version 4.0.2.2. Linux xxxx 3.8.0-26-generic #38-Ubuntu SMP Mon Jun 17 21:43:33 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux output of locale: LANG=en_GB.UTF-8 LANGUAGE= LC_CTYPE="en_GB.UTF-8" LC_NUMERIC="en_GB.UTF-8" LC_TIME="en_GB.UTF-8" LC_COLLATE="en_GB.UTF-8" LC_MONETARY="en_GB.UTF-8" LC_MESSAGES="en_GB.UTF-8" LC_PAPER="en_GB.UTF-8" LC_NAME="en_GB.UTF-8" LC_ADDRESS="en_GB.UTF-8" LC_TELEPHONE="en_GB.UTF-8" LC_MEASUREMENT="en_GB.UTF-8" LC_IDENTIFICATION="en_GB.UTF-8" LC_ALL= Please get in contact if I can help in anyway possible - this really needs fixing or at least identifying a cause to allow a work around.
I am unable to duplicate this problem under Crunchbang 11 running TDF/LO v4.1.0.4 using Character set of “Unicode (UTF-8)” and Language of “English (Australia)”. The behaviour is the same for TDF/LO v3.5.7.2 on the same platform. Regardless of whether I use CTRL+S once the CSV is opened or File > Save As... the existing delimiters are maintained. Is it possible the problem relates to locale, language, or character set? Can others please indicate these settings on your system and/or what you are testing with?
*** This bug has been marked as a duplicate of bug 53449 ***