[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-12 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

Dieter Praas  changed:

   What|Removed |Added

 Blocks||103341
 Ever confirmed|0   |1
   Keywords||needsUXEval
 Status|UNCONFIRMED |NEW
 CC||dgp-m...@gmx.de,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org

--- Comment #1 from Dieter Praas  ---
I confirm it, but let's ask design team, if it should be changed.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103341
[Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

Heiko Tietze  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC|libreoffice-ux-advise@lists |tietze.he...@gmail.com
   |.freedesktop.org|
 Status|NEW |RESOLVED
   Keywords|needsUXEval |

--- Comment #2 from Heiko Tietze  ---
It's intended design. Autocorrection is a powerful and widely accepted
functionality. Plus, you can undo the last step to restore -Hello World- as
typed. That works for me perfectly.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

Telesto  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|WORKSFORME  |---
 CC||c...@nouenoff.nl
 Ever confirmed|1   |0

--- Comment #3 from Telesto  ---
(In reply to Heiko Tietze from comment #2)
> It's intended design. Autocorrection is a powerful and widely accepted
> functionality. Plus, you can undo the last step to restore -Hello World- as
> typed. That works for me perfectly.

* Autocorrection is a powerful and widely accepted functionality.. 
Yes, not denying that. 

* Undo resolves it
Again, true 

You're missing my point. The question: should the autocorrect while typing
change the text formatting when typing -zzz- or *zz * or /zzz/ or _zzz_ as a
DEFAULT setting.

Not everybody likes it:
https://ask.libreoffice.org/en/question/142095/how-do-i-turn-off-the-automatic-strikethrough-text/
https://listarchives.libreoffice.org/global/users/msg51099.html

And it has quite the surprise effect (huh, what's happening here).I personally
see it as a geeky feature for Power users who want this & know how it works..

It shouldn't be a out of the box experience, as it can be rather annoying and
confusing (I don't want this.. How do I disable it..

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

Heiko Tietze  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Keywords||needsUXEval
 CC|tietze.he...@gmail.com  |libreoffice-ux-advise@lists
   ||.freedesktop.org
 Status|UNCONFIRMED |NEW

--- Comment #4 from Heiko Tietze  ---
(In reply to Telesto from comment #3)
> You're missing my point. The question: should the autocorrect while typing
> change the text formatting when typing -zzz- or *zz * or /zzz/ or _zzz_ as a
> DEFAULT setting.

Okay, up to the agenda for the team meeting. My WFM position stands. 

Btw, why did you add dashes at all? I mean isn't it very unlikely that Benjamin
types *Hello*. And making this bold is not unusual.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

Xisco FaulĂ­  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org

--- Comment #5 from Xisco FaulĂ­  ---
I won't make it to the Design meeting but I agree with Heiko's POV here

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #6 from Telesto  ---
(In reply to Heiko Tietze from comment #4)
> (In reply to Telesto from comment #3)
> > You're missing my point. The question: should the autocorrect while typing
> > change the text formatting when typing -zzz- or *zz * or /zzz/ or _zzz_ as a
> > DEFAULT setting.
> 
> Okay, up to the agenda for the team meeting. My WFM position stands. 
> 
> Btw, why did you add dashes at all? I mean isn't it very unlikely that
> Benjamin types *Hello*. And making this bold is not unusual.


I should be a little more specific:

*Asterisk* 
Writing things between two asterisks enable bold. However, I used this only
sporadically and only in cases of single words. So no large surprise effect. 

However there a stylistic usages to, for example *ouch*.
Or as a marking to indicate a temporally item. Say *possible* (which is open
for change,   

So not sure if this was perfect anyway

_Underscore_
Writing a sentence or a word as as _hello_  never occurred to me (so never an
issue). Can't think of a situation right now.

/Slash/ (since 5.4)
Not run into yet. But at least problematic when typing directory's like:
/usr/john/pictures

-dash- (since 5.4)
Quite common to use. I typed multiple sentence and ended with a dash (-)..
Suddenly I got a strike-through paragraph. Not aware it typed a dash without a
space at the beginning. 
Another example: say I want to type -12-12 (outcome: -24).

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #7 from Telesto  ---
Asterisks can be used in textual media to represent *emphasis* when bold or
italic text is not available (e.g., Twitter, text messaging).

Bounding asterisks as "a kind of self-describing stage direction", as linguist
Ben Zimmer has put it. For example, in "Another gas station robbery *sigh*,"
the writer uses *sigh* to express disappointment (but does not necessarily
literally sigh).[26]

Also some models use * quite a lot. Try typing:
De heer *, wonende te *, *, geboren te * op *, houder van een *, nummer *,
uitgegeven te * op *, gehuwd*,

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

V Stuart Foote  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||5418
 CC||vstuart.fo...@utsa.edu

--- Comment #8 from V Stuart Foote  ---
If we move to adjust work done to autocorrect handling [1] and make control
more granular than simple enabled/disabled while typing or editing (Tools ->
Autocorrect -> AutoCorrect Options: Options) then would want to reopen see also
bug 115418 [2] and selectively apply STYLE or DF.

Otherwise, the current behavior is as intended, but lacks granularity.
Acceptable and => WF

=-ref-=
[1] https://gerrit.libreoffice.org/#/c/31076/
[2] https://wiki.documentfoundation.org/Design/Meetings/2018-03-21

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #9 from Telesto  ---
Alternative proposal (in case of WFM for the default question and/or the more
granular settings): make it easier to disable this feature (at the minimum for
autocorrection while typing). It's rather deeply buried in the Tools /
Autocorrect / AutoCorrect Options/ Options dialog. So rather hard to access...

A bit similar to Number recognition for tables

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #10 from V Stuart Foote  ---
(In reply to Telesto from comment #9)
> Alternative proposal (in case of WFM for the default question and/or the
> more granular settings): make it easier to disable this feature (at the
> minimum for autocorrection while typing). It's rather deeply buried in the
> Tools / Autocorrect / AutoCorrect Options/ Options dialog. So rather hard to
> access...
> 
> A bit similar to Number recognition for tables

No! The AutoCorrect options dialog is simple as can be. The entry "Automatic
*bold*, /italic/, -strikeout- and _underline_" labeling is a simple
translation. And GUI makes behavior to apply while [M] -- modify, or [T] --
typing is obvious. Moving the control elsewhere, or into Expert Configuration
would make less sense than adjusting the default state(s) to disabled.

And though I beleive we would benefit from more ambitious refactoring to
provide granularity and user selection of using Character STYLE or DIRECT
FORMATTING (as currently applied). Absent that effort, the existing control is
suitable to task.

Again IMHO => WF

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #11 from Cor Nouws  ---
I understand it is annoying. Handling various correction types different, is
strange to me. So I see it as unavoidable little collateral damage. It will
force people to look in this functional part.. Is that a pro ? :)
Anyway, for me too: WFM.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

Telesto  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #12 from Telesto  ---
Let's move on.. WFM it is. Thanks for the input everyone..

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

Heiko Tietze  changed:

   What|Removed |Added

   Keywords|needsUXEval |
 CC|libreoffice-ux-advise@lists |tietze.he...@gmail.com
   |.freedesktop.org|

--- Comment #13 from Heiko Tietze  ---
Would have asked the users (G+, Twitter) if these autoformat options should get
disabled. Expected 90% No.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #14 from Telesto  ---
(In reply to Heiko Tietze from comment #13)
> Would have asked the users (G+, Twitter) if these autoformat options should
> get disabled. Expected 90% No.

Actually, I'm still interested in the outcome.. But don't think that a survey
reaches regular users. Followers are (mostly) LibreOffice enthusiast (ergo:
mostly pro-users). But that's me being skeptic. 

To get more response from every day users some sort of push notification model
could be used. A info bar (similar to Get involved or donation bar) to inform
about a surveys with a check for open survey's similar to the auto-updater..

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #15 from Heiko Tietze  ---
Here we go

https://twitter.com/liboDesign/status/1063023582064844800
https://plus.google.com/102673546895803839652/posts/JUbGDNmeCGK

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #16 from Telesto  ---
Another suggestion, if this end up in UX Advise again.. The dialog caption
'Options' in the AutoCorrect Options should - ideally - [*strike-through
warning*] be relabelled to something more meaningful. Word calls it AutoFormat
as you Type. A little more obvious place to look, compared to non-informative
description: 'options'.

https://word.tips.net/T000636_Making_Text_Bold.html

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2018-11-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #17 from Heiko Tietze  ---
(In reply to Heiko Tietze from comment #15)
> Here we go
> 
> https://twitter.com/liboDesign/status/1063023582064844800
> https://plus.google.com/102673546895803839652/posts/JUbGDNmeCGK

Twitter 47/53%, G+ 36/64% for "Yes, change"/"No, keep" (around 100 answers;
intentionally wrote the question in a kind of double negation with Yes=Change
so some replies may have mistakenly done wrong)


(In reply to Telesto from comment #16)
> Another suggestion... relabelled to something more meaningful

You talk about the tab "Options" that collects a list of predefined, hard-coded
things together with true options and tweaking settings. Hard to believe that a
terminology change solves anything. But feel free to create a new ticket with a
proposal.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2019-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

Telesto  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||4747

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2019-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #18 from Telesto  ---
I still think this should be optimized somehow (triggered by bug 124747).

* There is a group who are running into the automarkdown feature unaware about
the existence & find it disturbing/annoying/confusing
* There is a group who loves Markdown support and want it to be enabled all the
time

Still searching for a bright idea to make everybody happy..

Would a info-bar popping up the first time when the auto-formatting gets
triggered? Something like: autoformatting is enabled by default, you can
disable it in.. or see for more info..

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 121377] Autocorrect strikeout writing convention potential for unintended changes

2019-04-15 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121377

--- Comment #19 from Heiko Tietze  ---
(In reply to Telesto from comment #18)
> Would a info-bar popping up the first time when the auto-formatting gets
> triggered? Something like: autoformatting is enabled by default, you can
> disable it in.. or see for more info..

If we'd have a balloon tip, maybe. But then people scream "clippy is back".

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs