Description: When specifying Title Case formatting in the Find and Replace dialog, all caps is not changed. Steps to Reproduce: 1.Construct F&R search to hit all-caps text and replace with Title case 2. perform search 3. Actual Results: no change in text Expected Results: I want the text to be in title case Reproducible: Always User Profile Reset: No Additional Info: Font Effects of paragraph style make no difference (NOTE: They do not impose Title Case either, for that matter) My Search is for `([A-Z]{2,25})` Replace: $1, formatting: Title [x] Regex
Note: Menu / Format / Text / Change Case / Capitalize Every Word DOES impose Title Case on all-caps text, which is the way I believe this function should work. All these observations hold in LO 7.4.3.2 and 7.5 beta.
What does work is to use Find/Replace to "Find All", then use the Menu's "Capitalize Every Word" to impose Title Case.
Just for clarification: As far as I can see, finding of all-caps text works, so your bug is about replacing them with title case. Correct?
Yes, the Find part works, the Replace does not.
I can't assess, if replace settings are correct. If you just enter a word into replace dialog, it works. Perhaps you should use ask.libreoffice.org to get a confirmation or correction of replace setting.
Repro already in 3.5.0. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 74f398bb58510087cc4a11bb2253715771a2c6b2 CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 22 March 2023
Dear Paul, 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
This seems to be resolved in 25.8 dev. Also, I discovered that to do a f/r case change I do not have to go to regex ".*", etc. Simply leaving the field blank and specifying case is enough. Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f382c1a267a93539f3c169530780889336d20b25 CPU threads: 12; OS: Linux 6.1; UI render: default; VCL: qt5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
(In reply to Paul from comment #8) > This seems to be resolved in 25.8 dev. > > Also, I discovered that to do a f/r case change I do not have to go to regex > ".*", etc. Simply leaving the field blank and specifying case is enough. I'm sorry, but what are the steps? Your latest comment completely confuses me. Find: ([A-Z]{2,25}) Replace: $1 (Capitalize Every Word aka Title formatting) ...does not work.
The steps were simply to put Capitals in the find format, and Capitalize Every Word in the Replace format, leaving the two fields blank, then hit Replace All.
(In reply to Paul from comment #10) > The steps were simply to put Capitals in the find format, and Capitalize > Every Word in the Replace format, leaving the two fields blank, then hit > Replace All. Ah, so this only works, if we have done Format - Character - Font Effects - Case - UPPERCASE. I didn't get it at first and tried it on text I had changed via Format - Text - UPPERCASE, which in hindsight was just silly.
Actually, I was unaware of the difference. I just ran a test. Three sets of text converted to caps. one through the menu. the next through the Character properties. The third via a macro that is my standard way to change case. Only the second, done through character was hit. The F/R dialog deals with the Font Effects tab of a search dialog, but I don't know what element that dialog actually applies to. Apparently it's Character, but the dialog doesn't match the standard Character dialog very well. Maybe not all Character parameters are searchable. The macro creates a text cursor then works on its String with ".uno:ChangeCaseToTitleCase", and at this point I don't know what that effects. So now I'm more confused than before.
(In reply to Paul from comment #12) > Actually, I was unaware of the difference. > > I just ran a test. Three sets of text converted to caps. one through the > menu. the next through the Character properties. The third via a macro that > is my standard way to change case. Only the second, done through character > was hit. > > The F/R dialog deals with the Font Effects tab of a search dialog, but I > don't know what element that dialog actually applies to. Apparently it's > Character, but the dialog doesn't match the standard Character dialog very > well. Maybe not all Character parameters are searchable. > > The macro creates a text cursor then works on its String with > ".uno:ChangeCaseToTitleCase", and at this point I don't know what that > effects. > > So now I'm more confused than before. Well, I think your reasoning in comment 10 is solid compared to comment 0, because back in 2023 you were trying to apply Title Case as formatting to text that was literally uppercase. For text that is literally uppercase, the solution would be to use regex find `([A-Z]{2,25})`, click Find All so all the hits become selected and then apply Format - Text - Capitalize Every Word.