After ending a sentence with '“<reference to a heading>”;' (remove the single quotation marks), the line is broken after the ending double quotation mark, but before the semicolon (which becomes alone on the new line). The last word inside the <reference to a heading> should go to the next line with the closing quotation mark and the semicolon.
I created a sample PDF that shows the 1st sentence with the error and the 2nd sentence shows how it should have been formatted by Writer.
I also attached the source ODT file for examining. The font used to format it is Merriweather Sans, which can be obtained at "https://www.fontsquirrel.com/fonts/merriweather-sans".
Steps to Reproduce:
1. Create some heading with several words. The last word should not have an hyphen (for example it should be "word" and not "hyphenated-word").
2. Create a new paragraph and type some text. For example, it could be: This is some text that goes before the cross-reference
3. Go to Menu Insert, Cross-reference, Cross-references, select the "Type" "Headings", select the "Insert reference to" "Reference", select the created heading and select the button "Insert".
4. Insert the intelligent quotation marks surrounding the cross-reference you inserted.
5. Type ";" (without the quotation marks) after the closing curly quotation mark. It should be like this: “This is the reference that will be used for the test”;
6. If the line is not broken after the closing quotation mark (”) and before the semicolon (;), type a few letters before the inserted cross-reference until the line is broken incorrectly.
The line is broken on the wrong place (after the closing quotation mark and before the semicolon).
The line break should go before the last word, which should go to the next line along with the closing quotation mark and semicolon.
User Profile Reset: Yes
Build ID: 5896ab1714085361c45cf540f76f60673dd96a72
CPU threads: 8; OS: Windows 10.0; UI render: default;
Locale: pt-BR (pt_BR); Calc: CL
Also tested with:
Versão: 126.96.36.199 (x64)
ID de compilação: 1ec314fa52f458adc18c4f025c545a4e8b22c159
Threads da CPU:8; SO:Windows 10.0; Realizador da interface: padrão; VCL: win;
Local: pt-BR (pt_BR); Idioma de IU: pt-BR
Also tested with OpenGL enabled and disabled (it happens whether always).
Created attachment 153064 [details]
PDF showing how Writer incorrectly breaks the line and how it should have been broken
Created attachment 153065 [details]
Source ODT for the attached PDF.
Comment on attachment 153065 [details]
Source ODT for the attached PDF.
It needs the font at "https://www.fontsquirrel.com/fonts/merriweather-sans" to show the bug correctly, even if there are other missing fonts.
I can't confirm it (using your document from comment 3) with
Version: 188.8.131.52.alpha0+ (x64)
Build ID: 3e64065612acec2eb29aa21e2b515953422256d7
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win;
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-08-15_22:57:26
Locale: de-DE (de_DE); UI-Language: en-US
and also not with
Version: 184.108.40.206 (x64)
CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; VCL: win;
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
(In reply to Dieter from comment #4)
> I can't confirm it (using your document from comment 3) with
Dieter, have you tried installing the font on Comment 3 or just opened the document on Comment 3?
(In reply to João Paulo from comment #5)
> (In reply to Dieter from comment #4)
> > I can't confirm it (using your document from comment 3) with
> Dieter, have you tried installing the font on Comment 3 or just opened the
> document on Comment 3?
I can't remember, but when I tried it again I got the message that extension for portugues language is missing on my system. I couldn't find an extension for LO 6. So perhaps it's not a problem of LO on general. => Component "Linguistic"
Additional information: I used Merriweather Sans.
(In reply to Dieter from comment #6)
> (In reply to João Paulo from comment #5)
> > (In reply to Dieter from comment #4)
> > > I can't confirm it (using your document from comment 3) with
> > Dieter, have you tried installing the font on Comment 3 or just opened the
> > document on Comment 3?
> I can't remember, but when I tried it again I got the message that extension
> for portugues language is missing on my system. I couldn't find an extension
> for LO 6. So perhaps it's not a problem of LO on general. => Component
João: can you tell us which pt-BR dictionary we should install?
Hi Buovjaga! I used the default Brazilian Portuguese as it is packaged on Windows Installer package (the LibreOffice_6.4.3_Win_x64.msi file).
If you want to reproduce exactly my installed LibreOffice on Windows 10, you can run the following line on Windows Command Prompt:
This is a single line and can be used for both the 32 bits or the 64 bits version of LibreOffice, and it installs everything and then remove unneeded components, so it will be left only the Brazilian Portuguese interface (you may modify the setup going to Control Panel\Add or Remove Programs to add your native language). I got this info from https://wiki.documentfoundation.org/Deployment_and_Migration#Feature and tweaked for my needs.
I can reproduce with attached ODT example in 6.4.4 RC1 (all language packs installed):
版本: 220.127.116.11 (x64)
Build ID: b50bc319eca5cd5b66fbfe2ebd0d3bd1eed099b5
CPU 线程: 2; 操作系统: Windows 10.0 Build 18363; UI 渲染: 默认; VCL: win;
区域语言: zh-CN (zh_CN); UI 语言: zh-CN
So looks like something is buggy with the Portuguese hyphenizer.
By the way I don't need to install the specific Merriweather Sans font, just adding random words earlier in the paragraph to change text length will trigger this bug.
Also reproduced with 5.2.7 (the oldest version I have installed):
Version: 18.104.22.168 (x64)
Build ID: 2b7f1e640c46ceb28adf43ee075a6e8b8439ed10
CPU Threads: 2; OS Version: Windows 6.19; UI Render: default;
Locale: zh-CN (zh_CN); Calc: group
Dear João Paulo,
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://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!