[Libreoffice-bugs] [Bug 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Wed Jan 30 06:46:40 UTC 2019


https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #35 from Ljiljan <lilicus at gmail.com> ---
I just find it funny that we invest so much energy in something that just
cannot be user's logic. You select the text and you expect to see changes in
the selection.    

My following reply should be considered only as the purpose to illustrate how
far we can go regarding this issue (my answer are written as satire just to
illustrate how pointless this can be). We don't have empirical evidence to
support which logic is right, but current logic "selection -> only selection
changes" make more sense than "selection -> both selection and the text until
the next full stop".    

(In reply to Mike Kaganski from comment #34)
> (In reply to V Stuart Foote from comment #31)
> 
> Let's discuss the details :-)
> 
> 1. What should be done when a sentence start is selected, but not to the
> sentence end? (I'm pretty confident the sentence start here should be
> capitalized.)

Maybe changes should be extended to all sentences in the document, and all
sentence starts should be capitalized because that is what the user wants since
he/she selected the beginning of the sentence. In case he/she wanted to select
only the current sentence, then he/she should select the current sentence.
Otherwise, he /she indicates that the start of the sentence is important and it
should be changed consistently in the document. No, the user did not select
this part of the text (sentence start) expecting it to be changed, he/she was
expecting more! 

> 2. What should be done if a sentence end is selected, but not from start?
> (This one IMO is not that straightforward: we can capitalize the first
> selected character, or we may skip the sentence; my take would be capitalized> first selected character.)

The first next sentence should be capitalized, but also it should recommend
capitalizing all other sentences in the following paragraph. After all, the
user did not intend to capitalize this sentence since he/she did not select it
from the beginning. No, the user did not select the sentence end expecting it
to be changed, he/she was expecting more!   

> 3. What should be done if selection starts in the middle of a word (possibly
> not the first in a sentence)? We could capitalize first character of the
> word (again not good for Shift+F3); or first selected character; or skip the
> sentence. (I'd capitalize first selected character.)

In this case, we should you SpellCheck to see it this word exists in our
dictionary. The user is probably not sure about the selection of the word
(maybe he/she wrote "upcoming", but now considering only using "coming"). No,
the user did not select this part of the text expecting it to be changed,
he/she was expecting more!


> 4. What should we do when there's no selection? We could capitalize first
> character of the current word (if any; like UPPERCASE at al work); or current
> sentence. (My take is Capitalize current sentence.)

This is a special case where we should use AI to detect eyes movement in order
to detect sentence user would like to capitalize. 

> 5. What should be done with Capitalize Every Word function, that now also
> expands to whole words, even if only parts are selected? It's not in
> Shift+F3 IIUC, but it would become inconsistent. (I'd say change it
> consistently.)

I don't understand this, but AI might help here too. 

> 6. Should we only do the change for Word, or for other modules
> (Calc/Impress/etc) too for consistency? (I'd say yes.)

Definitely. Impress would be great since people use bullets, no full stops, so
this will capitalize only first bullet, and the other points would be lower
case... One slide should look like a long sentence! The same applies to Calc.
Maybe all sentences in one column can be changed to make it look consistent! Or
row. Not sure anymore!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20190130/c085afc2/attachment.html>


More information about the Libreoffice-bugs mailing list