pub struct PersonalName {
pub name: Name,
pub type: Option<String>,
pub romanized: Name,
pub phonetic: Name,
}
Fields§
§name: Name
The surname of an individual, if known, is enclosed between two slash (/) characters. The order of the name parts should be the order that the person would, by custom of their culture, have used when giving it to a recorder. Early versions of Personal Ancestral File ® and other products did not use the trailing slash when the surname was the last element of the name. If part of name is illegible, that part is indicated by an ellipsis (…). Capitalize the name of a person or place in the conventional manner— capitalize the first letter of each part and lowercase the other letters, unless conventional usage is otherwise. For example: McMurray.
Examples: William Lee (given name only or surname not known) /Parry/ (surname only) William Lee /Parry/ William Lee /Mac Parry/ (both parts (Mac and Parry) are surname parts William /Lee/ Parry (surname imbedded in the name string) William Lee /Pa…/
TODO: Can there be multiple names? The torture file seems to indicate so
type: Option<String>
§romanized: Name
for the name used in the superior <NAME_PERSONAL> context. The method used to romanize the name is indicated by the line_value of the subordinate <ROMANIZED_TYPE>, for example if romaji was used to provide a reading of a name written in kanji, then the ROMANIZED_TYPE subordinate to the ROMN tag would indicate romaji.
phonetic: Name
FONE The phonetic variation of the name is written in the same form as the was the name used in the superior <NAME_PERSONAL> primitive, but phonetically written using the method indicated by the subordinate <PHONETIC_TYPE> value, for example if hiragana was used to provide a reading of a name written in kanji, then the <PHONETIC_TYPE> value would indicate ‘kana’.