Bug 82082 - Autocorrection error with French punctuation
Summary: Autocorrection error with French punctuation
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-03 08:22 UTC by skywatcheuse
Modified: 2015-05-06 14:23 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description skywatcheuse 2014-08-03 08:22:24 UTC
Problem description:
I use the French punctuation, with non-breaking spaces before double punctuation marks. Whenever I type a closing quotation mark, a non-breaking space is inserted before, as it should. But whenever the quotation mark is followed by a space, a line break or a punctuation mark (i.e. every time), a second non-breaking space is added before the quotation mark.

Steps to reproduce:
1. Use a French configuration and type a quotation mark just after a word. You should see a non-breaking space before the quotation mark.
2. Then type "Space" or "Enter" or any punctuation mark. A second non-breaking space should appear before the quotation mark.
3. You can put the cursor just after the quotation mark and repeat #2. A third non-breaking space will appear, and so on.

Expected behavior:
Well, one single non-breaking space is enough.

(Note: I use Kubuntu 14.04.)
Operating System: Ubuntu
Version: 4.2.4.2 release
Comment 1 sophie 2014-08-04 14:05:29 UTC
Hi, I can not reproduce your issue, no breaking spaces added after. Are you using this type: « word » of quotation marks? Have you installed Grammalecte? and if yes, what is the version number? Thanks. If you reply, please use this link to do so https://bugs.freedesktop.org/show_bug.cgi?id=82082. Sophie
Comment 2 tommy27 2014-08-18 10:09:16 UTC
Please answer questions Then revert status to unconfirmed
Comment 3 QA Administrators 2015-04-01 14:46:51 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 4 QA Administrators 2015-05-06 14:21:06 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team