Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

Hi :)
It was Tim who offered to post the bug-report.  I am sure both Tim and
Virgil understand who your thanks are aimed at :)  Such confusions easily
arise on mailing-lists and both are very experienced with these sorts of
things.  :)

Posting a bug-report is not as difficult as it sounds.  There are various
guides and differing opinions on how to post a perfect bug-report but the
basic thing to remember is that it's always possible to add more to your
bug-report later so your first attempt does not have to be perfect, or even
good.  Also there is a team of QA personnel who help triage bugs and are
usually happy to help newbies improve their bug-reports.  After doing your
first report the documentation on how to post a perfect report might make
more sense and might help you improve yours.

The bug-report itself is much like posting an e-mail.  You just need to
write a good subject-line, maybe copy&paste the one you used for this
e-mail thread or maybe tweak it to something like "Bold stays activated
even after being switched off".

First thing is to register at the bug-reporting website.  This is the bit
that puts most people off but it's really not that tough.  You have made it
to this list and registered at Nabble so registering at the bug-reporting
place should be much easier for you.  Once you have registered it's easier
for any other issues you might spot in the future or to add helpful
comments to the bug-report that gets posted about this issue.

These guides help.  Both aim at helping you post a perfect bug-report so
don't worry too much about trying to do everything they say.  Some people
find the 1st link more useful because it's a nice pretty gui that helps
point&click users by hiding most of the options;

Other people find the 2nd link more useful for exactly the same reason (ie
that it doesn't hide anything and allows more flexibility);

If you do go for it you can always ask us for help and advice if you do get
stuck but i think you'll be surprised at how much easier it is than the
guides or reputation makes it sound! ;)
Good luck and regards from
Tom :)

On 5 November 2014 20:50, jerryvb <> wrote:

timllloyd wrote
I just did the same as Dan and got the same results. When I press
Ctrl+B at the end of a line, LO respects that choice when I get to the
next line, and doesn't apply boldface.

I did this with LO on Win7.


the fact remains that if you press enter twice (whether intentionally or
otherwise) the first blank line is bolded. From what I can see the
problem occurs between 4.2.3 and 4.2.4 (RPM version).

Jerry would you like to file a bug report? If not I am happy to jump
onto bugzilla tomorrow


Virgil, if you are willing to do that, please go right ahead. I've never
done that, so am not experienced at it. I don't mind if you do.

Thanks to everyone who verified what I was seeing. At first I just wasn't
sure if it was normal or not, but it did seem odd.

Yes, to see the problem you must press Enter two times after turning bold
off at the end of a line of bold text.


View this message in context:
Sent from the Users mailing list archive at

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.