Date Handler - Revision history

Patsyblefebre: /* Calendars */ space

2013-02-01T03:58:53Z

‎Calendars: space

Patsyblefebre: /* Calendars */ Japanese

2013-02-01T03:58:14Z

‎Calendars: Japanese

Patsyblefebre: /* How to test a date handler for your locale */ {{Man menu|

2013-02-01T03:57:31Z

‎How to test a date handler for your locale: {{Man menu|

Patsyblefebre: Gramps

2013-01-20T01:12:14Z

Gramps

Patsyblefebre: /* Tests with command-line */ update 404ed link

2012-12-26T22:14:40Z

‎Tests with command-line: update 404ed link

Patsyblefebre: /* Testing into GRAMPS */ update 404ed link

2012-12-26T22:13:18Z

‎Testing into GRAMPS: update 404ed link

Romjerome: /* Tests with command-line */

2012-04-01T11:38:55Z

‎Tests with command-line

Romjerome: /* Testing into GRAMPS */

2012-04-01T11:38:14Z

‎Testing into GRAMPS

Romjerome at 11:36, 1 April 2012

2012-04-01T11:36:49Z

Romjerome: /* Tests with command-line */

2012-04-01T06:20:07Z

‎Tests with command-line

@@ Line 45: / Line 45: @@
 Gramps uses Gregorian calendar by-default, but also supports Julian calendar, Hebrew calendar, Islamic calendar, Persian calendar, French Republican calendar and Swedish calendar.
 It is possible to add new one, like Chinese calendar, Indian Civil calendar, Bahá'í calendar, Mayan calendar, Zoroastrian calendar or Japanese calendar ... into gen/lib/calendar.
 We need to have rules which properly convert this new calendar to sdn (serial date number) and from sdn to calendar.

@@ Line 45: / Line 45: @@
 Gramps uses Gregorian calendar by-default, but also supports Julian calendar, Hebrew calendar, Islamic calendar, Persian calendar, French Republican calendar and Swedish calendar.
-It is possible to add new one, like Chinese calendar, Indian Civil calendar, Bahá'í calendar, Mayan calendar, Zoroastrian calendar or Japonese calendar ... into gen/lib/calendar.
+It is possible to add new one, like Chinese calendar, Indian Civil calendar, Bahá'í calendar, Mayan calendar, Zoroastrian calendar or Japanese calendar ... into gen/lib/calendar.
 We need to have rules which properly convert this new calendar to sdn (serial date number) and from sdn to calendar.

@@ Line 52: / Line 52: @@
 ===Testing into Gramps===
-You could have a look at [http://svn.code.sf.net/p/gramps/code/trunk/gramps/plugins/tool/dateparserdisplaytest.py dateparserdisplaytest.py] debug tool on SVN and available under '''Menu -> Tools -> Debug ->'''.
+You could have a look at [http://svn.code.sf.net/p/gramps/code/trunk/gramps/plugins/tool/dateparserdisplaytest.py dateparserdisplaytest.py] debug tool on SVN and available under {{Man menu|Menu -> Tools -> Debug ->}}.
 # Add this debug tool under your ''.gramps/plugins34'' directory
 # Create a <u>new empty Family Tree</u>.
-# Go on '''Menu -> Tools -> Debug -> test for date parser and displayer'''.
+# Go on {{Man menu|Menu -> Tools -> Debug -> test for date parser and displayer}}.
 # Compare entries on [[Gramps_3.4_Wiki_Manual_-_Main_Window#Events_Category|Events View]].

@@ Line 1: / Line 1: @@
-Rationale and requirements for the localized Date Handler module for GRAMPS.
+Rationale and requirements for the localized Date Handler module for Gramps.
 ==Why have different date handlers?==
@@ Line 5: / Line 5: @@
 By providing date handlers, several problems are resolved.
-* Dates entered by users of that language in almost any form can be parsed by GRAMPS.
+* Dates entered by users of that language in almost any form can be parsed by Gramps.
 * The displayed dates will look clear and correct to the users.
 * Translators do not have to worry about translating regular expressions like <code>(from|before|between)</code>.
@@ Line 32: / Line 32: @@
 ::where <code>MyDateParser</code> and <code>MyDateDisplay</code> are the classes defined for parsing and displaying, and the items in quotes are language identifiers that '''may possibly''' be associated with your language. For example, different systems use <code>ru</code>, <code>RU</code>, <code>ru_RU</code>, <code>koi8r</code>, <code>ru_koi8r</code>, <code>russian</code>, <code>Russian</code>, <code>ru_RU.koi8r</code>, etc. to identify the Russian language.
-Then you need to import the parser to GRAMPS by adding
+Then you need to import the parser to Gramps by adding
      import _Date_xx
 line to __init__.py file located in the same directory.
@@ Line 50: / Line 50: @@
 ==How to test a date handler for your locale==
-===Testing into GRAMPS===
+===Testing into Gramps===
 You could have a look at [http://svn.code.sf.net/p/gramps/code/trunk/gramps/plugins/tool/dateparserdisplaytest.py dateparserdisplaytest.py] debug tool on SVN and available under '''Menu -> Tools -> Debug ->'''.

@@ Line 64: / Line 64: @@
   $ python src/date_test.py
-* There is an other debug test under [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/gen/lib/test/date_test.py gen.lib] (see [[Unit_Test_Quickstart#Using_Your_Unit_Test|Unit test]]).
+* There is an other debug test under [http://svn.code.sf.net/p/gramps/code/trunk/gramps/gen/lib/test/date_test.py gen.lib] (see [[Unit_Test_Quickstart#Using_Your_Unit_Test|Unit test]]).
   $ export PYTHONPATH=''{path_to_/src}''
 It returns false positive/negative with modifier, calendar, quality, span, range dates, because it does not use translated words! You can try to generate a localized testing module by translating english words:

@@ Line 54: / Line 54: @@
 You could have a look at [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/plugins/tool/DateParserDisplayTest.py DateParserDisplayTest] debug tool on SVN and available under '''Menu -> Tools -> Debug ->'''.
-# Add this debug tool under your ''.gramps/plugins33'' directory
+# Add this debug tool under your ''.gramps/plugins34'' directory
 # Create a <u>new empty Family Tree</u>.
 # Go on '''Menu -> Tools -> Debug -> test for date parser and displayer'''.
-# Compare entries on [[Gramps_3.3_Wiki_Manual_-_Main_Window#Events_Category|Events View]].
+# Compare entries on [[Gramps_3.4_Wiki_Manual_-_Main_Window#Events_Category|Events View]].
 ===Tests with command-line===

@@ Line 62: / Line 62: @@
 * Download [[Media:Date_test.gz|python script]], copy the file under src (or gramps) directory, then under a console:
   $ python src/date_test.py
-* There is an other debug test under [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/gen/lib/test/date_test.py gen.lib] (see [[Unit_Test_Quickstart#Using_Your_Unit_Test|Unit test]]), but it returns false positive/negative with modifier, calendar, quality, span, range dates, because it does not use translated words!
+* There is an other debug test under [http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/gen/lib/test/date_test.py gen.lib] (see [[Unit_Test_Quickstart#Using_Your_Unit_Test|Unit test]]).
-But you can try to generate a localized testing module by translating english words:
+ $ export PYTHONPATH=''{path_to_/src}''
   en: ("between 1750 and 1752", "between 1749 and 1750", True),

← Older revision		Revision as of 06:20, 1 April 2012
Line 62:		Line 62:

	* Download [[Media:Date_test.gz\|python script]], copy the file under src (or gramps) directory, then under a console:		* Download [[Media:Date_test.gz\|python script]], copy the file under src (or gramps) directory, then under a console:
		+	$ export PYTHONPATH=''{path_to_/src}''
	$ python src/date_test.py		$ python src/date_test.py