Description: 1. LibreOffice does not treat diacritics as separate characters independetly from the accented letter. {letter + diacritics} are treated as a single letter. Positioning the cursor between them, selecting and searching each alone is impossible. 2. Searching text of a given color find all colors, not the wanted one. 3. Opentype fonts: LibreOffice adds some unwanted kerning. In latin fonts, it is moderate; but marked in arabic. Ex: "جاء" is shown with a space between the first and second letters. I checked the font andd verified it contains no intrinsic kerning. N.B. the same fonts are treated corectly in MS Word. Steps to Reproduce: See description Actual Results: See description Expected Results: See description Reproducible: Always User Profile Reset: No Additional Info: See description User-Agent: Mozilla/5.0 (masking-agent; rv:42.0) Gecko/20100101 Firefox/42.0
- The same occurs in Libreoffice 6.0 - I recently noticed that unwanted added kerning in Opentype fonts occurs in justified text, but not in right-alined or left-aligned text. Maybe, it relates to filling spaces between letters. - While redesigning the search function, it would be desirable to search for a given text formatted in a given style. Currently, it is possible to search for a style without text or a text without style.
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
Search does not take into consideration accurate Alef forms with Hamza in Arabic. I suggest to take MS Word search as an example.
> 1. LibreOffice does not treat diacritics as separate characters independetly from the accented letter. {letter + diacritics} are treated as a single letter. Positioning the cursor between them, selecting and searching each alone is impossible. Use shift+arrow keys to move the cursor between the base letter and the mark (it might not show anything visually, but try typing text and it will be inserted between the base and the mark). The other issues are all independent bugs or feature requests, place open a separate bug report for each issue and don’t lump them all together.
Khaled, Thanks for you suggestion but it does not resolve the problem. We should be able to search for, and replace, diacritics independently. This is very troublesome.
Setting to needinfo while we wait for the issues to be separated to their own reports.
Please test as per comment 4 Otherwise one issue each per BZ report... Please separate each issue into its own, with individual steps to reproduce and test documents/screen clips as needed.
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 INSUFFICIENTDATA 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 MassPing-NeedInfo-Ping-20181009
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 Warm Regards, QA Team MassPing-NeedInfo-20181105