The input field in "Insert->Object->QR and Barcode ..." does no longer allow multiple line. Only the first line from pasted text with newlines is accepted. This applies to writer and calc. Newlines where possible in version 6.4.3.
I can confirm with LO 7.4master
This seems to have begun at the below commit. Adding Cc: to Caolán McNamara; Could you possibly take a look at this one? Thanks a6ae8c042cdc21909c6786c120863c8cc4f74a07 is the first bad commit commit a6ae8c042cdc21909c6786c120863c8cc4f74a07 Author: Jenkins Build User <tdf@pollux.tdf> Date: Sat Jan 16 00:34:24 2021 +0100 source f89b94c280e8d986cdf08271f5cdc6b1dfe09575 https://gerrit.libreoffice.org/c/core/+/109310 tdf#138848 add truncate-multiline to all GtkEntries and GtkSpinButtons
IMHO, if entry fields should not have/allow multiline, the the entry field in the QR Code dialog should be replace by an text field (sorry, not sure what the proper GTK names are).
all "vcl" edits only allow one line, so the gtk ones were changed to match. So I agree with achim it needs to be a different widget is multi lines are wanted.
I think this bug is related to https://bugs.documentfoundation.org/show_bug.cgi?id=128718 ?
*** Bug 128718 has been marked as a duplicate of this bug. ***
I did prototype as a textview, but first cut looked a big ugly. I should try again
Just wanted to confirm that the problem of "only single-line QR codes" still persists in LO 7.4.3.2 on Win/x64 and give this bug a boost: To shed some light on why newlines in QR codes are important to users: When using LO to write invoices or allow for a quick donation through a SEPA direct bank transfer, it'd be awesome to be able to generate a corresponding EPC (European Payment Code; cf. https://en.wikipedia.org/wiki/EPC_QR_code ) QR code, which follows a fixed format that absolutely depends on the LF line feed (Alt+010) character to split data fields. Some banking apps will also read EPC codes using CR (Alt+013) or a combined CR/LF, but most will not. So that's one use case where LO could be one step ahead before MSO because the guys from Richmond don't get this right either (I have been discussing this, in German, on my freelance translator blog https://www.defrent.de/2021/04/eqc-qr-codes-in-ms-word/, where several more-or-less successful workarounds have been proposed by readers). Being able to piece a QR code together from Calc cells or Writer fields would further improve LO over and above the ability to manually enter a multi-line QR code, but that alone would be a real plus, given that feeding possibly sensitive and GDPR-relevant payment data should not be given to online QR image generators. Cheers, Christopher
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/11c2dae93e492442223922f621c5dafd30c99213 Resolves: tdf#146395 allow newlines in QR Codes It will be available in 7.4.4. 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.
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ebc7e13c0a79dbc5f21e78bcd9bb63a58c585f4a Resolves: tdf#146395 allow newlines in QR Codes It will be available in 7.5.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.
Hi Caolán, After you commit, the placeholder text "www.libreoffice.org" has become the default text in the text view, which changes the behaviour of the dialog. Users will have to delete it every time before adding their URL/Text. IMHO, if it's not possible to have a placeholder-text in a text-view, I would prefer not to have it as default text.
well, it is preselected, so its no great hardship to type something to replace it, but I can just as easily remove it
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6683010b1a856c3894cc0a7172ac14fda0b76aa8 Related: tdf#146395 drop default text It will be available in 7.6.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.
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-7-5": https://git.libreoffice.org/core/commit/2344f5ac296a6a29d031c6fadc67fad0523ac0e7 Related: tdf#146395 drop default text It will be available in 7.5.0.0.beta2. 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.
*** Bug 156154 has been marked as a duplicate of this bug. ***