Org-mode feature (*bold*, /italic/, -strikeout-, _underscore_) was introduced with 5.4(?) but lead to some confusion. Misbehavior was reported in bug 105230, bug 117011, bug 123015, bug 123146, bug 124747 (quick search on BZ), as well as .
So the RFE is to disable Tools > AutoCorrect > AutoCorrect Options > Options > Automatic *bold*... by default. Should be ChangeUnderlineWeight in .
Yep, seems to be rather disruptive. Like Writer suddenly turning into a chat application
The legacy OOo era autocorrect (e.g. markdown like) feature was enriched at 5.2 with italic and strike through actions with:
What is gained by disabling by default? It is our legacy, and like most 'autocorruption' is a beloved annoyance for new users. Clearly controllable from the 'Autocorrect Options' dialog.
We just disable it by default. Doubt many Benjamin users know this kind of formatting and are surprised, see list of bugs. Plus, the autocorrection is a direct formatting that we don't want to support actually.
+1 from me.. However, last time I proposed this I was shot down.. final say was a poll bug 121377
Thanks for the notes, Telesto & Stuart. Will bring this again to the design meeting for a second decision. Poll on Twitter was 54.5% against.
Point is that people who know what it does, actually want to enabled it. So the search for it. Or this group is also being unaware of the on off switch too..
The group of people who are typing and are surprise by the effect don't know where to look..
Another point is that the on off switch is actually rather hidden from the user, IMHO. But no clue how to solve that. A paragraph style with 'markdown' enabled instead of global setting..
(In reply to Telesto from comment #6)
>... A paragraph style with 'markdown' enabled instead of global setting..
But the autocorrect applies not just to text runs in a Paragraph, but for all modules: Writer, Calc, Draw, Impress.
Only the sm Formula editor where the parser for the Command window has its own attribute syntax but should probably be tweaked to support the *bold*, /italic/, -strikeout-, _underscore_ syntax, as alternative syntax.
Would be more than a simple paragraph style to fully implement a set of Markdown syntax--for display and output processing. I guess it could be some mix of RFC 7763, and some selection from RFC 7764
(In reply to Heiko Tietze from comment #5)
> Thanks for the notes, Telesto & Stuart. Will bring this again to the design
> meeting for a second decision. Poll on Twitter was 54.5% against.
Thanks for taking it up to the design team. IMO, as you know' I believe that this function should be set as with the default of OFF, "Tools-->AutoCorrect-->AutoCorrect Options-->Options" set with these switches OFF (default)
My arguments as stated in https://lists.freedesktop.org/archives/libreoffice-qa/2020-May/010852.html still stand. There is no problem with making the feature available should the user wish to have it, but it is not a feature that should come already turned on by default and causing confusion to the user who is expecting a return of exactly what is typed. Let's not add in frustration into the suite where it can be avoided.
Let me know if you need any more input for the design team's review.
Common sense should prevail and there should be no need for a poll.
I support the idea. Although I won't call me a Benjamin user, I wasn't aware of that setting and I can imagine, that it could be very annoying.
*** Bug 133202 has been marked as a duplicate of this bug. ***
No consensus, so remains Unconfirmed while UX evaluation continues. Only then, to NEW if agreed, or WF to resolve.
(In reply to V Stuart Foote from comment #11)
> No consensus, so remains Unconfirmed while UX evaluation continues. Only
> then, to NEW if agreed, or WF to resolve.
OK, didn't know that rule
(In reply to Telesto from comment #12)
> (In reply to V Stuart Foote from comment #11)
> > No consensus, so remains Unconfirmed while UX evaluation continues. Only
> > then, to NEW if agreed, or WF to resolve.
> OK, didn't know that rule
Not so much a rule as practical, NEW implies an enhancement has been agreed to and development can proceed.
Likewise, we don't leave things as REOPENED as it is a special category for bugs or enhancements that have been deemed FIXED, either by function (WFM) or specific commit recorded to the BZ issue.
Majority votes for switching off, and we received some tickets and requests about this. So let's switch markdown off for the Benjamins. The advanced users will be able to switch it on anyway.