PROPER in Collabora Office: Capitalize Simple Word Labels with a Reviewable Cleanup Policy
Use Collabora PROPER on lowercase labels, preserve original wording and avoid assuming that automatic capitalization knows personal names or acronyms.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: PROPER capitalizes the first letter of each word. For the lowercase control =PROPER("north region team"), the expected result is North Region Team. It is a mechanical text transformation rather than a language-aware style editor.
Availability and version history
- Introduced: original Collabora release and launch date are not established by the sources reviewed.
- Availability: documented in Collabora Office 26.04 help, scoped to the desktop-help release.
- Platform scope: online and mobile deployments are not inferred from desktop documentation.
- Checked: October 14, 2026. Direct function documentation and independently modeled text controls; no native Collabora test was performed.
Syntax and a deliberately clear input scope
=PROPER(text)
The argument is text or a reference to a text cell. Collabora’s direct page demonstrates ordinary words separated by spaces. These examples likewise use lowercase Latin words with ordinary spaces, avoiding unsupported assumptions about apostrophes, hyphens, digit boundaries or locale-specific casing.
The short definition does not give a complete rule for already-uppercase interior letters. This guide therefore does not certify that every mixed-case acronym or brand will survive unchanged, or that a particular punctuation mark always starts a new word.
Example 1: create a display-label column
Enter north region, south warehouse, quality review and support team in A2:A5. In B2 enter and fill down:
=PROPER(A2)
Expected labels: North Region, South Warehouse, Quality Review, Support Team. Keep A2:A5 as the source values. The output column provides a display variant without silently changing the stored source descriptions.
These are text labels, not unique keys. Two records can have the same display label for legitimate reasons, and capitalization does not establish that they refer to the same entity.
Example 2: compare several casing policies
For the source north team, expected outputs are:
=PROPER("north team"): North Team.=UPPER("north team"): NORTH TEAM.=LOWER("north team"): north team.
Choose the desired presentation before applying a transformation across a workbook. UPPER and LOWER express different policies; a professional title or brand may need a manually maintained display value instead.
Advanced example: retain a curated override
Use the following text inputs in D2:E4. Each empty override is an explicit ="" formula, not an unspecified imported blank.
| Row | D · Source label | E · Approved override |
|---|---|---|
| 2 | north region | ="" |
| 3 | api support | API Support |
| 4 | quality review | ="" |
In F2 enter and fill down:
=IF(EXACT(E2;"");PROPER(D2);E2)
Expected outputs: North Region, API Support, Quality Review. Without the override, the all-lowercase second source would produce Api Support. The override preserves the intentional acronym while the simple labels use the automatic rule.
EXACT compares the explicit text values, and IF selects the chosen presentation. This controlled example does not establish a full blank/error-coercion matrix for arbitrary override cells.
Advanced check: document what did and did not change
For quality review, both the source and expected Quality Review have length 14. The selected ASCII case conversion changes letters without adding characters in this control. This is not a universal promise for all scripts or case mappings.
Use a separate status such as =IF(EXACT(A2;B2);"Unchanged";"Review display") to expose a difference rather than overwriting the source. The lowercase first example is expected to produce Review display.
Limits and editorial judgment
PROPER cannot know how a person spells a name, whether a short word should remain lowercase in a title, or which organizational abbreviations require capitals. A mechanically consistent output can still be editorially wrong. Keep an override path and check representative real labels before adopting the rule.
The examples do not claim punctuation-boundary, multilingual, maximum-length or native-client testing. Use the ordinary-word controls as a reproducible starting point and maintain authoritative names separately.
References and verification
The dedicated Collabora function page was reviewed. Expected outputs are independently modeled text controls, not captured results from the application. Extended-character, coercion and deployment-specific behavior retain the limits stated above.