ucs2_strscpy(9)

💖 ucs2_strscpy — the Kernel API Manual, bestie edition 💖

okay so this one's from the Kernel API Manual, section 9, and it's literally the cutest little string copier you've ever met 🥰 it's called ucs2_strscpy and we're gonna get into it.

---

🌸 NAME 🌸

ucs2_strscpy — copy a UCS2 string into a sized buffer. that's it, that's the whole vibe 💅

---

✨ SYNOPSIS ✨

ssize_t ucs2_strscpy (ucs2_char_t *dst , const ucs2_char_t *src , size_t
count );

like, that's the whole signature, written out exactly as it lives 🫶

---

🎀 ARGUMENTS 🎀

• dst — pointer to the destination buffer, aka where we're copying the string to. this is the glow-up location 💖
• src — pointer to the source buffer, aka where we're copying the string from. the original, the blueprint, the main character 👑
• count — size of the destination buffer, measured in UCS2 (16-bit) characters. yes bestie, UCS2 characters, not bytes, don't get it twisted 🌸

---

🦋 DESCRIPTION 🦋

so it's like strscpy, only for UCS2 strings. periodt. 💅

it copies the source string src, or as much of it as actually fits, into the destination buffer dst. ngl, if the string buffers overlap, the behavior is undefined — so like, don't do that, that's not the vibe 😭

the destination buffer dst is always NUL-terminated, unless it's zero-sized. zero-sized buffers get nothing, which honestly? fair. 🫶

---

🔥 RETURN 🔥

it hands you back the number of characters copied into dst — and that's excluding the trailing NUL terminator, don't count the NUL bestie — or -E2BIG if count is 0 or if src got truncated because the destination buffer was too small. 😭 tiny buffer energy.

---

🌈 SEE ALSO 🌈

• Kernel file ./lib/ucs2_string.c — go look, iykyk ⭐

---

and that's the page!! this absolutely iconic little manpage came from ./lib, dated October 2026, for ucs2_strscpy(9). slay, ate, no cap 💜🧚‍♀️