Contact

PROPER in WPS Spreadsheet: Normalize Letter Case without Treating Names as Rules

Text Intermediate WPS Spreadsheet

Apply WPS PROPER to controlled text, inspect punctuation and digit boundaries and preserve original identifiers when normalization creates collisions.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: PROPER capitalizes the first letter and letters following nonletter characters, then lowercases the other letters. =PROPER("goodNight") has expected result Goodnight, matching the dated WPS demonstration.

Availability and version history

  • Introduced: documented by 2019-06-06 in WPS material; the first release is not established.
  • Availability: the dated official lesson identifies WPS Office for Windows Personal.
  • Scope: exact supported builds and other WPS clients remain unverified.
  • Checked: October 14, 2026. Documentation and independent examples; no native WPS execution.

Syntax and the documented boundary rule

=PROPER(text)

Text can be a quoted string, a formula returning text or a reference to a text cell. The official definition explicitly names nonletter boundaries; it is more specific than simply “capitalize every word.”

The walkthrough discusses an Excel-style data-cleaning situation, but the page is a WPS Academy function lesson with Windows Personal scope and a WPS function-dialog demonstration. This guide relies on that product-specific definition and demonstration, not on another program’s behavior.

PROPER changes case mechanically. It cannot know an organization’s preferred capitalization, a person’s chosen name spelling or the meaning of an acronym. Preserve the original text when those distinctions matter.

Example 1: inspect ordinary ASCII boundaries

Enter the following exact text strings in A2:A6. Put =PROPER(A2) in B2 and fill down.

A, original text B, expected text
goodNight Goodnight
mARY ann Mary Ann
o’NEIL O’Neil
part7blue Part7Blue
API data Api Data

The apostrophe and the digit seven are nonletters, so the following letters start new capitalized segments under the documented rule. The interior capital N in goodNight is lowercased because it is preceded by a letter.

The last row demonstrates a limitation: API becomes Api. The function has applied its case rule correctly, even if the result is inappropriate for that acronym.

These are ASCII controls. Locale-specific letter categories and unusual Unicode case mappings are not certified by these examples.

Example 2: keep spaces separate from case

In A9 enter =" aLICE smith ". Quotation marks make the two leading spaces, three internal spaces and two trailing spaces reproducible.

=PROPER(A9) has expected text Alice Smith . It changes letter case but does not remove those spaces. Both the original and the case-normalized text have 17 characters.

If ordinary-space cleanup is also intended, compare:

=PROPER(TRIM(A9))

The expected result is Alice Smith, with 11 characters. TRIM handles the separate spacing task. This example does not claim that TRIM removes every Unicode space or control character.

Use LEN to make the difference visible when leading or repeated spaces are difficult to notice on screen.

Advanced example: preserve a known acronym explicitly

Suppose A12 contains the exact text API, while A13 contains gOOD morning. A controlled rule can preserve that one approved acronym:

=IF(EXACT(A12,"API"),"API",PROPER(A12))

Fill down. Expected outputs are API and Good Morning. EXACT makes the exception case-sensitive rather than relying on an ordinary text-comparison rule.

If A12 is changed to lowercase api, the exact exception does not match and the expected output is Api. That is intentional in this narrowly defined policy. If lowercase variants should also become API, define and review that additional rule explicitly.

One exception does not make PROPER a universal name formatter. For several approved terms, maintain a reviewable mapping rather than repeatedly replacing short fragments inside unrelated words.

Advanced example: detect normalization collisions

In A16:A19 enter api, API, Api and aPI. Put =PROPER(A16) in B16 and fill down. All four expected outputs are Api.

In C16 use =COUNTIF($B$16:$B$19,B16) and fill down. Every expected count is 4, because the normalized outputs are identical. The original values were four different case patterns.

A display label can therefore lose distinctions that existed in the source. Keep an independent record ID and the original text when matching records, auditing changes or communicating someone else’s chosen spelling.

COUNTIF here checks identical normalized strings; the example does not require it to distinguish the original case variants.

Choosing another transformation

UPPER deliberately makes letters uppercase, while LOWER makes them lowercase. PROPER has a third, boundary-based contract.

For API data, those three independently expected outputs are API DATA, api data and Api Data. Choose the transformation that fits the intended output rather than treating all case-cleanup functions as equivalent.

Limits and verification

The dated source defines the text transformation but does not provide a complete coercion, error-precedence or international-name specification. The worked cases deliberately use explicit ASCII text. Empty references, unusual Unicode mappings and imported special values remain outside their certified scope.

A second PROPER pass leaves these already normalized examples unchanged. That idempotence is useful as a local control, but it does not prove that the transformed spelling is correct for its real-world owner.

References and verification

Complete function-specific sources reviewed. Expected results are independently derived controls, not native application captures. Formulas use English names and comma separators; check the installed locale.