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 188.8.131.52.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