Description: In French, typography rules add a non-breaking space before so-called double-punctuation signs (!?:;). Consequently, autocorrection abbreviations like :1/2: to produce ½ do not work, because the space is inserted before the treatment of the abbreviation. Work around: I replaced these abbreviation using a comma as the ending character in the DocumentList.xml file within the archive file acor_fr-CH.dat in the configuration folder, autocorr subfolder - for me, it is /home/<my-user-name>/.config/libreoffice/4/user/autocorr/ Steps to Reproduce: 1. Open Writer, document using French and autocorrection on 2. Type :1/2:<spaceY Actual Results: 3. It produces :1/2<non-breaking-space>: ) Expected Results: It should procude a ½ character Reproducible: Always User Profile Reset: No Additional Info: This is just a collision between the choice of a system of abbreviations in autocorrection and the rules of French typography.
You can also remove the unbreakable space after having typed the second ":" then if you type enter, the replace will be made.
So the problem seems to be the order of the replacements? I feel it would be logical to do them in the opposite order - would it break something?
(In reply to Mike Kaganski from comment #2) > So the problem seems to be the order of the replacements? I feel it would be > logical to do them in the opposite order - would it break something? Silvain, Julien: can you reflect on this question?
(In reply to Buovjaga from comment #3) > (In reply to Mike Kaganski from comment #2) > > So the problem seems to be the order of the replacements? I feel it would be > > logical to do them in the opposite order - would it break something? > > Silvain, Julien: can you reflect on this question? I don't know if there may be some cons, I mean perhaps there may also be some situations where this opposite order might be wrong.
As far as I understand, I do not see that using these autocorrection replacements before the typographic rules would break anything.
Ok, I guess a possibility is to come up with the change and merge it very early on in pre-alpha stage. Then the French community could test the heck out of it. If it causes other problems, it will be reverted.
It seems the function to modify may be SvxAutoCorrect::DoAutoCorrect (see https://opengrok.libreoffice.org/xref/core/editeng/source/misc/svxacorr.cxx?r=ae56dc05#1302). However, I don't measure the impact of changing the order of blocks and it seems it may impact other languages than French so too risky. If someone likes the risk, good luck! :-) => uncc myself.
Dear Silvain Dupertuis, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug