Created attachment 185872 [details] arabic_and_hebrew_overlap Consider the following text: אאאلا if you type that into a new Writer document, with the RTL font being David CLM and marked as Hebrew - the لا combined character will overlap the third א, and the אאא sequence will be rendered with a left offset into the line, instead of at the beginning of the line. This is actually a rather major fault in rendering of plain text. Seen with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ad387d5b984c6666906505d25685065f710ed55d CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US
May perhaps be related to 154029, via fallback-fonts and the effect of combined characters, I'm not sure.
I can reproduce. Would be interesting to know if it is a regression.
This seems to be related to font fallback, if the “Complex” font is set to a font that has Arabic, no overlap happens.
Khaled, do you think we should have a sub-meta-bug of Fonts, for Fallback-font-related issues?
(In reply to Eyal Rozenberg from comment #4) > Khaled, do you think we should have a sub-meta-bug of Fonts, for > Fallback-font-related issues? It wouldn’t hurt, I guess.
Happens in textboxes and in Impress, doesn't seem to happen in Calc (although I've not checked extensively).
Created attachment 201394 [details] Document with just a quote character and a ligature When LibreOffice saves a document in ODF or Flat ODF format, it saves a large number of application configuration parameters, either in settings.xml in the case of a full-fledged ODF file, or within: <office:document ... etc. etc... > <office:settings> <config:config-item-set config:name="ooo:configuration-settings"> in the FODT hierarchy. Regardless of whether that's a good thing to do by default - users may not be interested in sharing their app configuration with others; or they might want to limit the content saved in the document to _just_ what they intended to put in the document, e.g. content and styles. Typically, a user would not know - unless they inspected the ODF/Flat ODF's XML, that these configuration settings are saved at all. I therefore propose: 1. An easily-discoverable toggle for saving configuration data in files, by default (either just ODT/Flat ODT or for all formats, where the semantics might vary by format). 2. Placing a toggle on the Save... / Save As... dialogs controlling whether such data would be included in the current Save operation. This would be similar to the "Save with Password" and other toggles already present in the Save... / Save As... dialog. Note that this also has some benefits w.r.t. QA and development, in that files would be smaller, diff's between files would be smaller, and it would not be necessary to verify that differences in behavior are not the result of app configuration changes. (Although to be fair, that effect can also be achieved by editing the files saved.)
Comment on attachment 201394 [details] Document with just a quote character and a ligature Please excuse the comment added with this attachment, it was the result of a mis-copy-paste. This document demonstrates the bug without any Hebrew text, just a quotation mark (a neutral character) and the ligature.
Created attachment 201395 [details] Document exhibiting the overlap with just a quote character and a ligature Apparently, the marking as Hebrew is not significant; I changed it to "ar" everywhere in the file, and dropped the country code.