Created attachment 148755 [details] CSV Datasource file and screenshot Steps to reproduce: * Create new OpenDocument Text document * Open the document with LibreOffice Writer * View data sources (View -> Data Sources) * Clean up data sources as necessary (Context Menu -> Registered databases ... -> Delete -> Yes -> OK) * Attach data source * Open Fields dialog (Insert -> Field -> More Fields ...) * Select Mail merge fields (Database -> Mail merge fields) * Add database (Add database file -> Browse...) * Select the attached CSV file (Database.csv) * Adjust row format: Field separator: ; Text separator: " Decimal separator: , Thousands separator: . Ensure "Text contains headers" is selected Character set: Unicode (UTF-8) * Click OK * Expand the added database "Datasource" * Expand the table "Datasource" The first field, EMail, is shown as "EMail" (with quotes) whereas FieldNameAndAddress, Surname and all other following fields correctly do not contain the quotes. The "bad" field "EMail" seems to be working when using as mail merge field, but is now incompatible with documents created with an older version of LibreOffice (I have not checked since which version the break occurs), as the quotes were not present before. The problem does not occur if all quotes in the header line in the CSV file are removed.
Created attachment 148768 [details] file encoded utf8-bom i noticed attached file is encoded with utf8-bom. could you please check, if it works if you use utf-8 instead?
Created attachment 148770 [details] insert_fields_db_encoded_utf-8 for me, it seems to work with utf8 and Version: 6.1.5.1 (x64) Build ID: f18954c1ba9116b85c32b6bdbc0188d3e0fd24c7 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: group threaded
Hello! Thank you for the quick response. Removing the BOM in the datasource file fixes the problem. But shouldn't it also work with BOM? Regards, Dominik
(In reply to Dominik Hölzl from comment #3) > Removing the BOM in the datasource file fixes the problem. > But shouldn't it also work with BOM? Menu File/New/Database Wizard has no option to select encoding. and changing encoding later via Tables/CSVDataBase/context menu/ Database/Properties... from "System" to "Unicode (UTF-8)" does not work (EMail, is shown as "EMail" with quotes) according to: Bug 115056 - FILESAVE: Calc doesn't write CSV as UTF-8 Bug 82254 - FILESAVE: UTF-8 BOM removed from CSV when saving file BOM get lost during save but opening your BOM *.csv with calc is fine with selected enconding "Unicode (UTF-8)". IMHO this can be seen as a bug.
Dear Dominik Hölzl, 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 https://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
Andreas Heinisch committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/aa69f2a176329795fad957ac639329307c146e58 tdf#123055 - Start to read unicode text in order to avoid the BOM It will be available in 7.3.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.