# `FamilyName`

A family name, one line as the person writes it. Personal data.

[People and contact](types.md#people-and-contact); not ordered; personal data (identifying); since Jadpo 0.1.0.

## Make one

Build one from its text, `FamilyName("Somerville")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: FamilyName)` reads one from its text; text that isn't one at all fails `malformed`, such as `""`, ` Somerville` or `"Somerville\t"`.

## Text, JSON and storage

`text.from` writes its canonical text, the one form `text.parse` reads back. JSON sends its canonical text as a string.

| Text | JSON |
|---|---|
| `Somerville` | `"Somerville"` |
| `van der Berg` | `"van der Berg"` |
| `山田` | `"山田"` |

It is stored in one column named for the field, of type `text`. `van der Berg` is stored as `'van der Berg'`.

## Shown to people

`text.format(value, locale:)` shows it to people in their locale.

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `Somerville` | `Somerville` |
| `van der Berg` | `van der Berg` |
| `山田` | `山田` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It isn't ordered, so `<` and sorting don't take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.