Description: -- Steps to Reproduce: 1. Open a new Writer, Calc, or Impress file 2. Input "LibreOffice" 3. Set the font to "Capture it 2" or other fonts that help observation 4. Insert the Emoji character "😃" (Smiling Face With Open Mouth) between "Libre" and "Office" Actual Results: The font of the alphabet "e" changed. Expected Results: The font should not change. Reproducible: Always User Profile Reset: No Additional Info: A space between the alphabet "e" and Emoji would make it return normal. User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/62.0.3202.62 Chrome/62.0.3202.62 Safari/537.36
Created attachment 137514 [details] screenshot tested in ... Version: 5.4.2.2 Build ID: 1:5.4.2~rc2-0ubuntu0.16.04.1~lo2 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: zh-TW (zh_TW.UTF-8); Calc: group and Version: 6.0.0.0.alpha1+ Build ID: 1f8c3e3b78e0abb96d06a51eca354ae7ade5deb2 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-11-01_22:57:04 Locale: zh-TW (zh_TW.UTF-8); Calc: group
Confirmed. But on Windows builds just with the :emoji: auto-correct mechanism, while if using the Special Character dialog the insertion of the glyph selected is done cleanly. STR 1. Writer document 2. paragraph with Liberartion Serif font 3. enter "Libre§Office" 4. position cursor after "§" 5. enter :dice: Result -- autocorrect pulls Dice glyph (U+1F3B2) from fallback font and places, while the "§" changes to that font (Segoe UI Emoji). And a copy of the "§" is stamped at the start of the line. 6. repeat through 4. 7. open Special Character dialog 8. enter 1F3B2 in the search and 'Insert' Result -- Dice glyph (fallback font) is inserted cleanly, the "§" remains Liberation Serif and just one is visible. Note: on Windows we remain unable to test the experimental Emoji dialog (Standrad toolbar), so not sure if that behaves or not. =-testing-= On Windows 10 Home 64-bit en-US (v1709) with Version: 5.4.3.1 (x64) Build ID: 32c8895c6cae21571f364dbb059f419a743ee44d CPU threads: 4; OS: Windows 6.19; UI render: GL; Locale: en-US (en_US); Calc: group
Created attachment 137520 [details] result of STR on Windows from comment 2
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Hiunn-hué, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug