TRIM is useful for cleaning imported names, customer regions, product codes and spreadsheet lookup keys where unwanted surrounding spaces make text values look different. For example, an incoming code of CA-2048-RED can be standardized in a separate formula cell before copying corrected values into an approved dataset. Do not overwrite the source until the cleanup is checked: some text fields deliberately contain spaces, and internal spaces may matter.

• PlanMaker 2026 manual

=TRIM(Text)

Text (required) is a quoted text literal, an A1-style cell reference or an expression returning text. There is one required argument, no documented optional argument and no default value. The function returns its cleaned text in the formula cell. The original input cell is unchanged. The references in the English PlanMaker 2026 PDF p. 842 and the 2024/2021 online manuals use the exact signature TRIM(Text).

Language and regional entry: these formulas assume the English-language names in SoftMaker’s English manual. TRIM has only one argument, so no comma/semicolon list separator occurs. International character sets, special spaces, cell formatting and number-conversion behavior were not tested in different editions/locales.

In a blank worksheet type Original field in A1, PlanMaker formula in B1, Expected result in C1. Enter the formulas/text below. Quotation marks in the table display examples are delimiters for showing spaces; they are not part of an expected cell value. The A-column expressions that start with = are worksheet formulas that generate text strings; other A entries may be typed directly.

Reproduce and inspect: in B2 enter =TRIM(A2), press Enter and compare with North. For A3, look carefully at spaces between words using the formula bar or length measurements; the plain display may make one and two spaces hard to distinguish. The A8 combined formula intentionally uses documented CHAR control codes 10 and 13, then runs CLEAN first so its control characters are removed before TRIM. PlanMaker 2026 documents a minimum CHAR argument of 10, which these examples respect. 2026 manual (CHAR, CLEAN and TRIM sections; accessed 2026-10-11).

Validation label: All sample outputs are documentation-derived expectations independently calculated for ASCII input, not native PlanMaker results. In particular, internal-space retention in A3/A5 is inferred from the vendor’s limited description and should remain a publication test case. The standalone TRIM official example confirms stripping leading/trailing spaces only. No PlanMaker screenshot or cross-platform execution was performed.

1. Count removed ordinary spaces

With A3 as in the table, type =LEN(A3)-LEN(TRIM(A3)). Under PlanMaker’s documented edge-only behavior, the expected result is 4: two leading and two trailing spaces are removed, while the two spaces between East and Zone remain. For row 2, the same formula also gives 4. Both are independently calculated text lengths, not observed calculations. LEN and TRIM are separately documented by the vendor.

2. Prepare an imported identifier without changing the source

Suppose A7 is generated as =" CA-2048-RED ". In B7, =TRIM(A7) has the expected text result CA-2048-RED. This helps compare an incoming label with an existing unpadded identifier, but does not normalize letter case or remove internal spaces.

3. Combine CLEAN then TRIM, deliberately

For A8 enter =CHAR(10)&" North "&CHAR(13) and in B8 =TRIM(CLEAN(A8)). The expected result is North: CLEAN targets the low-code line feed/carriage return, and TRIM removes the remaining ordinary outer spaces. Reversing the order may not clean the same incoming field because TRIM is only documented to handle spaces at the edges. This ordering is a reasoned application of both references, not a native execution test.

4. Internal spaces are not a guaranteed normalization pass

A3 has East, then two spaces, then Zone. The 2026 PlanMaker reference does not assert Excel-style internal collapsing. Do not tell readers that TRIM produces East Zone without native testing. If consistent single separators are a strict business requirement, test a specifically designed cleaning procedure rather than assuming Excel parity.

• TRIM seems to do nothing: if the only extra spaces are between words, the PlanMaker documentation guarantees only edge cleanup. Check leading/trailing vs internal spaces, and test installed-version results.
• Invisible characters remain: CLEAN and TRIM do different jobs. Vendor TRIM’s reference says spaces, not line feeds, tabs, HTML formatting or all Unicode whitespace.
• A nonbreaking space is not removed: this is a plausible data issue; how PlanMaker treats code-160 spaces is not established by the simple TRIM manual entry. Do not claim guaranteed removal or guaranteed retention without testing.
• Numbers with leading zeroes: use text input as in A6; do not rely on TRIM to preserve numeric-display formatting or coerce strings into numbers. If A6 was originally numeric, its leading zeroes may already have been discarded before TRIM runs.
• Original text still has spaces: TRIM returns a new value in its formula cell. Do not expect it to edit the referenced A cell.
• Formula appears literally or errors: ensure a leading =, one required argument, matching parentheses and quotes, and inspect cell formatting. The vendor reference alone does not justify asserting specific errors for wrong types or broken references.
• Excel displays a different result: check internal repeated spaces before concluding that the two spreadsheet engines implement TRIM identically.

SoftMaker editions: PlanMaker 2021, 2024, 2026 official English references all use TRIM(Text) and state that leading and trailing spaces are removed (2026 printed p. 842, checked 2026-10-11). They do not prove feature introduction date, differences between FreeOffice and other editions, or runtime behavior on individual Windows/macOS/Linux/Android/iOS builds. No edition/platform native execution was available for this research.

Microsoft Excel: Excel’s TRIM removes extra spaces except single spaces between words, and its docs warn that the function by itself is not designed to remove nonbreaking space 160. Excel therefore has a documented broader internal-space rule than the PlanMaker reference describes; the observed practical divergence must still be validated in actual PlanMaker and Excel. Microsoft Excel TRIM (accessed 2026-10-11). No workbook import/export, .xlsx round-trip or .xls legacy save test was performed.

Locale: single-argument formulas avoid separator differences, but function name localization, entered text and encoding require checking your installed program and region. Formula results in this guide intentionally use simple ASCII for independent calculation; accented scripts and unusual spaces are unverified.

• SoftMaker PlanMaker — function documentation
• 2024 TRIM
• PlanMaker 2026 function list
• 2021 reference
• SoftMaker CLEAN 2024 reference

Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in SoftMaker PlanMaker.

• No genuine SoftMaker PlanMaker screenshots are included; this guide does not use mock application images.