If I try to select a single phrase using a triple click, I need to have an uppercase character after the punctuation signal. Otherwise, the selection loses the stop point and keep going on to the followed phrases. I think you can use this paragraph to test:
Hello, this is a simple paragraph test. did you realize that we begun this second phrase with a lowercase character? and here again! now I guess you have a good paragraph to test what I'm trying to say.
Try, please, to click over each one of the phrases in the paragraph above and you will understand my point. At least I hope so! Please, check that with some pontuation signals the selection works perfect. But not with all of them.
modified summary notes.
tested under Win7 64bit with different LibO releases.
triple click selection has the same behaviour at least up to 3.3.3 (but I suppose it has always been like that).
for the moment I'll label it as NEW but I'm tempted to label it as NOTABUG since it's caused by incorrect ortography from the user...
AFAIK in every language the "." should alway be followed by a capital letter.
adding Writer expert to CC list to let him decide about it.
I understand... but when you say the "." should always be followed by a uppercase letter, I think you should say the ".", the "!", and the "?" should always be followed by a uppercase letter. However, the problem occurs only with the ".". So, at a minimum, this behaviour looks a little inconsistent.
As an additional observation, despite I had agreed with you about the convention on capital letters after certain punctuation signals, I think, in general, we are changing some conventions and, for instance, writing almost with no uppercase letters. Indeed, your own text may be a good example of it.
So, in my opinion, fix this tiny detail can make Writer a bit more consistent and ready to the new trends.
(In reply to comment #2)
> I understand... but when you say the "." should always be followed by a
> uppercase letter, I think you should say the ".", the "!", and the "?"
> should always be followed by a uppercase letter. However, the problem occurs
> only with the ".". So, at a minimum, this behaviour looks a little
You are right about this.
> As an additional observation, despite I had agreed with you about the
> convention on capital letters after certain punctuation signals, I think, in
> general, we are changing some conventions and, for instance, writing almost
> with no uppercase letters. Indeed, your own text may be a good example of
try writing a school paper with no uppercase and try explaining the teacher it's a new trend.... I bet it won't help to turn an "F" into an "A"
IMHO Writing processing tool should follow current orthographic conventions not SMS language trends etc. etc.
> So, in my opinion, fix this tiny detail can make Writer a bit more
> consistent and ready to the new trends.
> Thks again.
I pass the ball to the develeopes.
Restricted my LibreOffice hacking area
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Perhaps this behaviour exists because full stops are not only assoc. with the end of a sentence but with abbreviations, initials and decimal separators. Changing the selection behaviour to include lower-case characters after a full stop would then result in only the text after these use cases being selected. Extra conditions would then need to be considered and an extra click to get to the beginning of the sentence and then another click to get the paragraph.
What if a sentence contains three or four full stops? At that point, it would be easier just to drag select the paragraph instead of having to repeatedly click. There would be no consistency and the user would not know what to expect. I do not know of any other application that acts this way and I doubt many would want it changed.
Click Shift Click Selection:
Click at the beginning of the text that you want to select. Hold down Shift and click at the end of the block of text that you want to select. You can even select from the end to the beginning of a block of text using this method.
Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16
Changed to RESOLVED NOTABUG.
Yes, you have some points. I agree with your main idea, specially when we're talking about texts written in English. Thks for your attention.