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

2021-07-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

Michael Warner  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |michael.warner.ut+libreoffi
   |desktop.org |c...@gmail.com
 Status|NEW |ASSIGNED

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2021-07-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #79 from V Stuart Foote  ---
*** Bug 143296 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2021-02-09 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #78 from Mihail Balabanov  ---
For the time being, I published my workaround solution as an extension. It is a
LibreOffice Basic macro for Cycle Case which honors the selection, autoselects
only a single word when there is no selection, uses the current case of the
selected text for a starting point instead of a counter, and can cycle the case
of word the user just typed (including when there is already a space between it
and the cursor).

https://extensions.libreoffice.org/en/extensions/show/4036

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2021-02-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #77 from Heiko Tietze  ---
(In reply to Mihail Balabanov from comment #76)
> What can we, as users, do to help the developers fix it sooner?

Find a volunteer or get professional support. Changing the selection is not a
simple task and at least beyond my skills.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2021-02-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #76 from Mihail Balabanov  ---
In version 7.2, the Cycle Case command is still largely unusable for the use
cases that are important to me.

What can we, as users, do to help the developers fix it sooner?

- Is more user input needed for creating a new specification? Would it be
helpful to provide some more use cases to help decide on the best approach that
won't cause regressions for other users?

- Are the developers too few and/or too busy with more important stuff to
tackle the issue for the time being? Can we agree on a quick, minimal temporary
fix (like reverting the inclusion of Sentence Case in Cycle Case) and postpone
any functionally better but time consuming refactor (like modifying Sentence
Case or providing a separate Initial capital command, analogous to lowercase /
UPPERCASE / Title Case, to replace Sentence Case in Cycle Case) for a better
time?

- Is the issue currently considered unimportant? If yes, how can we verify
objectively that the people complaining from it are representative for a larger
group of users and not a random vocal minority as suggested several comments
above?

***

As the commenters above, I would like to thank the developers for their
tireless work on a wonderful project!

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2021-01-31 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #75 from MK  ---
Fwiw and not wishing to add to the heat generated above, as a simple user of
LibreOffice this is not expected behaviour: if I select a section of text and
conduct an operation, I expect it to be restricted to the selection.  Please
may I add my immense gratitude to all those who give their time and effort to
make this such a superb piece of software.  Thank you.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2020-12-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

Ming Hua  changed:

   What|Removed |Added

 CC||ciprian.tro...@yahoo.com

--- Comment #74 from Ming Hua  ---
*** Bug 133427 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2020-12-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

 CC||reinaldoce...@gmail.com

--- Comment #73 from V Stuart Foote  ---
*** Bug 138611 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||nikif...@mail.bg

--- Comment #72 from V Stuart Foote  ---
*** Bug 138346 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

Simon  changed:

   What|Removed |Added

 CC||simonpaulspring...@gmail.co
   ||m

--- Comment #71 from Simon  ---
Fwiw and not wishing to add to the heat generated above, as a simple user of
LibreOffice this is not expected behaviour: if I select a section of text and
conduct an operation, I expect it to be restricted to the selection.  Please
may I add my immense gratitude to all those who give their time and effort to
make this such a superb piece of software.  Thank you.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2020-06-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

Dieter  changed:

   What|Removed |Added

   Hardware|x86-64 (AMD64)  |All
Version|7.0.0.0.beta1+  |Inherited From OOo
 OS|Linux (All) |All

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2020-06-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

pgbor...@gmail.com changed:

   What|Removed |Added

 OS|All |Linux (All)
Version|Inherited From OOo  |7.0.0.0.beta1+
   Hardware|All |x86-64 (AMD64)

--- Comment #70 from pgbor...@gmail.com ---
Confirmed with:

LOdev 7.0.0.0.beta1
Build ID: 94f789cbb5b4a511c319542c7bdc31ff3b3c
Manjaro Linux
CPU threads: 4; Kernel 5.6
UI render default; VCL: kf5
Locale: pt-BR (en_US.UTF-8); UI: en-US

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2020-06-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

 CC||rohitka...@gmail.com

--- Comment #69 from V Stuart Foote  ---
*** Bug 134123 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2020-04-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #68 from Will  ---
This bug still exists.

If a user selects a piece of text, the user is giving an instruction to the
programme: "I am working with this piece of text only."

I do not understand why the programme would intentionally ignore that
instruction.

It is infuriating when, for example, Word (on Windows) selects what it thinks I
should want to select instead of what I have actually selected.

Please would someone fix this?

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2020-02-21 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

Dieter  changed:

   What|Removed |Added

 CC||ga...@currah.us

--- Comment #67 from Dieter  ---
*** Bug 130749 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2020-01-31 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

Dieter  changed:

   What|Removed |Added

 CC||ntar...@gmail.com

--- Comment #66 from Dieter  ---
*** Bug 130331 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-12-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

 CC||sdc.bla...@youmail.dk

--- Comment #65 from V Stuart Foote  ---
*** Bug 129144 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-12-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

sdc.bla...@youmail.dk changed:

   What|Removed |Added

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

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-12-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

Xisco FaulĂ­  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org
   Priority|medium  |high

--- Comment #64 from Xisco FaulĂ­  ---
Changing priority to 'high' since the number of duplicates is higher than 5 or
the number of people in CC higher than 20

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-09-07 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

 CC||j...@jfdeck.net

--- Comment #63 from V Stuart Foote  ---
*** Bug 127432 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #62 from Wolf  ---
In 
my Version: 6.2.4.2
Build-ID: 1:6.2.4-0ubuntu0.18.04.1~lo1

it is even more odd:

* put the cursor in one word - hit Shift-F3: case of that word cycles
* put the cursor in another word - hit Shift-F3: case of that word cycles, BUT
AS WELL THE CASE OF THE WORD TOUCHED BEFORE

Please repair that function, it's really important!

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #61 from V Stuart Foote  ---
(In reply to Justin L from comment #60)
> Most of the duplicates here are complaints that Sentence case was added to
> the Shift-F3 sequence in LO 6.1 
> 
> authorheiko tietze 2018-03-26 14:58:23 +0200
> commit84f8e28d092676aad830a9fbae8145a57c6301bc
> bug 116315 - Cycle Case including Sentence case
> Sentence case added at position #2 in the sequence

Well sure--it functioned as intended when only applied via menu action (now at
Format -> Text -> Sentence case). As Mike reported in OP, it was annoying then
that the transliteration did not honor a selection if made.

Addition to the Cycle Case sequence for bug 116315 brought it to a head.

Fundamentally the same issue--it does not honor Selection and expands to affect
entire sentence run. 

And, sidebar have a sneaking feeling that it is not using the ICU libs to
delimit sentence runs at correctly set bounds, kind expect CTL and CJK scripts
are not well handled but I've not dug deeply at them.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #60 from Justin L  ---
Most of the duplicates here are complaints that Sentence case was added to the
Shift-F3 sequence in LO 6.1 

author  heiko tietze 2018-03-26 14:58:23 +0200
commit  84f8e28d092676aad830a9fbae8145a57c6301bc
bug 116315 - Cycle Case including Sentence case
Sentence case added at position #2 in the sequence

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||danilog...@gmail.com

--- Comment #59 from V Stuart Foote  ---
*** Bug 124760 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #58 from Heiko Tietze  ---
(In reply to V Stuart Foote from comment #57)
> (In reply to Mike Kaganski from comment #34)
> 
> Yes, with selection made--honor the selection.

Fully agree.

> > 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.)
> 
> Hmm, looks like the TITLE_CASE transliteration has always been in the
> caserotate.cxx -- obviously it has to apply to the Word bounds, current word
> for no selection--and to all words of a selection (including the opening
> word).

We could introduce an (advanced) option "[ ] Expand selection to word
boundaries for transliteration" that changes the selection first. Looking at
Justin's patch note 

| enhance Shift-F3 rotating between UPPER, lower, Title cases. 
| - allow cursor at the beginning of the word
| - allow cursor at the end of the word
| - allow cursor in whitespace before a word 
| - rotate based on current status, not on a blind counter

supports the idea of simplification.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #57 from V Stuart Foote  ---
(In reply to Mike Kaganski from comment #34)
> 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.)

Yes, with selection of start of sentence--but not the whole run should honor
the selection--capitalize first character, the rest of the selection to lower
case per sentence case).

> 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 capitalize
> first selected character.)

Yes, with selection made--honor the selection. Capitalize the first selected
character, remainder of selection to lower case.

> 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.)

Yes, with selection made--pass exactly that string for transliteration--and
then only the TITLE_CASE would need to expand to its word bound.

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

With no selection, i.e. text cursor only, this remains the rub! But, if no
selection--should probably not apply to the whole sentence, applying just to
the word at the text cursor position would "protect" users from clobbering
things. Sentence case would then match the other transliterations.

> 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.)

Hmm, looks like the TITLE_CASE transliteration has always been in the
caserotate.cxx -- obviously it has to apply to the Word bounds, current word
for no selection--and to all words of a selection (including the opening word).

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

Needs consistency across _ALL_ modules

As a side bar to handling this--added a request for an UNO action to "Select
Sentence" as bug 124552, to more precisely select sentence via a keyboard
shortcut rather than a mouse cursor drag.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||jl...@mail.com

--- Comment #56 from V Stuart Foote  ---
(In reply to Heiko Tietze from comment #55)
> 
> Seems we agree on the required change. Cycle case should work on the
> selection and if there is none on the full sentence (as today).

OK, we should proceed--apply SENTENCE_CASE with a bimodal behavior [ selection
| no selection ].

But, Mike K's list of questions from comment 34 need a resolution. 

Also there is Justin L's work on bug 63529 and his abandoned
https://gerrit.libreoffice.org/#/c/33581/ which tweaked word boundaries and
proposed some control over the transliteration sequence depending on current
state. 

Should we address that from UX perspective--or let it be, and just be satisfied
here  with consistent "bimodal" selection handling of the fixed transliteration
sequence for caserotate.cxx, i.e.:

TITLE_CASE -> SENTENCE_CASE -> LOWERCASE_UPPERCASE -> UPPERCASE_LOWERCASE;

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

Justin L  changed:

   What|Removed |Added

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

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

Heiko Tietze  changed:

   What|Removed |Added

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

--- Comment #55 from Heiko Tietze  ---
(In reply to Philip Rayment from comment #54)
> The cycling ALREADY changes text outside the selection.  That's the problem...

Seems we agree on the required change. Cycle case should work on the selection
and if there is none on the full sentence (as today). The consideration of
automatically selection or doing nothing was misleading and might confuse
users.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #54 from Philip Rayment  ---
(In reply to Heiko Tietze from comment #53)

> > I hesitate to suggest this, but one option may be to change the process to
> > be as follows:
> > ...
> > > Third  keypress: Mary Jones met [JOE] Smith (sentence case 
> > > reverted/undone before trying next option)
> 
> Changing text outside the selection contradicts our effort. So I wouldn't
> touch "smith".

The cycling ALREADY changes text outside the selection.  That's the problem (or
one of them).  That step I was suggesting merely /reverts/ that change when
sentence case is not required.  (And it wasn't just Smith; it was also Jones.)

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #53 from Heiko Tietze  ---
(In reply to V Stuart Foote from comment #51)
> Might be cleaner to explicitly do nothing unless there is a selection made.

That would feel like a regression for people who are used to the function.

(In reply to Philip Rayment from comment #52)
> ... (maybe I missed one cycle)
> I hesitate to suggest this, but one option may be to change the process to
> be as follows:
> ...
> > Third  keypress: Mary Jones met [JOE] Smith (sentence case reverted/undone 
> > before trying next option)

Changing text outside the selection contradicts our effort. So I wouldn't touch
"smith".

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #52 from Philip Rayment  ---
(In reply to Heiko Tietze from comment #50)

> How the transliteration works is another question to me. I would keep the
> status quo which means:
... 
> ("Mary Jones met [joe] Smith" - "joe" is selected)
> TITLE_CASE: JOE
> SENTENCE_CASE: joe
> LOWERCASE_UPPERCASE: Joe
> UPPERCASE_LOWERCASE: joe

Only that's NOT the status quo, if by that you mean what happens now, and if
you're using Shift-F3 to cycle (perhaps you weren't referring to that??).  What
happens now is:

> ("Mary Jones met [joe] Smith" - "joe" is selected)
> First  keypress: Mary Jones met [Joe] Smith
> Second keypress: Mary jones met [joe] smith (sentence case applied; Jones and 
> Smith decapitalised)
> Third  keypress: Mary jones met [JOE] smith
> Fourth keypress: Mary jones met [joe] smith

I hesitate to suggest this, but one option may be to change the process to be
as follows:
> ("Mary Jones met [joe] Smith" - "joe" is selected)
> First  keypress: Mary Jones met [Joe] Smith
> Second keypress: Mary jones met [joe] smith (sentence case applied; Jones and 
> Smith decapitalised)
> Third  keypress: Mary Jones met [JOE] Smith (sentence case reverted/undone 
> before trying next option)
> Fourth keypress: Mary Jones met [joe] Smith

This would be regardless of whether a selection was made or not.  The problem
is that if the cycling is also fixed to start from the beginning of the cycle
rather than the next step after the previous when a new bit of text is
selected, the user might move the cursor elsewhere after the second step and be
stuck with the unwanted sentence case.  Although there's always the undo
button.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #51 from V Stuart Foote  ---
(In reply to Heiko Tietze from comment #50)
>
> Basically I agree with the selection on/off consideration. But how about to
> select the whole sentence first when nothing has been selected ("text cursor
> focus")? And to apply the function as it works today but always to the
> selection. It has the benefit of being more transparent to the user and
> simplifies workflow and code.
> ...

Might be cleaner to explicitly do nothing unless there is a selection made.
Making the expanded selection to sentence boundaries (from text cursor
position) would still be too late for the user to avoid an unintended action.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

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

--- Comment #50 from Heiko Tietze  ---
(In reply to V Stuart Foote from comment #45)
> To UX-Advise to move this forward...

Basically I agree with the selection on/off consideration. But how about to
select the whole sentence first when nothing has been selected ("text cursor
focus")? And to apply the function as it works today but always to the
selection. It has the benefit of being more transparent to the user and
simplifies workflow and code.

(In reply to Philip Rayment from comment #49)
>  "Mary Jones met joe Smith"

How the transliteration works is another question to me. I would keep the
status quo which means:

(without selection)
TITLE_CASE: Mary Jones Met Joe Smith
SENTENCE_CASE: Mary jones met joe smith
LOWERCASE_UPPERCASE: MARY JONES MET JOE SMITH
UPPERCASE_LOWERCASE: mary jones met joe smith

("Mary Jones met [joe] Smith" - "joe" is selected)
TITLE_CASE: JOE
SENTENCE_CASE: joe
LOWERCASE_UPPERCASE: Joe
UPPERCASE_LOWERCASE: joe

("Mary Jones met [joe Smith]" - "joe Smith" is selected)
TITLE_CASE: Joe Smith
SENTENCE_CASE: Joe smith
LOWERCASE_UPPERCASE: JOE SMITH
UPPERCASE_LOWERCASE: joe smith

Any if-then condition complicates the procedure and makes it hard for users to
predict the result.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-03-31 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #49 from Philip Rayment  ---
(In reply to V Stuart Foote from comment #47)

> No! In fact the change in comment 45 of explicitly handling selection
> state--would restore consistent and expected behavior to the UI 

Sorry, I must have misunderstood.  But please explain how this works in more
detail.  If you have this sentence:
 "Mary Jones met joe Smith"
and put the cursor in "joe", but didn't select it, and press Shift-F3 to
capitalise "joe", but you're at the wrong step in the cycle, then sentence case
is applied instead, changing "Jones" to "jones" and "Smith" to "smith".  How
does your proposal prevent that?

(In reply to V Stuart Foote from comment #47)
> ... Usage
> notes in documentation is sufficient to warn users to make a selection for
> cycling a single word.

What documentation?  Without trying an extensive search, I couldn't find any
documentation on Shift-F3 beyond it being mentioned in the menus.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-03-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #48 from V Stuart Foote  ---
(In reply to V Stuart Foote from comment #47)
Should have acknowledged that one other alternative would be to require a
selection for any of the Case rotate tranliteration to apply. Force user to
make a selection. 

Not very onerous as we select word with double click, sentence with triple
click, and paragraph with quad click. With comparable keyboard selection at
word bounds.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-03-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #47 from V Stuart Foote  ---
(In reply to Philip Rayment from comment #46)
>
> I don't know what ICU means, but if I understand you, this would make any
> use of cycling with Shift-F3 and no selection unusable.  Suppose you want to
> capitalise a single word, so place the cursor in that word but don't select
> it.  Instead of capitalising that word, you could end up applying sentence
> capitalisation to the entire sentence, an unwanted and unexpected outcome.

No! In fact the change in comment 45 of explicitly handling selection
state--would restore consistent and expected behavior to the UI and there is
only so much protection we can give to users without impacting function.
If premise remains as for bug 116315, that SENTENCE_CASE belongs in the Cycle
case list (Title Case, Sentence case, UPPERCASE, lowercase). Usage notes in
documentation is sufficient to warn users to make a selection for cycling a
single word.

Besides, this is exactly the behavior now. No selection for the other
transliterations applies just to the ICU word boundaries at text cursor
position,- while SENTENCE_CASE expands from that position to the sentence
boundaries so no regression involved.

=-ref-=
ICU -- https://en.wikipedia.org/wiki/International_Components_for_Unicode

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-03-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #46 from Philip Rayment  ---
(In reply to V Stuart Foote from comment #45)

I don't know what ICU means, but if I understand you, this would make any use
of cycling with Shift-F3 and no selection unusable.  Suppose you want to
capitalise a single word, so place the cursor in that word but don't select it.
 Instead of capitalising that word, you could end up applying sentence
capitalisation to the entire sentence, an unwanted and unexpected outcome.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-03-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org

--- Comment #45 from V Stuart Foote  ---
To UX-Advise to move this forward...

But my take remains that the original implementation applying the
SENTENCE_CASE, via ICU transliteration, needs additional control logic. 

Believe we need to handle two cases for applying SENTENCE_CASE in edit engine
[1].

1) Case -- an active selection made:

   expand only to the ICU -word boundaries- that hold the selection and apply
ICU transliteration. Treat that "temp" string as the sentence--and apply
transliteration.  Since the transliteration of the selection likely cross
sentence boundaries, would need to break selection into multiple "temp" strings
(an opening, middle(s), a closing)--but honor the selections at the word
boundaries as the range.

2) Case --  only text cursor focus, no selection made:

   expand only to the ICU -sentence boundaries- that hold the text cursor and
apply ICU transliteration.

The current implementation for sentence case always performs the expansion when
applying SENTENCE_CASE transliteration, with or without selection--that's the
issue. Current implementation probably could/should be retained for a no
selection case, but need to provide new code for the with selection handling.

=-ref-=
[1]
https://opengrok.libreoffice.org/xref/core/editeng/source/editeng/impedit4.cxx?r=492ea7e0#2665

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-03-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

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

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-03-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #44 from V Stuart Foote  ---
*** Bug 123977 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #43 from Philip Rayment  ---
(In reply to Ljiljan from comment #41)
> So honouring selection is important. We don't know what user intends to do.
> Selection helps here, not guessing. That was the point of my satire... not
> to offend everyone.
Now THAT was helpful.  I think you've made a good case for that particular
circumstance, and it's compatible with the suggestions I offered.  I do think
that honouring the selection is important; I just think that there may be
special cases where it doesn't apply.  However, honouring the selection should
be the starting point.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #42 from Philip Rayment  ---
(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.)
I'd suggest that the sentence start should be capitalised, and the rest of the
selection (not sentence) made lower case.
> 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 capitalize
> first selected character.)
I think the selection should be made lower case.  That wouldn't do anything
that selecting lower-case would do, but if that's not what the user wanted, he
would realise that the "error" is his in not selecting the start of the
sentence.  And changing the selection to lower case would give exactly the same
outcome as that portion of the sentence would have if the whole sentence had
been selected, so there is some consistency there.
I make those two comment, though, on the basis of a user selecting part of *A*
sentence.  If one selects several sentences, but only parts of the first and
last sentences, doing it this way would make it inconsistent with Capitalise
Every Word (which you do raise in Q. 5). 
> 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.)
You're still asking about sentence case?  If so, I'd treat this the same as in
my answer to question 2.
> 4. What should we do when there's no selection? We could capitalize first
> character of current word (if any; like UPPERCASE at al work); or current
> sentence. (My take is Capitalize current sentence.)
If there is no selection, like other cases, the entire sentence (in this case)
should be assumed to be selected.
> 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.)
It is in Shift+F3.  I'm undecided on this one.
> 6. Should we only do the change for Word, or for other modules
> (Calc/Impress/etc) too for consistency? (I'd say yes.)
I'd agree yes, although Calc is the only other one I use more than rarely, and
I'd rarely use these functions in Calc, so my opinion may not be worth much
here.

Your questions are good ones, and I've offered some thoughts, but I probably
haven't properly considered all circumstances, so there may be good arguments
against what I've said.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #41 from Ljiljan  ---
Let's say I start with this sentence: 

"This is my SENTENCE I wrote as an example to ILLUSTRATE the how the user might
use this function [here I intend to put a full stop after changing it to
sentence case] and THIS SENTENCE HAS NO PURPOSE AT ALL."

Now, I decide to split this into two sentences. I select this first part
expecting to change the first part of the text to sentence case, and then I
will put the full stop after "this function" part. But LibreOffice decides to
change the complete paragraph, and I did not want the second part to be
changed.

In the context of the user stories, this is a real scenario and the current
implementation does not help. 

So honouring selection is important. We don't know what user intends to do.
Selection helps here, not guessing. That was the point of my satire... not to
offend 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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #40 from Philip Rayment  ---
(In reply to Mike Kaganski from comment #36)
> (In reply to Ljiljan from comment #35)
> 
> I had decided to fix this, and so I found all relevant code and  saw the
> implementation; while thinking of possible reimplementation, I fount it
> useful to ask specific questions, so that the programming decisions would be
> clear and based on user requirements.
> 
> But now you are free to fix this yourself. I'm no more interested in this.

Mike, please don't allow one commenter to put you off this.  I didn't realise
that you were planning on fixing this, and I thought your list of questions was
just to illustrate the problems rather than seeking feedback that would be
taken into account in an actual fix.  I'll have a go at answering your
questions in a separate reply.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #39 from Philip Rayment  ---
(In reply to Ljiljan from comment #35)
> You select the text and you expect to see changes in
> the selection.
In most cases, yes, but not always.  For example, it makes little sense to
apply sentence text to only part of a sentence, especially part that doesn't
involve the start of it.  So it may not be the case you expect to see changes
only in the selection in that case.

Mike Kaganski's questions were fair, and your satire was unhelpful.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #38 from Kriton Kyrimis  ---
The way I see it, things are pretty simple: If the user selects a piece of text
and asks for something to be done with it, he expects that something to be done
with only that piece of text. If the result is not what he expected, his
reaction will be "oh, yeah, I should have made a different selection", undo the
change and try again. On, the other hand, if that something is done with other
parts of the document, the user's reaction could well be "why did this happen?
I didn't ask for this", as, e.g., with that A, signifying Amperes, in the first
comment.

Thus, if you can fix this issue, please do so, and do it in the simplest
possible way, i.e., only applying case changes in the selected text, even if it
means introducing a capital letter in the middle of a word. There is no need
for LO to try and second-guess the user.

Thanks.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #37 from Ljiljan  ---
(In reply to Mike Kaganski from comment #36)
> (In reply to Ljiljan from comment #35)
> 
> I had decided to fix this, and so I found all relevant code and  saw the
> implementation; while thinking of possible reimplementation, I fount it
> useful to ask specific questions, so that the programming decisions would be
> clear and based on user requirements.
> 
> But now you are free to fix this yourself. I'm no more interested in this.

No problem, I also stopped reporting bugs because their only purporse is to
make developer aware what makes me nervous. Their logic is always the right
one, afterall we are getting software for free so learn to live with that.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #36 from Mike Kaganski  ---
(In reply to Ljiljan from comment #35)

I had decided to fix this, and so I found all relevant code and  saw the
implementation; while thinking of possible reimplementation, I fount it useful
to ask specific questions, so that the programming decisions would be clear and
based on user requirements.

But now you are free to fix this yourself. I'm no more interested in this.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-29 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #35 from Ljiljan  ---
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.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


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

2019-01-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #34 from Mike Kaganski  ---
(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.)
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 capitalize first
selected character.)
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.)
4. What should we do when there's no selection? We could capitalize first
character of current word (if any; like UPPERCASE at al work); or current
sentence. (My take is Capitalize current sentence.)
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.)
6. Should we only do the change for Word, or for other modules
(Calc/Impress/etc) too for consistency? (I'd say yes.)

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #33 from Peter Roelofsen  ---
In reply to Mike Kaganski: thanknyou for posting some real insulting stuff. If
you tell people that they should not insultbother people, then don't insult
other people yourself. Your reply is so typical if what I call playing games by
belittling the user, it's amazing. 100 % score on the bullying scale.

Lilian summarizes it very nicely. The user is an idiot.

I'm done here. Your attitude is sickening.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #32 from Ljiljan  ---
The current "Sentence case" logic would make perfect sense in case you select
no single character and you expect to change cases of a complete sentence.
However, in the case when you invest the effort to select the part of your
text, there is no single justifiable reason to extend this to complete
sentence. So, there are no two sides to this story; just the one that is
currently implemented and the one that should be implemented (in case some
developer have time; not requesting anything because I don't use "Sentence
case" anymore or SHIFT + F3... I adjusted my behaviour with custom menus and
custom shortcuts).  

With the current implementation, we are saying: "Oh, you selected the part of
the text, but we believe you should consider the full sentence."

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #31 from V Stuart Foote  ---
(In reply to Mike Kaganski from comment #30)
+1

But the original issue as summarized in bug 119495 was clearly a duplicate of
this. 

Absent SENTENCE_CASE's default expansion of selection, adding it to the
+F3 transliteration cycling would have been a non issue.

The non-reset of the mode cycling, with a timer based patch attempt, was issue
creep--and arguable as to merit. But IMHO agree a reset upon detecting a
selection change/edit cursor movement is probably the way to normalize its
behavior.

>From UX perspective, honoring the user's selection--eliminating the legacy auto
expansion (or reduction) to work with "sentence" runs--is now more urgently
needed to close this out as efficiently as possible. 

No need/advantage to reverting bug 116315 that can't be handled with changes
needed to make SENTENCE_CASE apply to user selection, rather than to expanded
runs between "sentence" breaks as now. 

Dev choice, but the actual refactoring could be ambitious (where is it used and
should behavior be user settable in Advanced Configuration) or simple (move
SENTENCE_CASE from TransliterationModulesExtra to TransliterationModules, apply
to selection only). 

Adjust things here and you fix legitimate corruption of +F3 cycling.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #30 from Mike Kaganski  ---
(In reply to Philip Rayment from comment #29)
+1

(In reply to Peter Roelofsen from comment #28)
> Mike Kaganski: I am not insulting anybody. I feel insulted by programmes who
> refuse to consider serious error reports by competent users. And add to the
> insult by stating that tge cide is correct, implying that the users are
> stupid.

You show exactly what I said: users believe that they Hold The Truth. They
believe that they are Competent Users, and thus what they raise is Serious
Errors.

Now let's see this problem again. I reported it while back, when Shift-F3
didn't include this function yet, and so my specific bug report doesn't cover
the side effects of the inclusion of it into the Shift-F3. So I believe that
bug 119495 is another bug.

And thus let's discuss the original issue here, which both I and Peter
Roelofsen raised here and at Apache. Which is affecting what is not selected (I
don't tell about ignoring a char after full stop bit from Apache bug, which I
cannot repro, and I didn't raise here).

And so now Peter Roelofsen says: "programmes ... refuse to consider serious
error reports by competent users" - so he clearly just dismisses the others'
opinions. He mentions another opinion of Orcmid as a "proof", and treats all
others arguments as "insulting", which is clearly not constructive approach,
but a technique to make own PoV look "ultimate truth".

But the original implementation specifically made it work like that, to cover
*another user's* demand to be able to mark *parts* of sentences in
multi-selection mode, and have the *full sentences* processed. It means that
Peter Roelofsen declares that *another user* "stupid" (using his own
terminology), not the programmer who implemented that.

Note that I still consider changing the implementation to only handle selection
to be the right move; not because I suppose the implementation to be erroneous,
but because I believe that change would cover larger set of use cases, and be
more compliant with least surprise principle. But I understand that this is
arguable; and I will never dismiss another's opinion contradicting mine to be
insulting or dismissive, unless that opponent uses unfair argument
technologies. Even less will I consider insulting posts that bring the original
design bits into the discussion, which allows one to have fuller and better
understanding of the picture.

Personally I would consider the seriousness of the problem that Orcmid caller
serious as documentation problem [1], where the intended behavior of the
function is not described. And then again, this my issue is about choosing if
my suggested approach is beneficial to more users than existing approach,
nothing more.

[1]
https://help.libreoffice.org/latest/en-US/text/swriter/guide/text_capital.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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #29 from Philip Rayment  ---
> It is correct as it was implemented, and behaves programmatically as expected.
You're probably right, but the issue is what "it" is.  This bug as opened was
about how sentence case works.  The problem I see is that bug 119495 has been
closed as a duplicate of this bug, but that bug was about sentence case being
used in the Shift-F3 cycle.  So "it" now includes the latter.  Perhaps bug
119495 should not have been considered a duplicate, and should have remained
open?

> It is clear from discussion of the feature, they did not consider that the 
> SENTENCE_CASE would be added to the +F3 toggle...
And to my mind, that is the key problem, because...

> No one discounts that it has undesired effects.
... the result is not just an "undesired effect", but a situation where
Shift-F3 is largely UNUSABLE.

Perhaps the quick fix is to remove sentence case from the Shift-F3 cycle so
that that is usable again, then come to some agreement about the original issue
in this bug and how it can be incorporated into the Shift-F3 cycle without
making that unusable.

But maintaining that the way that sentence case works is arguably correct
ignores the bigger problem of the Shift-F3 cycle being unusable, and therefore
misleads as to the urgency of fixing that clear bug.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-26 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #28 from Peter Roelofsen  ---
Mike Kaganski: I am not insulting anybody. I feel insulted by programmes who
refuse to consider serious error reports by competent users. And add to the
insult by stating that tge cide is correct, implying that the users are stupid.

For a similar case, but for OpenOffice, see this discussion in the OO Issue
tracker: https://bz.apache.org/ooo/show_bug.cgi?id=119407

(Orcmid, the last person to post a comment in that discussion, was then a
senior staff member of AOO development at Apache.)

We're now several years later, right now I can't test if the bug still exists
in AOO, but I'm fairly sure that it does. I rest my case.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #27 from Mike Kaganski  ---
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 comment #21)

> 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 https://bz.apache.org/ooo/show_bug.cgi?id=113587#c5
> 
> *But 9 years on does this need revisit?* 
> 
> Maybe, since for bug 116315 we've now added the SENTENCE_CASE
> transliteration to the +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.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #26 from V Stuart Foote  ---
(In reply to Philip Rayment from comment #24)
> > So, while we may not like it--behavior could be considered correct.
> 
> No, it is NOT correct.  Repeatedly pressing F3 to get to the case you need
> *destroys* any capitalisation that already existed, and thereby makes this
> function unusable in many cases.

No one discounts that it has undesired effects. 

In comment 21 I've simply pointed to what causes users grief--noting that at
the time it was implemented in 2010, the OOo users and developers chose to
handle the SENTENCE_CASE transliteration against full sentences--expanding any
selection to the include sentence boundary.

It is clear from discussion of the feature, they did not consider that the
SENTENCE_CASE would be added to the +F3 toggle, and that users applying
it from Format menu would "only" use it rationally when they were cleaning up
blocks of text. 

It is correct as it was implemented, and behaves programmatically as expected.
It simply does not have the additional logic needed to deal with users seeking
to apply sentence case selectively--when developed they did not think it would
need it, and folks would be better served working with sentences rather than
word selections.

Since the +F3 case cycle now includes the SENTENCE_CASE transliteration,
working with selections consistently becomes more of an issue needing dev
attention to remove the annoyance.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #25 from Philip Rayment  ---
In fact, I'll repeat some steps to reproduce that I provided on that other bug:

Type the sentence "john smith and joe blow wrote to fred jones.

Now, using Shift-F3 as many times you like and selecting whatever parts of the
text you'd like, capitalise the first letter of each name, and only those
letters.
If you can do it, I'd like to know how.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #24 from Philip Rayment  ---
> So, while we may not like it--behavior could be considered correct.

No, it is NOT correct.  Repeatedly pressing F3 to get to the case you need
*destroys* any capitalisation that already existed, and thereby makes this
function unusable in many cases.  That is NOT correct.  See the extensive
discussion of bug 119495 which has now been closed as a duplicate of this one.

And please... FIX 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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

Philip Rayment  changed:

   What|Removed |Added

   Severity|minor   |normal
 CC||pjraym...@yahoo.com.au

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

--- Comment #23 from Peter Roelofsen  ---
+1 for @Mike Kaganski

Please note that most users aren't programmers. Their logic is different than
the logic of the programmers. So the question is: Whose logic is right? I'd say
that as the product is a productivity tool, the logic of the user should take
precedence over the logic of the programmer, who may not be aware how a user
may use features of the software. Anything that reduces the usability or
efficiency of a productivity tool shouod be seen as bad, a show stopper, etc.
We're not playing a game between users and programmers, and nobody should try
to win that game by inventing some "logic" so that you can maintain the status
quo and "win". Registering a bug, issue or enhancement request is a daunting
task for many users, Please remember that.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

 CC||jumbo4...@yahoo.fr

--- Comment #22 from V Stuart Foote  ---
*** Bug 119495 has been marked as a duplicate of this bug. ***

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

Version|3.5.2 release   |Inherited From OOo

--- Comment #21 from V Stuart Foote  ---
(In reply to V Stuart Foote from comment #20)

> Edit engine
> seems to expand the selection when SENTENCE_CASE transliteration is applied
> here [2].
> 
> So, while we may not like it--behavior could be considered correct.
> 

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 https://bz.apache.org/ooo/show_bug.cgi?id=113587#c5

But 9 years on does this need revisit? 

Maybe, since for bug 116315 we've now added the SENTENCE_CASE transliteration
to the +F3 cycling, meaning more folks will experience this during use.

-- 
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 49033] Change case -> Sentence case doesn't honor selection; case of entire sentence changes (STR comment 20)

2019-01-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=49033

V Stuart Foote  changed:

   What|Removed |Added

Summary|Change case -> Sentence |Change case -> Sentence
   |case doesn't honor  |case doesn't honor
   |selection; case of entire   |selection; case of entire
   |sentence changes|sentence changes (STR
   ||comment 20)
 CC||er...@redhat.com

--- Comment #20 from V Stuart Foote  ---
(In reply to Dieter Praas from comment #19)
> Can't reproduce it in

Unfortunately it remains to be fixed. And here are STR that still indicate the
string handling of selection for ICU filter is wrong:

1. new Writer document
2. add DT -> F3 autotext for the DummyText
3. select the 'h' form "him." ending the first sentence, and capitalize
4. select all but the "Him." of the first sentence "He heard quiet steps behind
"
5. cycle the applied ICU Transliteration filter with +F3

Watch it cycle. If corrected the "Him." should remain capitalized? 

Currently it still does not.  Rather, the full sentence textrun, rather than
the selection/or word, is affected upon cycling to the SENTENCE_CASE
transliteration [1].

Imagine that is caused by difference in the "default" string handling for
SENTENCE_CASE, by definition no substrings of selection/word? Edit engine seems
to expand the selection when SENTENCE_CASE transliteration is applied here [2].

So, while we may not like it--behavior could be considered correct.

=-testing-=
Windows 10 Ent 64-bit en-US with
Version: 6.3.0.0.alpha0+ (x64)
Build ID: ffa5b8a82eab18041bbee4d6914892b82c7801d3
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-12-19_03:24:54
Locale: en-US (en_US); UI-Language: en-US
Calc: CL

-=ref-=
[1]
https://opengrok.libreoffice.org/xref/core/unotools/source/i18n/caserotate.cxx
[2]
https://opengrok.libreoffice.org/xref/core/editeng/source/editeng/impedit4.cxx?r=492ea7e0#2785

-- 
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