@@ -63,6 +63,9 @@ Other editable attributes
6363Parser Customization Examples
6464-----------------------------
6565
66+ Removing a Title
67+ ~~~~~~~~~~~~~~~~
68+
6669Take a look at the :py:mod: `nameparser.config ` documentation to see what's
6770in the constants. Here's a quick walk through of some examples where you
6871might want to adjust them.
@@ -104,6 +107,8 @@ constant so that "Hon" can be parsed as a first name.
104107 nickname: ''
105108 ]>
106109
110+ Adding a Title
111+ ~~~~~~~~~~~~~~~~
107112
108113"Dean" is a common first name so it is not included in the default titles
109114constant. But in some contexts it is more common as a title. If you would
@@ -134,8 +139,8 @@ making them lower case and removing periods.
134139 ]>
135140
136141
137- Parser Customizations Are Module-Wide
138- +++++++++++++++++++++++++++++++++++++
142+ Module-level Shared Configuration Instance
143+ ------------------------------------------
139144
140145When you modify the configuration, by default this will modify the behavior all
141146HumanName instances. This could be a handy way to set it up for your entire
@@ -191,7 +196,7 @@ reference to the module-level config values with the behavior described above.
191196
192197
193198Config Changes May Need Parse Refresh
194- +++++++++++++++++++++++++++++++++++++
199+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
195200
196201The full name is parsed upon assignment to the ``full_name `` attribute or
197202instantiation. Sometimes after making changes to configuration or other inner
@@ -237,7 +242,7 @@ those changes with ``repr()``.
237242
238243
239244Adjusting names after parsing them
240- ===================================
245+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
241246
242247Each attribute has a corresponding ordered list of name pieces. If you're doing
243248pre- or post-processing you may wish to manipulate these lists directly.
0 commit comments