<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=49033#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=49033">bug 49033</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>Please refrain from insulting others by declaring someone is "playing games" and "tries to win", without even carefully reading what has been said (let alone understand): (In reply to V Stuart Foote from <a href="show_bug.cgi?id=49033#c21">comment #21</a>) > Seems this was intentional to "keep it simple by just capitalizing the first > letter or each sentence", and so temporarily expand selection(s) to the full > sentence for applying the transliteration. > > see <a href="https://bz.apache.org/ooo/show_bug.cgi?id=113587#c5">https://bz.apache.org/ooo/show_bug.cgi?id=113587#c5</a> > > *But 9 years on does this need revisit?* > > Maybe, since for <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Cycle Case does not use Sentence case or tOGGLE cASE" href="show_bug.cgi?id=116315">bug 116315</a> we've now added the SENTENCE_CASE > transliteration to the <Shift>+F3 cycling, meaning more folks will > experience this during use. Secondly, what users like to call "programmer's logic" is always another user's logic, which happens to not fit you, but that was adopted by programmer as an implementation specification. This reflects multitude of ways anything may be used, and there's no way to please everyone. This is what users refuse to accept when they insist that their "logic" (in this context it's the way they use something) is universal. Yes, programmer's choice of specification may be bad in the sense that it doesn't reflects the majority's use case, but that needs proving, and it's not easy (in bug reports, you always see the PoV of those who disagree with the status quo, and those who agree are Just happily use it and don't visit bug reports). In this case, my "logic" (as user who filed the report, also being a developer) differed from the "logic" adopted by the feature author, who considered multiselection usecase (which I didn't), but didn't consider normalizing pasted chunks of text that had bad case in the source (where author's presumptions doesn't hold). Now that the feature started to be used in a scenario not meant initially, this became more important.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>