When symbols become squares or lines break
Separate font support, combining characters, narrow layouts and accessibility.
A square may be a font-support problem
A blank square or question-mark box can mean that the current font lacks a glyph for a character. The copied text may still exist even when the device cannot draw its shape. Paste the same text into another browser or app to compare. Include ordinary text for anything another person must understand. Automatically replacing every unsupported-looking symbol would change the source, so our copy function does not silently swap it for a different character.
Different appearance does not always mean different text
An app may display a character as monochrome text while another uses a colorful emoji design. Some decorations also combine a base character with combining marks or less-visible characters. Removing a tiny mark by eye can leave an unexpected result. If editing damages the appearance, copy the original again and compare from a clean start. A visual preview on your own screen cannot guarantee that the recipient’s device uses the same font or design.
Space-aligned grids are fragile on phones
A post’s grid depends on font widths and available screen width. Even a copy that preserves full-width spaces can wrap differently if the destination app measures text differently. For a short bio, prefer one detail per line or a compact divider. Keep the full original of longer text art and test it in a note first. A layout that lines up on a wide monitor is not evidence that it will line up in a narrow profile field.
Keep the important meaning in ordinary text
Write essential names, dates and link instructions in normal text first. A screen reader may announce decorative symbols in an unexpected or lengthy way. Add a short face rather than repeating long ornamental lines, and explain the meaning in words when it matters. A readable profile is easier to search, copy and understand across languages than one that transforms every word into decorative lettering. Decoration should support the message, not be the only way to recover it.
Report a useful, privacy-safe example
When reporting a display issue, include the page address, exact symbol, device and browser, and the destination app. A comparison screenshot can help if personal information is removed. Do not send passwords, private messages or your entire clipboard. Our contact page links to the public account. We do not label untested combinations as compatible with every device; guidance is updated as specific issues are found.
Unicode FAQ · Characters and Combining Marks