> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/dataset-configure-redaction/textual-datasets-synthesis-options/synthesis-options-for-specific-entity-types/synthesis-name.md).
# Name synthesis options
Before it synthesizes a name value, Textual always removes any leading or trailing punctuation, except for periods after initials.
For the Given Name and Family Name entity types, you can configure:
* Whether to treat the same name with different casing as a different value.
* Whether to replicate the gender of the original value.
Synthesis options for name values
## Differentiating source values by case
To treat the same name with different casing as different source values, check I**s Consistency Case Sensitive**.
For example, when this is checked, `john` and `John` are treated as different names, and can have different replacement values - `john` might be replaced with `michael`, and `John` might be replaced with `Stephen`.
When this is not checked, then john and John are treated as the same source value, and get the same replacement.
## Preserving gender in names
To replace source names with a names that have the same gender, check **Preserve Gender**.
For example, when this is checked, John might be replaced with Michael, since they are both traditionally male names. However, John would not be replaced with Mary, which is traditionally a female name.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tonic.ai/textual/dataset-configure-redaction/textual-datasets-synthesis-options/synthesis-options-for-specific-entity-types/synthesis-name.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
