Current behaviour: Calc ignores a custom template set as default when opening a CSV file. Expected behaviour: When opening a CSV file and with a custom template set as default, Calc uses that custom template to display the csv file. Steps to reproduce: 1. Create a custom calc template: a. Create a new Calc file; b. Modify the default style, e.g. set a different font; c. Save the file as template using menu File -> Templates -> Save as template 2. Set as default template: -> Menu File -> Templates -> Manage, select your template, "Set as default" button. 3. Verify that Calc knows and applies the new default template: -> Close and re-open Calc. The new file should use the custom style set in step 1.c. 4. Open a CSV file with Calc. Calc won't use the custom style set in step 1.c. -> Problem! There are some workarounds (see http://superuser.com/questions/302107/how-to-set-the-default-font-in-libreoffice-calc/302133#302133 at the end), but it would be nice if Calc would apply custom templates in a consistent way.
Ubuntu 14.10 x64 LibreOffice 4.3.2.2 release Confirmed (NEW) Minor - slows down professional quality work but does not prevent it. Low - default for minor bugs. (please don't change the severity/importance without knowing what they are used for). It would be good to upload a csv file so it's faster to test this. Thanks for reporting! Indeed a little frustrating.
Created attachment 109614 [details] Example CSV file for testing Sample CSV file added to ease testing.
I can confirm that the Options > LibreOffice > Fonts doesn't respect the Font Settings for HTML, Basic and SQL Sources. Even though I've specified that Times New Roman should be used with Size = 8, it consistenly uses Liberation Sans and the result is HUGE characters. I've also tried using the Replacement Table to convert Liberation Sans to Times New Roman but this doesn't work either. In my case, I have an sql database from which I want to extract rows of data from a specific table to a csv file (there's no option for an ods file). Each day a scheduled job performs the extaction and then clears the data from the table, I open the csv and copy data for that day and 'Paste Special' without formats into an odt file which uses Times New Roman 8 point. The amount of data (columns & rows) is small so the HUGE font is not a big problem, it's just irritating. It would be much nicer if the csv file used the TNR 8 point format.
Relevant ask.lo.org questions, sometimes with workaround as proposed answer: - https://ask.libreoffice.org/en/question/3256/ - https://ask.libreoffice.org/en/question/27342/ - https://ask.libreoffice.org/en/question/108336/
This is still the case in 5.4.0.1 40m0 Though this is no major bug, it really slows down my work. (re)generating CSV files and checking them in LO (using the Reload functionality) will reset the font to something non-sensible on every reload. Could we al least have an option to NOT change the font settings on reload please?
** 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
Still present in Version: 6.0.5.2 (x64) Build-ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
Dear FS, 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
Still present in Version: 6.3.3.2 Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde5; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Using a custom template in this case is not correct. Custom template is a complete document (with full set of options available to Calc, including formatting, sheets number and *content*), that copy is used when creating a new document. It is neither applicable to opening existing documents (of any kind), nor appropriate because possible template content (values pre-existing in cells, or more than a single sheet) and formatting would not save back to the CSV - so opening a CSV with all that fancy formatting would suggest users to customize the view, save, and expect it to be kept. If one wants to have some fixed layout for a CSV, one should consider adding the CSV linked as a sheet into an ODS, being able then to apply any formatting available. The question about applicability of "Font Settings for HTML, Basic and SQL Sources" mentioned in comment 3 is different from the one raised here; it might be reasonable, but needs own proposal. WONTFIX/INVALID IMO.
Closing NOTABUG, just as tdf#131274 (see comment 10 here, and bug 131274 comment 3, for rationale). Ignoring custom template in this case is expected, normal, and not a bug (and should not be ever changed). If needed, CSV import should get more own settings, and they need to stick, which is a different issue (tdf#74580 is partially about this).
I visit this page the first time and found it very informative and useful, the way of providing details is very presentable. I usually browsing to avoid depression https://www.bestessays-uk.org/lab-report is very informative and interesting articles to make me happy and tension free.
At present, it appears that template customization is the only way of setting default styles in openoffice. This is important e.g., to add more than font customizations. For example, I need to increase padding by default. (That's how I ended up here; I don't need to customize fonts.) Saving a file as ODS (even if the CSV is linked) creates a problem. Libreoffice does not adjust column and row sizes properly when padding is adjusted, and that translates into columns and rows being too small. When an ODS file with a CSV linked as a sheet is opened, the file is outdated until it is refreshed. Column heights and widths are correct until the file is refreshed. So, either way, you need to adjust visibility settings. Methods that require opening libreoffice first are very inconvenient, because if you are e.g., processing many files in the file manager, you need to open libreoffice, find the file, and import it, as opposed to being able to just double click on it. So, I'll go back to the original question: What would be the way to customize the default style then, such that it applies to all files open, including CSV files?
In my prior comment: %s/openoffice/libreoffice/g Sorry. Old habits die hard.
(In reply to Ivan from comment #13) > So, I'll go back to the original question: What would be the way to > customize the default style then, such that it applies to all files open, > including CSV files? There will *never* be a way "that applies to all files open". Calc will always use the formatting information from file when exists. It is not going to change. The *limited* customization of CSV look and feel would be possible, as per comment 11.