<field nameid='datebirth' type='datefield _description="Some Baptize record register birth date"optional='1'/>

<field nameid='First Witness' object='Person' optional='1' size='25' relation='witness'/> <field nameid='Second Witness' object='Person' optional='1' size='25' relation='witness/> <field nameid='Celebrant' object='Person' optional='1' size='25' relation='celebrant'/> <field nameid='addressparents' size='35' object='Place' optional='1' _description='Some records contain part of the address of the parents'/> <freeflowinputs> <freeflowinput style='condensed' lang='en'> On <datebapt>, a <Gender> was baptized, and given the name <Name>. His father is <Father>, his mother <Mother>, who gave birth on <datebirth>. Witnesses are <First Witness> and <Second Witness> and celebrant <Celebrant>. </freeflowinput> </freeflowinputs>

<englishtranslation>

</englishtranslation> Some features:# nameid is a fixed key, which via translation section obtains it's true English value. _en can be translated via po files# relation attribute could be dropped, as nameid could be mapped in code to relation. Keep?# freeflowinput should not be translated. Translators should update this xml and add their lang, in the GUI a dropdown box for all lang can be offered. It is not good practice to translate such long texts via po. Using po puts pressure on English not too change too much. Working like this allows to offer a Latin version and have people inspect the typical form in Latin. The style allows different freeflow texts for the same langauage# fields are by default textfield, which need a size attribute# if not textfield is needed, the field is given a type, eg genderfield, datefield, ...