[I'll attach test files after initial description] How to reproduce 1. Use file testData_3SheetsWithEmail.ods 2. Create and register datasource <testData_3SheetsWithEmail.odb> 3. Create new Writer document 4. Open datasource window, and open testData_3SheetsWithEmail.shortlist 5. Drag the following fields to the writer file: Name, Number, Postal code, Phone, Getal_StdOpmaak, Getal_GetalOpmaak Note that in the initial situation (see screen print below) all the fields have the same formatting. 6. Now select row 1 and click Data to Fields Note that fields Phone and Getal_* are displayed larger 7. Now select row 2 and click Data to Fields Note that also field Number is displayed larger. (content is now 23, was 123 b) >> All field only showing numbers, display larger
Created attachment 132926 [details] test file with description, merge fields, screen prints
Created attachment 132927 [details] spreadsheet used to create datasource
Created attachment 132928 [details] datasource from spreadsheet can maybe used, if placed in same folder as spreadsheet (I didn't check setting relative/absolute paths) If so, opening the Writer file, immediately gives the fields needed to test.
tested in Version: 5.4.0.0.alpha0+ Build ID: 74ccd02eda2d6325a27266fd935aba29b3d75020 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-04-27_23:51:14 Locale: nl-NL (nl_NL.UTF-8); Calc: group Was OK in Version: 5.4.0.0.alpha0+ Build ID: b0026125ab60d98cf6705e5d89e2f87575b5d337 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-03-21_01:15:06 Locale: nl-NL (nl_NL.UTF-8); Calc: group
Repro. "Larger" meaning that the font is different (Sans instead of Serif). Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 9348b322a5c230dfcc2231661b73e480b130fcd9 CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on April 28th 2016
thanks for confirming. Now in my situation I'm not able to adapt the field to the desired font. So that is looking rather ugly, unprofessional, in merged files.. (hint for the severity 'minor' ;) )
let me raise this one... - It turns out that also existing files with the fields have the same problem; - It is impossible to correct the problem in the file NB it is a recent problem. OK in Version: 5.4.0.0.alpha0+ Build ID: 2f5baab8498ce1303dded8aa7e16adbf80341c39 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-04-17_23:20:42 Locale: nl-NL (nl_NL.UTF-8); Calc: group
Created attachment 133226 [details] bibisect in daily Linux dbgutil bibisect repository
Working on debian-stretch in the daily Linux dbgutil bibisect repository, I see that the bug started somewhere in the 8 commits ... commit date s-h -------- ---------- -------- good 8b7f5c9c 2017-04-27 437105b9 bad b8d9ccca 2017-04-28 74ccd02e For this work, I deemed the version bad equally whether the sans-serif font shows on the first or on the second data-to-fields. I am removing keyword bibisectRequest and adding bibisected.
Regression introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=437105b940d997d742bd5e31cfa0ce4b949b29f2..74ccd02eda2d6325a27266fd935aba29b3d75020
** 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
ah how lovely - issue doesn't exist/show any more in Version: 6.2.0.0.alpha0+ Build ID: 3208fcb3a36d75d6290d9c548430682f153b09db CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-09-20_23:54:32 Locale: nl-NL (nl_NL.UTF-8); Calc: threaded