Bold Fraktur Text style

This is the most honestly-named node in the pack: it converts your text to bold Fraktur Unicode. That's it. One input, one output, no models, no sampling. You type once upon a time, you get the 𝔉𝔯𝔞𝔨𝔱𝔲𝔯-looking equivalent back, and you can wire the result anywhere a string goes - usually into a text encode or an overlay node.

Why would you? Two real reasons, neither of which is "I'm practicing my gothic calligraphy." The first is visual: if you're generating images with rendered text, fonts matter, and a Fraktur-styled string is a cheap way to tell a stylized/ancient/horror-flavored model what kind of lettering you want on a sign, a book cover, or a title card. The second is practical in a sneaky way: Fraktur characters are a different Unicode block than the ASCII you typed, so the string can't be accidentally re-typed or mangled the way normal text can when it flows through a prompt template - it's a one-way ticket to "this text is intentional."

Mechanically it's a per-character mapping: supported Latin letters get replaced with their bold Fraktur Unicode code points, and characters without a mapping pass through unchanged. That last part is the limit to remember - Fraktur only covers the basic Latin alphabet (plus some punctuation), so anything with accents, Cyrillic, or emoji stays as-is, and you'll get a mixed-style string. The flip side is the node's sibling, UC_UnBoldFrakturTextStyle, which reverses the mapping back to plain text - handy if you need to round-trip.

The inputs and outputs are as minimal as they get: a multiline text string in, fraktur_text out. Wire the output into a CLIP text encode, a Text Overlay node, or a markdown preview and you're done. There's no configuration, no gotcha in the node itself.

The gotcha is downstream, and it's worth saying plainly: Unicode is only as good as the font rendering it. Bold Fraktur characters live in the Mathematical Alphanumeric Symbols block (uppercase starts at U+1D56C), which a surprising number of fonts and some text encoders simply don't have glyphs for. If your renderer or model mangles the characters, that's not a bug in this node - that's the font. If you're using this to influence generated image text, keep the string short; LLM-based encoders read instruction-style text best when it's not a wall of decorative glyphs.

Install is pack-standard: ComfyUI Manager search "ComfyUI-UtilsCollection", or cd ComfyUI/custom_nodes && git clone https://github.com/silveroxides/ComfyUI-UtilsCollection and restart. It needs nothing beyond the pack's trivial Python deps. Three-minute toy, zero cost, occasionally exactly what a stylized-text workflow needed.