Use this strings: 🏠🏡🏢🏣🏤🏥🏦🏧🏨🏩🏪🏫🏬🏭🏮🏯🏰🏱🏲🏳🏴🏵🏶🏷🏸🏹🏺🏻🏼🏽🏾🏿 And change the size and fonts type... have fun...
Do you have any valid, *specific* problem to report? There is no sample reproducer document, screenshot, steps to reproduce, etc. https://www.chiark.greenend.org.uk/~sgtatham/bugs.html However… > Show the Unicode in wrong size... > And change the size and fonts type... have fun... You realize that these characters are emoji, so are likely to be supported only in fonts with “Emoji” in their name? If a character isn’t supported in a typeface, how can you expect LO (or any other program whatsoever) to assign specific character formatting that will look as you expect? (Not that it makes sense to apply any formatting to *emoji* that isn’t font size, but…)
This is not a proper bug description; in this state, it's a kind of quest "try to guess what I'm talking about; see how inventive I am". For instance, I don't see anything special in Version: 6.0.5.1 (x64) Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: ru-RU (ru_RU); Calc: CL, using Liberation Mono, and increasing the size. Is it because it is Linux-only? or just because OP didn't tell what to look at, and what are the pre-requisites, like browser (which might in theory affect what is copied to clipboard), fonts, and specific sizes? Please provide the information in understandable and reproducible way (with clear steps, like "1. Create a new text document; 2. Paste the string copied from the comment 0; 3. Ansure that the font is XXX, and size is Y; 4. Change size to Z; 5. Observe ABC at right/left/top/bottom of page/line/whatever..."). It sometimes helps to attach documents you created to show the problem (in which you know the problem os observable); and/or screenshots. Please set the status back to UNCONFIRMED after you've provided the necessary info.
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-20190111
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-20190321