RIGHTB Function (Gnumeric)
Use RIGHTB in Gnumeric for a UTF-8 byte-limited suffix. See character-boundary trimming, optional counts, multibyte examples and blank-input results.
Verification status: Cached October 14, 2026 evidence; no new application run on October 15. 17 selected expressions were recalculated with Gnumeric 1.12.57 ssconvert. Formula identities and raw CSV fields were checked; Gnumeric 1.12.62 was source-checked only; GUI display and native output types were not verified. How formula examples are checked
Quick answer: =RIGHTB("Lévy",2) produced “vy” in Gnumeric 1.12.57.
Availability and version history
- Introduced: Introduced in Gnumeric 1.9.10 release notes.
- Supported in: Registered in Gnumeric 1.12.62; no retirement is established.
- Last functioning version: Selected calculations are verified in 1.12.57. The newest functioning release is unverified; source registration in 1.12.62 does not establish newer runtime results.
- Scope: Desktop Gnumeric with its String Functions plugin. English comma-separated formulas are shown.
- Checked: October 14, 2026. Tables use 1.12.57 ssconvert under C.UTF-8; 1.12.62 was source-inspected only.
What RIGHTB returns
RIGHTB returns complete characters from the end of a UTF-8 string, using at most the specified byte budget. If the proposed start lies inside a multibyte character, the result starts after that character. The function does not return a fragment of its encoding. Versioned function help.
Syntax and arguments
=RIGHTB(text[,num_bytes])
- text: Required source text.
- num_bytes: Optional maximum bytes to retain; default 1. Negative counts give
#VALUE!; positive fractions are truncated in the selected tests.
Brackets indicate optional arguments; do not type them. Current worksheet implementation.
Reproducible examples
The native column records recalculated CSV field content. Quotes delimit readable text; "" means an empty field expected to be text from the callback. They do not certify the exported cell type. The independent column checks the stated character mapping, UTF-8 byte operation or decimal conversion.
| Formula | Gnumeric 1.12.57 CSV result | Independent reference |
|---|---|---|
=RIGHTB("Lévy",2) |
"vy" |
"vy" |
=RIGHTB("Lévy",3) |
"vy" |
"vy" |
=RIGHTB("Lévy",4) |
"évy" |
"évy" |
=RIGHTB("Lévy",1) |
"y" |
"y" |
=RIGHTB("Aä¸B",4) |
"ä¸B" |
"ä¸B" |
=RIGHTB("Aä¸B",3) |
"B" |
"B" |
=RIGHTB("A😀B",5) |
"😀B" |
"😀B" |
=RIGHTB("A😀B",4) |
"B" |
"B" |
Practical worksheet
For Lévy, the suffix vy uses two bytes. Both =RIGHTB("Lévy",2) and =RIGHTB("Lévy",3) return vy: the three-byte budget cannot fit the two-byte é plus v and y. Four bytes are enough for évy. This is useful only when a receiving field’s limit is expressed in UTF-8 bytes.
Advanced interpretation and checks
The saved =LEFTB("Aä¸B",1)&RIGHTB("Aä¸B",4) reconstructs Aä¸B. The first part is the one-byte A; the second is the three-byte ä¸ plus the one-byte B. The boundary is deliberate.
For A😀B, a four-byte suffix budget returns B, while five bytes return 😀B. Bytes 2–5 all belong to the same emoji. Check whether the shortened suffix still distinguishes records before using it as an identifier.
Boundaries and troubleshooting
A missing count means one byte, not one Unicode character: =RIGHTB("é") returns empty text. Use RIGHT for a character-based requirement. Zero gives empty text and a budget beyond the source length returns the whole string. The selected 3.9-byte case uses three bytes.
F2 contains Lévy; F5 is genuinely blank. The boundary protection covers code points, not complete visual grapheme clusters. A separately encoded combining accent can still be separated from its base letter.
| Formula | Gnumeric 1.12.57 CSV result |
|---|---|
=RIGHTB("é") |
"" |
=RIGHTB("Lévy",0) |
"" |
=RIGHTB("Lévy",3.9) |
"vy" |
=RIGHTB("Lévy",99) |
"Lévy" |
=RIGHTB("",1) |
"" |
=RIGHTB("Lévy",-1) |
#VALUE! |
=RIGHTB(F2,3) |
"vy" |
=RIGHTB(F5,1) |
"" |
Official evidence and checking scope
The source snapshots and native results below were retained from October 14, 2026. The recovered guide was checked against those saved records on October 15; neither the application nor a newer release was executed again.
The complete RIGHTB callback is byte-identical between the two inspected releases. Both stale and uncached SUM controls recalculated correctly. Saved native XML retains the function identities. No GUI result display, other locale, native output-type certification or newer-release execution is claimed.