TEXTSPLIT Function (Gnumeric)
Split text into Gnumeric arrays by row and column delimiters with padding and empty handling.
Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in Gnumeric. How formula examples are checked
Quick answer
TEXTSPLIT divides text into a multi-cell array, using one delimiter to separate columns and optionally another to separate rows. It is useful for splitting CSV-like codes or two-dimensional synthetic strings; it is not a fully featured CSV parser with quote/escape handling.
=TEXTSPLIT("Red,Green,Blue",",")
Expected array: one row with three elements: Red | Green | Blue. Gnumeric’s function descriptor marks the result non-scalar (array-producing). The exact cell expansion behaviour in a particular UI/build was not natively tested. GNOME tagged implementation.
Official Gnumeric syntax (1.12.61+)
=TEXTSPLIT(text, col_delimiter, [row_delimiter], [ignore_empty], [match_mode], [pad_with])
| Argument | Required? | Meaning | Default |
|---|---|---|---|
text |
Yes | Input string or referenced text cell. | None |
col_delimiter |
Yes | Delimiter string or an array of strings that separates array columns. | None |
row_delimiter |
No | Delimiter string or array to start another array row. | No row splitting |
ignore_empty |
No | Boolean: TRUE omits empty fragments; FALSE keeps them. |
FALSE |
match_mode |
No | 0 case-sensitive; 1 case-insensitive. |
0 |
pad_with |
No | Value used for missing elements in shorter rows of a rectangular result. | #N/A |
Use the English comma-separated formulas as written, adapting argument separators to your Gnumeric locale if necessary. The actual function descriptor is SA|A?f?, with missing optional values handled in its implementation. This documentation represents Gnumeric 1.12.62 specifically, not a guess from Excel. Source.
Example 1: split across columns
Create a column with heading Codes and put Red,Green,Blue in A2. Enter this in a suitable empty result location:
=TEXTSPLIT(A2,",")
Expected logical result (one row, three columns):
| Element 1 | Element 2 | Element 3 |
|---|---|---|
Red |
Green |
Blue |
The source returns an array with one row. Do not assume Excel-style automatic spill mechanics: if your Gnumeric installation requires an array-formula range or shows an array warning, consult its array-entry behaviour and retest in that build. Formula execution and placement were not performed in this research batch.
Example 2: both row and column delimiters
Set A3 to Oak,Pine;Maple,Birch and enter:
=TEXTSPLIT(A3,",",";")
Expected array (semicolon introduces another row):
| Column 1 | Column 2 |
|---|---|
Oak |
Pine |
Maple |
Birch |
To demonstrate empty-fragment handling, =TEXTSPLIT("A,,B",",",";",FALSE) is expected to return the three logical columns A, an empty text fragment, B. Changing the last argument to TRUE drops the empty fragment and gives the two logical columns A, B. (The third argument is the unused row delimiter here; this avoids relying on undocumented empty positional-argument syntax.)
Advanced example: ragged rows and padding
Uneven input can create a nonrectangular logical split. Gnumeric returns a rectangular array and pads shorter rows. Compare:
=TEXTSPLIT("A,B;C",",",";",FALSE,0,"N/A_TEXT")
Expected elements:
| Column 1 | Column 2 |
|---|---|
A |
B |
C |
N/A_TEXT |
When pad_with is omitted, the release-source implementation uses an #N/A error value for missing positions. This differs from an actual delimiter-created empty field. For case-insensitive delimiter matching, =TEXTSPLIT("redXbluexgreen","X",";",FALSE,1) is expected to split into red, blue, green. These are independently reasoned expectations, not app-screen observations.
Errors, limitations and troubleshooting
- Missing pieces show
#N/A: This may be padding, not a bad source string. Supplypad_withfor user-friendly output. - Blank output elements: Consecutive column delimiters create empty fragments by default. Set
ignore_empty=TRUEto omit them. - Unexpected number of rows: Verify that the third argument is really the row delimiter; the second is the column delimiter.
- Wrong case behaviour:
match_mode=0matches case;1ignores case. The source handles case-folded matching, but Unicode/overlapping-delimiter edge cases need native confirmation. - Blocked array output: The function returns an array rather than a scalar. Ensure the intended area is available, and check how your installed Gnumeric build handles array formula results.
- Quoting/data import: TEXTSPLIT does not parse quoted CSV escapes. Use an import tool for complicated CSV/TSV files rather than expecting CSV quoting rules here.
- Version support: Added in Gnumeric 1.12.61 and included in 1.12.62; do not infer support in older Gnumeric or in builds without the standard String Functions plugin.
Cross-software and related guides
Microsoft Excel 365 and Excel 2024 document the same six named slots and explicit spill behaviour, but this does not prove identical array/UI behaviour in Gnumeric. Google Sheets provides SPLIT with its own delimiter rules. Microsoft TEXTSPLIT reference.
Official reference and verification
Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in Gnumeric.
- No genuine Gnumeric screenshots are included; this guide does not use mock application images.