It appears CALC is doing that 'Linuxy' thing where certain /cr /lf (0x0D;0x0A) combinations are changed to plain /lf - thereby corrupting the the integrity and sort-order of text-fields in a DBF file.
Steve, Can you be more precise please : 1) Give a step by step instruction as to how to reproduce. 2) Provide a sample file or files (DBF in this case containing the crlf characters). 3) Indicate whether this used to work in previous versions of LibreOffice or OpenOffice.org. Thanks, Alex
Created attachment 57840 [details] Corrupted memo field See record #3
Thanks Steve, I will look at this when I've got a minute or two. Alex
(In reply to comment #3) > Thanks Steve, I will look at this when I've got a minute or two. > > Alex Hmmm, unfortunately, on my Mac, I don't have any Russian codepage support, so can't not open the file in any meaningful form. I tried opening in UTF-8 and got a string of JP characters which didn't help much. Will have to try on another OS. Alex
But attached files have no Russian text inside. How to open attached fpt file in LO? I do not know. But problem is there.
(In reply to comment #2) > Created attachment 57840 [details] > Corrupted memo field > > See record #3 KEY,N,4,0 DATA,M 1 apples bananas 2 lemons peaches 3 libre office
(In reply to comment #6) > (In reply to comment #2) > > Created attachment 57840 [details] > > Corrupted memo field > > > > See record #3 > > KEY,N,4,0 DATA,M > 1 apples > bananas > 2 lemons > peaches > 3 libre > office Checked with: LO 3.5.5.3 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Anything wrong with that data?
Not my day... I am sorry for bugnoise. After saving as dbf and reloading I got: KEY,N,4,2 DATA,M 1,00 2,00 3,00
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO