Created attachment 153637 [details]
picture of the issue
In a file with Burmese numbers as drop caps, some are bigger than other.
See the attached screenshot.
This issue on github, give more information: https://github.com/bibledit/cloud/issues/312
Created attachment 153638 [details]
Drop cap error
File for example.
Build ID: f23e19cd15f14566832befba73fb6bbc1cffb0d7
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
but not in
Version 18.104.22.168.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
@Khaled, I thought you might be interested in this issue...
Bibisected with Linux 41max to https://git.libreoffice.org/core/+/98f56121858b4bea54d056a073005a10648785c6%5E!/
fdo#54629 MultiSalLayout::GetBoundRect always uses level 0 fallback font
Adding Cc: to Caolán McNamara
I don’t see a big here, may be an unfortunate feature. The font size is set so that the bounding box of the text fits in N lines, and the first drop cap has a larger descender so it uses a smaller font size size than the second one which does not have a descender at all.
I don’t know what the “correct” versions looked like, but the only option here is to use the line height instead of the bounding box, but then users of, say, Latin fonts with ascender bigger than cap height will be getting extra empty space above drop caps and smaller font size than what they have now.
I don't think the bisect points to a time when it worked by design, more by chance depending on fairly random glyph fallback quirks
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!
Seems to be OK.