We import a CSV file with text to be cut. If I import the same files from last year, I now get different emojis represented.
I had thought it was a version problem, but even going back several versions, it acts the same.
Wondered if anyone had seen similar and knew a way of reverting back to the older emoji
@chappie had issues with emoji - maybe relevant.
can you SHOW us the difference? Between what you expect and what you are getting?
Are you using the same font as you were before?
Upload a sample lightburn file so the mind-hive can check against their own machine.
Tangible, visible evidence will get better answers.
I am using same font (Arial) as it is the same templated merge file
The emojis are âribbonâ and âcherry blossomâ but others also look different.
Attached Lightburn file shows how they used to look and how they look now.
emoji test.lbrn2 (232.0 KB)
Iâm not seeing any of these characters in any of my Arial fonts. Can you provide any more information that might help?
EDIT:
Upon further investigation it appears that there is some trickery afoot! From what I can gather these emoji characters are either from the âSegoe UI Emojiâ or âSegoe UI Symbolâ fonts (although I still canât find them in either of the font files). Windows and compliant apps perform some background shenanigans to show the emoji characters while making you think itâs in whatever font is currently selected.
Iâll continue attempting to find out moreâŚ
EDIT#2:
Ok, so as far as I can tell your original design is what was deployed with Windows 10 Fall Creators Update (Oct. 2017). The one thatâs replaced it looks to be a Windows 11 version (which has also seen updates during its life).
Hope this helps.
Thanks for your reply. Yes, that is as far as I had got yesterday with the Segoe UI Emoji font being responsible. They seem to show unless you choose a font that has emoji support e.g. Noto Emoji.
Itâs just odd how at some point in late 2025 those fonts have changed as the original design was from earlier in 2025. Also strange that most likely a Windows update has finally gotten around to updating those fonts from the old (possibly 2017 like you said) to the new one now.
Iâm currently down a rabbit hole of trying to get the older one back on my machine.
Will update here if and when I manage that!
Yes, itâs odd that the timing of the windows updates that are apparently responsible for the change(s) donât seem to correspond with your experience.
I have come across various recommendations online saying to download a Windows ISO then extract the old font file from there. Anyway, you seem to be getting to the bottom of it so let us know how you get on.
This may not solve your issue but Windows has a special feature you can use to see what special characters are in a particular font.
Go to Windows Start and type in âCharacter Mapâ. Run the program .
From the top where it says Font: Select a font and then scroll down to the bottom to see all the special characters available in that font. You can select characters and then copy and paste them into lightburn. Hereâs how it works
Go to the character map and search the fonts to see if there is one that contains the special characters you want.
Select the special characters you want and click on Copy.
Then go to lightburn and paste them into your design.
You can also click on Advanced View and look at different character sets within a font.
This may not solve your issue but at least tell you if there is a font that contains the special characters you are looking for
Using your info, I have successfully navigated the rabbit hole. The versions you want are indeed in the old Segoe UI Emoji TTF file (the Segoe UI Symbol TTF file has another version, but worse and similar to the current one).
I grabbed the old TTF files off one of my old mothballed Win10 computers and used a bit of python to update each with âOldâ appended to its font name (and new internal IDs). I then installed the old fonts with their updated names and reopened LightBurn. The ânewâ fonts were then available in the list (e.g. âSegoe UI Emoji Oldâ), and I was able to successfully use them to get results matching your original version.
Iâm going to send you a private message with more details, since I canât post the modified font files here (copyright, derivative works, etc.), but basically, you were correct in your diagnosis, and weâve got this licked for you.
Glad I was able to help. Remember when you install a new font. Right Click on the font and select Install for All Users otherwise it may not show up in Lightburn.
Hereâs a nice little free program called NexusFont. You can use it to view all of the fonts installed on your computer and a sample of each font. You can also print out the list. Makes it much easier to find the font you are looking for. Although it doesnt show special characters
Windows Character Map certainly has its uses (and I use it quite often), but one issue I find with it is that the glyphs are very small. When youâre trying to locate a particular glyph among hundreds (or even thousands) it can be pretty much impossible to find what youâre looking for. Searching for âribbonâ or âcherry blossomâ brings back nothing, and neither does searching for the unicode value. Manually scrolling through the glyphs with the cursor keys doesnât reveal either of these characters (at least on my system). Neither can I find them when looking through the glyphs in FontExpert. Corel Font Manager however, does show a lot more glyphs.but there are over 62,000 of them to look through in this particular font file! Iâve just discovered BabelMap which is able to show them.
I donât think @ClayJar was responding to your post about Character Map, but was replying to the post by @gjbarker (hence the quote at the top of his reply).
Thanks all.
For now I am using the old versions of these font files thanks to @ClayJar as an extra font installed.
I may get around to making them the default files on Windows again, but chances are future updates will overwrite them again without notice, so will probably stick with a workaround so we are cutting what is expected.
Another approach, although not workable with imported cvs file, would be to grab the emojis and change them from Text to Path to make them native SVG objects, and them import them into your art library for archive.
Have a great day!
