Residence and census - Revision history

Romjerome: /* How or where could we set address on event ? */

2010-10-10T16:18:58Z

‎How or where could we set address on event ?

2010-10-10T16:18:29Z

‎How or where could we set address on event ?

2010-07-19T14:27:35Z

‎Events

2010-07-19T14:24:47Z

‎To share data

2010-07-19T14:22:17Z

‎Events

2010-07-19T14:20:36Z

2009-06-07T23:50:20Z

‎Multiples places: spelling gramar

2009-06-07T23:48:35Z

‎More informations: spelling

2009-01-30T11:58:26Z

‎Multiples places

2009-01-30T11:48:08Z

‎Events

@@ Line 49: / Line 49: @@
 |}
-On census' description we could use "the "header of family" as person's name on census event.
+On description we could use "the "header of family" as person's name on census event.
 === To share data ===

@@ Line 49: / Line 49: @@
 |}
-I agree, we could use "(event type) of person's name" on both event type (residence and census), maybe with the "header of family" as person's name on census event.
+On census' description we could use "the "header of family" as person's name on census event.
 === To share data ===

@@ Line 12: / Line 12: @@
   RESI 	{RESIDENCE} 	The act of dwelling at an address for a period of time.
   CENS 	{CENSUS} 	The event of the periodic count of the population for a designated
-                         locality, such as a
+                         locality, such as a national orstate Census.
-                        national orstate Census.
   TYPE 	{TYPE}   	A further qualification to the meaning of the associated superior tag.
                          The value does not have anycomputer processing reliability.

@@ Line 54: / Line 54: @@
 === To share data ===
-* with Gramps XML format (to Gramps), there is no problem, descriptions on event are safe.
+* Gramps XML format (from Gramps to Gramps): there is no problem, descriptions on event are safe.
-* but if the recipient's program ignores TYPE attribut (GEDCOM), then he could lose descriptions on event ...
+* Gedcom: if the recipient's program ignores TYPE attribut (GEDCOM), then he could lose descriptions on event ...
 == More information ==

@@ Line 11: / Line 11: @@
   RESI 	{RESIDENCE} 	The act of dwelling at an address for a period of time.
-  CENS 	{CENSUS} 	The event of the periodic count of the population for a designated locality, such as a
+  CENS 	{CENSUS} 	The event of the periodic count of the population for a designated
                          national orstate Census.
-  TYPE 	{TYPE}   	A further qualification to the meaning of the associated superior tag. The value does not
+  TYPE 	{TYPE}   	A further qualification to the meaning of the associated superior tag.
-                        have anycomputer processing reliability. It is more in the form of a short one or two word
+                        The value does not have anycomputer processing reliability.
                          note that should be displayed any time the associated data is displayed.

← Older revision		Revision as of 14:20, 19 July 2010
Line 1:		Line 1:
	[[Category:Documentation]][[Category:Tutorials]]		[[Category:Documentation]][[Category:Tutorials]]
−	{{languages~~\|Residence and census~~}}	+	{{languages}}

@@ Line 20: / Line 20: @@
 === Multiples places ===
-There is a lot of solutions :
+There are many solutions :
 * GEDCOM 5.5 allows a sub-division on place title separated by commas.
 But using a specific address as place title (or place attribute) might generate a lot of place objects on the same city or same district (no shared place object).
-* Gramps provides an Address tab on person editor.
+* GRAMPS provides an Address tab on person editor.
-But maybe an other GEDCOM issue, which could hide some useful informations for genealogical searchs !
+But maybe an other GEDCOM issue, which could hide some useful information for genealogical searches!
-* The most effective emplacement for setting address seems to be the event editor !!!
+* The most effective emplacement for setting address seems to be the event editor!
-Event objects are used on reports and displayed on views/tabs/dialogs. (see [[Why_residence_event_and_not_Address%3F]])
+Event objects are used on reports and displayed on views/tabs/dialogs. (see [[Why residence event and not Address%3F]])
 Most places deal with events (see Place Report)

@@ Line 55: / Line 55: @@
 * but if the recipient's program ignores TYPE attribut (GEDCOM), then he could lose descriptions on event ...
-== More informations ==
+== More information ==
 *[[Why_residence_event_and_not_Address%3F|why event rather than address]] ?
-*[[Recording_UK_Census_data]]
+*[[Recording UK Census data]]
-*[[Recording_FR_Census_data]]
+*[[Recording FR Census data]]