Created attachment 119446 [details] data files - 1 LibreOffice Calc takes more than 2 minutes to load the attached files, and, I hope one can tune the process of loading and parsing to allow for business analysis. I am hoping that the article at http://howtodoinjava.com/2013/05/27/parse-csv-files-in-java/ outlines the concept. Files originally sourced from https://www.sec.gov/.
Trying to upload the other file at https://bugs.documentfoundation.org/show_bug.cgi?id=94902 results in an error reading that the entity is too large i.e. the file exceeds the acceptable maximum size I assume even though the upload speed seems to be showing visible progress at least on this forum. You may contact the original provider of data for further details or other technical specifications that may apply.
The .txt files are tab separated data, UTF-8 encoded. num.txt loads in about 5 secs. pre.txt loads in a couple of secs. tag.txt loads in 1-2 secs and says: The data could not be loaded completely because the maximum number of characters per cell was exceeded. sub.txt loads nearly instantly. Win 7 Pro 64-bit, Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: fi-FI (fi_FI)
What file an I trying to open in this zip? Also, if there is a file that is too large please attach it to a third party (such as google drive) and then link to it. It's not sufficient to ask our team to go find the file. Marking as NEEDINFO as it's unclear what file is taking that long. Also, FWIW - usually "this file opens slow" is not enough to constitute a bug report. Do you have some reason why you think it should open faster? Does it open faster in some other software? Without indicating why you think this should be faster - the bug will likely be closed as NOTABUG as large files will obviously take a long time to parse and format correctly. If users could just say "make it faster" and that would constitute a valid bug report - we'd have thousands of such bug reports with individual large files that take awhile to open/save/etc... Please tell us what file you're referring to, link to the other document that you refer to, and explain why you think the file opens too slow (given the size, and it's not a ods file so there is some substantial parsing to be done). After doing this, please set to UNCONFIRMED. Thanks
(In reply to Jonathan Camilleri from comment #0) > [...] > I am hoping that the article at > http://howtodoinjava.com/2013/05/27/parse-csv-files-in-java/ outlines the > concept. LibreOffice is not written in Java.
I confirm what Beluga said in comment #2 but for LibreOffice 5.0.4.0+ built at home under Ubuntu 15.04 x86-64 with gcc 5.1. Best regards. JBF
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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping-20170131
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170328