<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>miacollinsnotesのブログ</title>
<link>https://ameblo.jp/miacollinsnotes/</link>
<atom:link href="https://rssblog.ameba.jp/miacollinsnotes/rss20.xml" rel="self" type="application/rss+xml" />
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
<description>ブログの説明を入力します。</description>
<language>ja</language>
<item>
<title>Why Stylish Names Turn Into Boxes in Adopt Me</title>
<description>
<![CDATA[ <p><em>By Mia Collins</em></p><p>The most frustrating Adopt Me rename is the one that looked perfect in a preview and then landed as empty boxes, missing letters, or a filtered string. That usually is not a “broken font file.” These styles are Unicode characters. If the game does not have a glyph for a character, or if it rejects a mark, the preview in a browser will not save you.</p><h2>Test a short sample first</h2><p>I copy only a few letters, not the full name, and paste them into the game before I commit. If the sample already fails, I stop and switch to a simpler recipe. I also check length: decorative frames and combining marks count toward the 20-character pet-name limit, so a style can overflow even when the base name is short.</p><p><a href="https://www.adoptmefonts.org/fonts-that-work">Fonts that display in Adopt Me</a> is a practical compatibility guide: which copy-and-paste Unicode styles actually show up, and what to try when something is filtered, replaced by a box, or too long. I use it as a troubleshooting page, not as a promise that every listed style will work forever on every device. If a character becomes a replacement box, I assume the font coverage is missing, not that I copied “the wrong way.”</p><h2>Prefer fewer marks when in doubt</h2><p>Styles that rely on a stack of combining marks, or on letters from less common blocks, fail more often in my tests than plainer lookalikes. When two styles are close in mood, I keep the one that still looks like letters after I paste it into a plain notes app. Accessibility also matters: a name that a friend cannot read, or that a screen reader spells out as a jumble of symbols, is a poor rename even if it looks ornate in a preview.</p><p>Once a sample pastes cleanly and fits the limit, I copy the full name. If it then fails, I go back to the sample style rather than inventing a new name on the spot.</p><h2>References</h2><ul><li><a href="https://en.wikipedia.org/wiki/Specials_(Unicode_block)">Specials (Unicode block) (Wikipedia)</a> — including the replacement character you see when a glyph is missing.</li><li><a href="https://www.unicode.org/faq/unsup_char.html">FAQ: Display of Unassigned Code Points and Unsupported Characters (Unicode)</a> — why a “tofu” box appears.</li><li><a href="https://www.unicode.org/faq/char_combmark.html">FAQ: Combining Marks (Unicode)</a> — stacked marks and rendering limits.</li><li><a href="https://www.unicode.org/reports/tr29/">Unicode Standard Annex #29, Text Segmentation</a> — how length can differ from what you see.</li><li><a href="https://webaim.org/techniques/screenreader/">Using a Screen Reader (WebAIM)</a> — a reminder that decorative text is still read as characters.</li><li><a href="https://support.microsoft.com/en-us/windows/windows-keyboard-tips-and-tricks-588e0b72-0fff-6d3f-aeee-6e5116097942">Windows keyboard tips (Microsoft)</a> — practical copy and input habits on a PC.</li></ul><p><em>Disclosure: the linked Adopt Me Fonts site is one of our own projects. The references are independent and do not endorse it.</em></p>
]]>
</description>
<link>https://ameblo.jp/miacollinsnotes/entry-12984418952.html</link>
<pubDate>Fri, 13 Nov 2026 21:17:18 +0900</pubDate>
</item>
</channel>
</rss>
