Bug 65944 - punctuation after inline formula may go to the next line
Summary: punctuation after inline formula may go to the next line
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.5.2 release
Hardware: Other All
: low trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Paragraph
  Show dependency treegraph
 
Reported: 2013-06-19 18:14 UTC by Yury
Modified: 2023-06-10 03:14 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
formula followed by comma immediately - bad flow (11.46 KB, image/png)
2013-06-19 18:14 UTC, Yury
Details
demo (11.91 KB, application/vnd.oasis.opendocument.text)
2014-11-16 14:35 UTC, Yury
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yury 2013-06-19 18:14:32 UTC
Created attachment 81080 [details]
formula followed by comma immediately - bad flow

It's possible for punctuation (dot or comma) following the inline formula frame to be reflowed to the next line [Proofpic]. This should never happen, formula frame (any frame, even?) should count as a word.
Comment 1 Yury 2014-11-07 16:54:19 UTC
I still get this problem in 3.6.7.2 from time to time. Very annoying as to fix one bad placement of punctuation I often have to edit 1-2 lines leading to it.

Difficult to reproduce but should be findable promptly in line breaking routines or whatever those are called - formulas (objects) count as  words (aren't breakable), but punctuation isn't counted as "trailing" those words.
Comment 2 Buovjaga 2014-11-16 13:58:27 UTC
Please attach a test document, so it's faster for QA to test.
Change back to UNCONFIRMED after you have provided the document.
Comment 3 Yury 2014-11-16 14:35:40 UTC
Created attachment 109555 [details]
demo

Oh, all right, I'm attaching one. Everything in the file is done in MS 'Times New Roman'. On my linux system I have comma (with no space before it) on the next line.
Comment 4 Buovjaga 2014-11-16 15:29:06 UTC
(In reply to Yury from comment #3)
> Created attachment 109555 [details]
> demo
> 
> Oh, all right, I'm attaching one. Everything in the file is done in MS
> 'Times New Roman'. On my linux system I have comma (with no space before it)
> on the next line.

Confirmed on Windows and Ubuntu.

Win 7 64-bit Version: 4.4.0.0.alpha2+
Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08

Ubuntu 14.10 64-bit Version: 4.4.0.0.alpha2+
Build ID: 3cf226622a3d8c09d655034dbcc81695f1662b87
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-15_23:24:22
Comment 5 Yury 2015-04-27 08:22:26 UTC
BTW, such cases aren't registering in the 'Find' functionality, when searching for regexp '^\,'.
Comment 6 QA Administrators 2016-09-20 09:32:13 UTC Comment hidden (obsolete)
Comment 7 Yury 2016-09-20 16:33:07 UTC
Still reproducible with the attached ODT and 
Version: 5.2.1.2
Build ID: 31dd62db80d4e60af04904455ec9c9219178d620
CPU Threads: 2; OS Version: Linux 4.4; UI Render: default; 
Locale: ru-RU (en_GB.UTF-8); Calc: group
Comment 8 Regina Henschel 2017-02-05 13:32:14 UTC
This is a special case of the more general bug 65323.
Comment 9 QA Administrators 2018-02-06 03:27:47 UTC Comment hidden (obsolete)
Comment 10 Yury 2018-02-07 03:58:12 UTC
Issue still there.

Version: 5.4.4.2
Build ID: 2524958677847fb3bb44820e40380acbe820f960
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2;

Version: 6.0.0.2
Build ID: 06b618bb6f431d27fd2def25aa19c833e29b61cd
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2;
Comment 11 QA Administrators 2019-02-08 03:51:32 UTC Comment hidden (obsolete)
Comment 12 Yury 2019-02-08 11:57:06 UTC
Still there in 6.2.0 release, with every accessible VCL.

Version: 6.2.0.3
Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: qt5; 
Locale: ru-RU (en_GB.UTF-8); UI-Language: en-US
Calc: threaded
Comment 13 QA Administrators 2021-06-09 03:47:45 UTC Comment hidden (obsolete)
Comment 14 QA Administrators 2023-06-10 03:14:26 UTC
Dear Yury,

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!

Warm Regards,
QA Team

MassPing-UntouchedBug