From: Stephen G. <ste...@op...> - 2008-10-23 00:34:34
|
Hi All, I'm starting gramps up on windows and get the following message. D:\tempSVNPyFiles\gramps>d:\SVNGramps_build\src\gramps.py Date parser for English_Australia not available, using default Date displayer for English_Australia not available, using default I get the same error for gramps-3.0.0-1 gramps-3.1.0-SVN11184 gramps-3.0.3-1 Would something be missing from my installation, or do I have to create new code for a date parser/displayer for English_Australia Steve |
From: Brian M. <br...@gr...> - 2008-10-23 02:04:17
|
Stephen, > I'm starting gramps up on windows and get the following > message. > > D:\tempSVNPyFiles\gramps>d:\SVNGramps_build\src\gramps.py > Date parser for English_Australia not available, using > default > Date displayer for English_Australia not available, using > default > > I get the same error for > gramps-3.0.0-1 > gramps-3.1.0-SVN11184 > gramps-3.0.3-1 > > Would something be missing from my installation, or do I > have to create > new code for a date parser/displayer for English_Australia That's not really an error message. It is more of an informational message. The locale on your computer is set to "English_Australia". But we don't have a date parser associated with that locale. So we use the default instead (which happens to be "English_United-States". ~Brian |
From: Douglas S. B. <db...@cs...> - 2008-10-23 11:10:04
|
> Stephen, > >> I'm starting gramps up on windows and get the following >> message. >> >> D:\tempSVNPyFiles\gramps>d:\SVNGramps_build\src\gramps.py >> Date parser for English_Australia not available, using >> default >> Date displayer for English_Australia not available, using >> default >> >> I get the same error for >> gramps-3.0.0-1 >> gramps-3.1.0-SVN11184 >> gramps-3.0.3-1 >> >> Would something be missing from my installation, or do I >> have to create >> new code for a date parser/displayer for English_Australia > > That's not really an error message. It is more of an informational > message. The locale on your computer is set to "English_Australia". But we > don't have a date parser associated with that locale. So we use the > default instead (which happens to be "English_United-States". But it isn't very informative---one can't tell that it isn't an error. Perhaps the message should say what you just explained: NOTE: The locale on your computer is set to "X" but GRAMPS doesn't have a specific date parser for that locale. The current date parser is set to "Y". For more information (including how to change this), please see WEBPAGE. The WEBPAGE would be one that further explains how to change this, and links to how to write/request a new one. Any message that gets printed to the screen should be prefaced with NOTE, WARNING, or ERROR. Stephen, could you add a bug report at http://www.gramps-project.org/bugs/ making this suggestion? -Doug > ~Brian > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Brian M. <br...@gr...> - 2008-10-23 12:48:01
|
> > Stephen, > > > >> I'm starting gramps up on windows and get the > following > >> message. > >> > >> > D:\tempSVNPyFiles\gramps>d:\SVNGramps_build\src\gramps.py > >> Date parser for English_Australia not available, > using > >> default > >> Date displayer for English_Australia not > available, using > >> default > >> > >> I get the same error for > >> gramps-3.0.0-1 > >> gramps-3.1.0-SVN11184 > >> gramps-3.0.3-1 > >> > >> Would something be missing from my installation, > or do I > >> have to create > >> new code for a date parser/displayer for > English_Australia > > > > That's not really an error message. It is more of > an informational > > message. The locale on your computer is set to > "English_Australia". But we > > don't have a date parser associated with that > locale. So we use the > > default instead (which happens to be > "English_United-States". > > But it isn't very informative---one can't tell that > it isn't an error. > Perhaps the message should say what you just explained: > > NOTE: The locale on your computer is set to "X" > but GRAMPS doesn't have a > specific date parser for that locale. The current date > parser is set to > "Y". For more information (including how to > change this), please see > WEBPAGE. > > The WEBPAGE would be one that further explains how to > change this, and > links to how to write/request a new one. Any message that > gets printed to > the screen should be prefaced with NOTE, WARNING, or ERROR. > > Stephen, could you add a bug report at > http://www.gramps-project.org/bugs/ > making this suggestion? Changing the message would be pretty much inconsequential because 99% of Gramps users don't run Gramps from the command line and will never see the message no matter how descriptive it is. Maybe we need to add something to the user interface instead. Or, maybe we need to remove the message altogether. Stephen didn't complain about the date parsing because he doesn't have any date parsing problems. He only asked about the message. Removing the message would have saved everyone the conversation. ~BM |
From: Benny M. <ben...@gm...> - 2008-10-23 13:17:12
|
I think the message was added as a nod to the 1% of users using the command line: perhaps you are the person who wants to invest the time to code a date parser for your language.... A person who uses eg Slovak in gramps will quickly discover his months are not autmatically recognized in GRAMPS however. Benny 2008/10/23 Brian Matherly <br...@gr...> > > > Stephen, > > > > > >> I'm starting gramps up on windows and get the > > following > > >> message. > > >> > > >> > > D:\tempSVNPyFiles\gramps>d:\SVNGramps_build\src\gramps.py > > >> Date parser for English_Australia not available, > > using > > >> default > > >> Date displayer for English_Australia not > > available, using > > >> default > > >> > > >> I get the same error for > > >> gramps-3.0.0-1 > > >> gramps-3.1.0-SVN11184 > > >> gramps-3.0.3-1 > > >> > > >> Would something be missing from my installation, > > or do I > > >> have to create > > >> new code for a date parser/displayer for > > English_Australia > > > > > > That's not really an error message. It is more of > > an informational > > > message. The locale on your computer is set to > > "English_Australia". But we > > > don't have a date parser associated with that > > locale. So we use the > > > default instead (which happens to be > > "English_United-States". > > > > But it isn't very informative---one can't tell that > > it isn't an error. > > Perhaps the message should say what you just explained: > > > > NOTE: The locale on your computer is set to "X" > > but GRAMPS doesn't have a > > specific date parser for that locale. The current date > > parser is set to > > "Y". For more information (including how to > > change this), please see > > WEBPAGE. > > > > The WEBPAGE would be one that further explains how to > > change this, and > > links to how to write/request a new one. Any message that > > gets printed to > > the screen should be prefaced with NOTE, WARNING, or ERROR. > > > > Stephen, could you add a bug report at > > http://www.gramps-project.org/bugs/ > > making this suggestion? > > Changing the message would be pretty much inconsequential because 99% of > Gramps users don't run Gramps from the command line and will never see the > message no matter how descriptive it is. > > Maybe we need to add something to the user interface instead. Or, maybe we > need to remove the message altogether. Stephen didn't complain about the > date parsing because he doesn't have any date parsing problems. He only > asked about the message. Removing the message would have saved everyone the > conversation. > > ~BM > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Benny M. <ben...@gm...> - 2008-10-23 12:49:48
|
I do not agree this should be more than one line of output. 'Date parser for English_Australia not available, using default' is a valid sentence, and cannot be misunderstood. Making it longer will only annoy people that start from command line. Most that needs to happen is to add the locale as windows indicates it to the list of locales the default covers (at the bottom of the file) and the output will go away. That is, if Australians are happy with the US default. Benny 2008/10/23 Douglas S. Blank <db...@cs...> > > Stephen, > > > >> I'm starting gramps up on windows and get the following > >> message. > >> > >> D:\tempSVNPyFiles\gramps>d:\SVNGramps_build\src\gramps.py > >> Date parser for English_Australia not available, using > >> default > >> Date displayer for English_Australia not available, using > >> default > >> > >> I get the same error for > >> gramps-3.0.0-1 > >> gramps-3.1.0-SVN11184 > >> gramps-3.0.3-1 > >> > >> Would something be missing from my installation, or do I > >> have to create > >> new code for a date parser/displayer for English_Australia > > > > That's not really an error message. It is more of an informational > > message. The locale on your computer is set to "English_Australia". But > we > > don't have a date parser associated with that locale. So we use the > > default instead (which happens to be "English_United-States". > > But it isn't very informative---one can't tell that it isn't an error. > Perhaps the message should say what you just explained: > > NOTE: The locale on your computer is set to "X" but GRAMPS doesn't have a > specific date parser for that locale. The current date parser is set to > "Y". For more information (including how to change this), please see > WEBPAGE. > > The WEBPAGE would be one that further explains how to change this, and > links to how to write/request a new one. Any message that gets printed to > the screen should be prefaced with NOTE, WARNING, or ERROR. > > Stephen, could you add a bug report at http://www.gramps-project.org/bugs/ > making this suggestion? > > -Doug > > > ~Brian > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Stephen G. <ste...@op...> - 2008-10-23 22:02:17
|
Hi All, From my point of view, I think the warning is fine for unsupported locale. I was querying if something could be done to make English_Australia locale supported - hence the warning would go away. I haven't looked into the functionality behind date parser, .. what it provides. I've got an idea it's just for the months (JAN => 1 FEB => 2 etc. and text like 'before' and 'after'), in which case ya, we are fine with the US-defaults If it's got more to do with layout i.e. dd/mm/YYYY or mm/dd/YYYY , .. then we usually go with the British on this (dd/mm/YYYY), if the British are happy with US-defaults, then I expect we will be also. If the British have their own date parser, then we probably want that one. > add the locale as windows indicates it to the list of locales the default covers (at the bottom of the file) Which file would that be? Steve > I do not agree this should be more than one line of output. > > 'Date parser for English_Australia not available, using default' > > is a valid sentence, and cannot be misunderstood. Making it longer > will only annoy people that start from command line. > > Most that needs to happen is to add the locale as windows indicates it > to the list of locales the default covers (at the bottom of the file) > and the output will go away. That is, if Australians are happy with > the US default. > > Benny > > 2008/10/23 Douglas S. Blank <db...@cs... > <mailto:db...@cs...>> > > > Stephen, > > > >> I'm starting gramps up on windows and get the following > >> message. > >> > >> D:\tempSVNPyFiles\gramps>d:\SVNGramps_build\src\gramps.py > >> Date parser for English_Australia not available, using > >> default > >> Date displayer for English_Australia not available, using > >> default > >> > >> I get the same error for > >> gramps-3.0.0-1 > >> gramps-3.1.0-SVN11184 > >> gramps-3.0.3-1 > >> > >> Would something be missing from my installation, or do I > >> have to create > >> new code for a date parser/displayer for English_Australia > > > > That's not really an error message. It is more of an informational > > message. The locale on your computer is set to > "English_Australia". But we > > don't have a date parser associated with that locale. So we use the > > default instead (which happens to be "English_United-States". > |
From: Benny M. <ben...@gm...> - 2008-10-24 07:48:13
|
To make a patch for your australian: You open the file DateHandler/_DateHandler.py after the line LANG = locale.getlocale(locale.LC_TIME)[0] add: print LANG so as to see how for australia the LANG is given. Next you see the dictionaries: LANG_TO_PARSER and the dictionary LANG_TO_DISPLAY add there the australian LANG. For Parser use value DateParser, for Display use the DateDisplayEn. About the format of date not being correct, this depends on your installed locale. If the locale on your box says to use mm/dd/yyyy, then that will be used for numbers, otherwise dd/mm/yyyy This is line 199 in _DateParser, using tformat to see the order of day and month in your locale In display however, GRAMPS shows what you set in the preferences, so you control that. Note that we cannot display something like 12/12/2008, but we can parse it (the reason being that you could then set something different as display than what the parser takes, leading to an obvious error of months and days switching everytime you save.) Benny 2008/10/23 Stephen George <ste...@op...> > Hi All, > > From my point of view, I think the warning is fine for unsupported locale. > > I was querying if something could be done to make English_Australia > locale supported - hence the warning would go away. > > I haven't looked into the functionality behind date parser, .. what it > provides. > > I've got an idea it's just for the months (JAN => 1 FEB => 2 etc. and > text like 'before' and 'after'), in which case ya, we are fine with the > US-defaults > > If it's got more to do with layout i.e. dd/mm/YYYY or mm/dd/YYYY , .. > then we usually go with the British on this (dd/mm/YYYY), if the British > are happy with US-defaults, then I expect we will be also. If the > British have their own date parser, then we probably want that one. > > > add the locale as windows indicates it to the list of locales the > default covers (at the bottom of the file) > Which file would that be? > > Steve > > > I do not agree this should be more than one line of output. > > > > 'Date parser for English_Australia not available, using default' > > > > is a valid sentence, and cannot be misunderstood. Making it longer > > will only annoy people that start from command line. > > > > Most that needs to happen is to add the locale as windows indicates it > > to the list of locales the default covers (at the bottom of the file) > > and the output will go away. That is, if Australians are happy with > > the US default. > > > > Benny > > > > 2008/10/23 Douglas S. Blank <db...@cs... > > <mailto:db...@cs...>> > > > > > Stephen, > > > > > >> I'm starting gramps up on windows and get the following > > >> message. > > >> > > >> D:\tempSVNPyFiles\gramps>d:\SVNGramps_build\src\gramps.py > > >> Date parser for English_Australia not available, using > > >> default > > >> Date displayer for English_Australia not available, using > > >> default > > >> > > >> I get the same error for > > >> gramps-3.0.0-1 > > >> gramps-3.1.0-SVN11184 > > >> gramps-3.0.3-1 > > >> > > >> Would something be missing from my installation, or do I > > >> have to create > > >> new code for a date parser/displayer for English_Australia > > > > > > That's not really an error message. It is more of an informational > > > message. The locale on your computer is set to > > "English_Australia". But we > > > don't have a date parser associated with that locale. So we use the > > > default instead (which happens to be "English_United-States". > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Martin S. <mar...@ma...> - 2008-10-24 00:00:54
|
Brian Matherly <br...@gr...> writes: > > That's not really an error message. It is more of an informational > message. The locale on your computer is set to "English_Australia". > But we don't have a date parser associated with that locale. So we use > the default instead (which happens to be "English_United-States". This default is wrong for Australia, which follows British date conventions rather than US ones. -- Martin |
From: Brian M. <br...@gr...> - 2008-10-28 04:25:06
|
> > That's not really an error message. It is more of > an informational > > message. The locale on your computer is set to > "English_Australia". > > But we don't have a date parser associated with > that locale. So we use > > the default instead (which happens to be > "English_United-States". > > This default is wrong for Australia, which follows British > date > conventions rather than US ones. I could be wrong, but I'm not sure that we have a separate date parser for British locales. As far as I can tell (and I didn't write the code), we only have one English date parser. So unless someone writes a British/Australia date parser, it will all be the same. ~Brian |
From: Algis K. <aka...@pc...> - 2008-10-28 07:11:43
|
Brian, On Tue, 28 Oct 2008 15:24:58 Brian Matherly wrote: > > > That's not really an error message. It is more of > > My locale is 'English_Australian' (and it has been so for the last 60 years, albeit intermittently). However, ever since Australia adopted the SI (Standard International) units (Newton for force, kg for mass, meter for length), personally I use ISO standard date format. In this country, the usual date format is dd/mm/yyyy. When I attempt to enter ISO format (yyyy-mm-dd), gramps gui warns me by a change of colours of the field for date. If you want me to add the date format, tell me the name of the module to look at and be patient with me. I would need some guidance. Also, every so often I do get side tracked, hence the need for patience. Today I am waiting for a visit of one of our granddaughters, who decided to go to India to do some charity work in a few weeks time; and I have tax returns to finish for last fiscal year, ending 2008-06-30. In Australia, we sensibly use end of fiscal as far away of Christmas and New Year as possible. The point is that it would be some time before I would be able to start the job. What I would like to add to gramps as far as dates are concerned, is an ISO standard date format and an Australian one. OldAl. > > an informational > > > > > message. The locale on your computer is set to > > > > "English_Australia". > > > > > But we don't have a date parser associated with > > > > that locale. So we use > > > > > the default instead (which happens to be > > > > "English_United-States". > > > > This default is wrong for Australia, which follows British > > date > > conventions rather than US ones. > > I could be wrong, but I'm not sure that we have a separate date parser for > British locales. As far as I can tell (and I didn't write the code), we > only have one English date parser. So unless someone writes a > British/Australia date parser, it will all be the same. > > ~Brian > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge Build the coolest Linux based applications with Moblin SDK & win > great prizes Grand prize is a trip for two to an Open Source event anywhere > in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel -- Dr Algis Kabaila (PhD Eng) http://akabaila.pcug.org.au/StructuralAnalysis/ ------------------------------------------------ |
From: Brian M. <br...@gr...> - 2008-10-28 12:10:31
|
Al, > My locale is 'English_Australian' (and it has been > so for the last 60 years, > albeit intermittently). However, ever since Australia > adopted the SI > (Standard International) units (Newton for force, kg for > mass, meter for > length), personally I use ISO standard date format. > > In this country, the usual date format is dd/mm/yyyy. When > I attempt to enter > ISO format (yyyy-mm-dd), gramps gui warns me by a change of > colours of the > field for date. > > If you want me to add the date format, tell me the name of > the module to look > at and be patient with me. I would need some guidance. > Also, every so often > I do get side tracked, hence the need for patience. Today I > am waiting for a > visit of one of our granddaughters, who decided to go to > India to do some > charity work in a few weeks time; and I have tax returns to > finish for last > fiscal year, ending 2008-06-30. In Australia, we sensibly > use end of fiscal > as far away of Christmas and New Year as possible. The > point is that it would > be some time before I would be able to start the job. > > What I would like to add to gramps as far as dates are > concerned, is an ISO > standard date format and an Australian one. In the "DateHandler" module you will see many files - each for a different language. All you would need to do is implement one of those files for your locale. ~Brian |
From: Doug Morrison-C. <li...@ds...> - 2008-10-28 13:35:55
|
On Tue, 28 Oct 2008 04:43:40 -0700 (PDT) Brian Matherly <br...@gr...> wrote: > Al, > > > My locale is 'English_Australian' (and it has been > > so for the last 60 years, > > albeit intermittently). However, ever since Australia > > adopted the SI > > (Standard International) units (Newton for force, kg for > > mass, meter for > > length), personally I use ISO standard date format. > > In the "DateHandler" module you will see many files - each for a > different language. All you would need to do is implement one of > those files for your locale. > > ~Brian > I could be (and probably am) way wrong, but it looks to me as if the default English date handler (in _DateHandler.py itself) covers all the bases: ISO, day month year and month day, year. Maybe it just needs en-AU and en-GB being added into the default list around line 70??? I know nothing really about python, so I have probably missed something significant. But maybe this will simplify the job considerably ;-) Doug Morrison-Cleary |
From: Algis K. <aka...@pc...> - 2008-10-29 03:30:26
|
Benny, On Tue, 28 Oct 2008 19:20:41 Benny Malengier wrote: > ISO should work in GRAMPS in all locales, if not, something is wrong, a bug > or in your setup. > > And although there is only one english date parser, in linux the us locale > says mm/dd/yyyy and in uk dd/mm/yyyy, and GRAMPS understands that and > changes the Numerical entry as the locale says. > > So, normally, if locale in Australia is set correctly, all should just > work, no extra work required. > > Benny [...] I used a fairly recent gramps v3.0.4-0.SVN11199, invoked from CLI. I decided to add to my smallish data base my "favorite" person, Charlie Farlie, BA. He has a 25-th birthday today, so he was born 1983-10-29. So I started entering the date in the date field: 1983- . At this point the field turned to pink. I clicked on the date editor, which showed "Text" in the type box. For real people in the same data base, I ignored the "pink" warning and the dates were actually entered in ISO format. I don't know how gramps interprets it - probably as text. It may well be unable to calculate whatever a report wants to calculate. For Charlie Farlie, I then used the date editor: from left to right, entered 29 in day field, selected OCT from the drop down list for month then entered 1983 for year and clicked OK. This causes the date field to be filled with 1983-10-29. This should be reproducible. Just enter a name and try to enter yyyy-mm-dd into the date field. I sure would appreciate a verification of this behaviour. TIA, Al. |
From: Douglas S. B. <db...@cs...> - 2008-10-29 03:42:13
|
> Benny, > > On Tue, 28 Oct 2008 19:20:41 Benny Malengier wrote: >> ISO should work in GRAMPS in all locales, if not, something is wrong, a >> bug >> or in your setup. >> >> And although there is only one english date parser, in linux the us >> locale >> says mm/dd/yyyy and in uk dd/mm/yyyy, and GRAMPS understands that and >> changes the Numerical entry as the locale says. >> >> So, normally, if locale in Australia is set correctly, all should just >> work, no extra work required. >> >> Benny > [...] > > I used a fairly recent gramps v3.0.4-0.SVN11199, invoked from CLI. I > decided > to add to my smallish data base my "favorite" person, Al, [Don't know if that is a real person, but I'd be careful about putting real names/birthdates on the internets.] [snip] > entering > the date in the date field: 1983- . At this point the field turned to > pink. That would be correct: "1983-" is a badly formed date. You should just keep typing there to finish it off. Does that work for you? -Doug |
From: Algis K. <aka...@pc...> - 2008-10-29 07:10:46
|
Doug, On Wed, 29 Oct 2008 14:42:07 Douglas S. Blank wrote: > > Benny, > > > > On Tue, 28 Oct 2008 19:20:41 Benny Malengier wrote: > >> ISO should work in GRAMPS in all locales, if not, something is wrong, a > >> bug > >> or in your setup. > >> > >> And although there is only one english date parser, in linux the us > >> locale > >> says mm/dd/yyyy and in uk dd/mm/yyyy, and GRAMPS understands that and > >> changes the Numerical entry as the locale says. > >> > >> So, normally, if locale in Australia is set correctly, all should just > >> work, no extra work required. > >> > >> Benny > > > > [...] > > > > I used a fairly recent gramps v3.0.4-0.SVN11199, invoked from CLI. I > > decided > > to add to my smallish data base my "favorite" person, > > Al, > > [Don't know if that is a real person, but I'd be careful about putting > real names/birthdates on the internets.] > > [snip] > > > entering > > the date in the date field: 1983- . At this point the field turned to > > pink. > > That would be correct: "1983-" is a badly formed date. You should just > keep typing there to finish it off. Does that work for you? > > -Doug Yes, it kind of "works" in so far as it makes the date being shown correctly when person is displayed. As I did say, I have been entering the dates in this manner for other (real) people. What spooks me is that Benny tells me that gramps would not be able to use it in computation. After reading your email, I added an older brother of Charlie Farlie, Fred Farlie, Dr, who was born three years before Charlie - on 1980-10-29. Well, after 1980- is entered, the field turns pink; after 1980-10- is entered it turns off the warning and it stays turned off when the whole 1980-10-29 is entered. This is suggestive that the date is accepted. So what is really wanted now, is to find and apply a report that does calculate some dates. If it turns out that it all works OK, I would consider the unnecessary warning (pink colour of the field) being a confusing behaviour of gramps. A confusing behaviour that it would be desirable to eliminate. Thank you for looking into it this. I guess you realised already what gramps is doing! Of course, Charlie Farlie, BA, a private detective was a comical character from bygone days. In the egalitarian country that Australia is, the attachment of "BA" to the surname, whilst strictly correct, is in itself somewhat amusing (as amusing as is "Dr", which I sometimes employ - at times it is good to poke fun at oneself.) Thank you again, Al. |
From: Douglas S. B. <db...@cs...> - 2008-10-29 11:23:38
|
[snip] >> > entering >> > the date in the date field: 1983- . At this point the field turned to >> > pink. >> >> That would be correct: "1983-" is a badly formed date. You should just >> keep typing there to finish it off. Does that work for you? >> >> -Doug > > Yes, it kind of "works" in so far as it makes the date being shown > correctly > when person is displayed. As I did say, I have been entering the dates in > this manner for other (real) people. What spooks me is that Benny tells me > that gramps would not be able to use it in computation. After reading > your > email, I added an older brother of Charlie Farlie, Fred Farlie, Dr, who > was > born three years before Charlie - on 1980-10-29. Well, after 1980- is > entered, the field turns pink; after 1980-10- is entered it turns off the > warning and it stays turned off when the whole 1980-10-29 is entered. > This > is suggestive that the date is accepted. So what is really wanted now, is > to > find and apply a report that does calculate some dates. Al, If you want to interactively explore date calculations, try: http://www.gramps-project.org/wiki/index.php?title=Gramps_3.0_Wiki_Manual_-_Gramplets#Python_Gramplet There you can do things like: # What was the date 9 months before Oct. 25, 1962: > Date("1962-10-25") - (0, 9, 0) # How old was someone when they died: > Date("1942-02-21") - Date("2007-04-10") The date in quotes uses the same parser as a data entry field, so you can check to see if a particular format is giving you the correct date. > If it turns out that it all works OK, I would consider the unnecessary > warning > (pink colour of the field) being a confusing behaviour of gramps. > A confusing behaviour that it would be desirable to eliminate. We've discussed this, but I think the current method is a happy balance, once your know what it is doing. > Thank you for looking into it this. I guess you realised already what > gramps > is doing! > > Of course, Charlie Farlie, BA, a private detective was a comical character > from bygone days. Of course :) -Doug > In the egalitarian country that Australia is, the > attachment of "BA" to the surname, whilst strictly correct, is in itself > somewhat amusing (as amusing as is "Dr", which I sometimes employ - at > times > it is good to poke fun at oneself.) > Thank you again, > > Al. > |
From: Benny M. <ben...@gm...> - 2008-10-29 08:29:57
|
2008/10/29 Algis Kabaila <aka...@pc...> > Doug, > On Wed, 29 Oct 2008 14:42:07 Douglas S. Blank wrote: > > > Benny, > > > > > > On Tue, 28 Oct 2008 19:20:41 Benny Malengier wrote: > > >> ISO should work in GRAMPS in all locales, if not, something is wrong, > a > > >> bug > > >> or in your setup. > > >> > > >> And although there is only one english date parser, in linux the us > > >> locale > > >> says mm/dd/yyyy and in uk dd/mm/yyyy, and GRAMPS understands that and > > >> changes the Numerical entry as the locale says. > > >> > > >> So, normally, if locale in Australia is set correctly, all should just > > >> work, no extra work required. > > >> > > >> Benny > > > > > > [...] > > > > > > I used a fairly recent gramps v3.0.4-0.SVN11199, invoked from CLI. I > > > decided > > > to add to my smallish data base my "favorite" person, > > > > Al, > > > > [Don't know if that is a real person, but I'd be careful about putting > > real names/birthdates on the internets.] > > > > [snip] > > > > > entering > > > the date in the date field: 1983- . At this point the field turned to > > > pink. > > > > That would be correct: "1983-" is a badly formed date. You should just > > keep typing there to finish it off. Does that work for you? > > > > -Doug > > Yes, it kind of "works" in so far as it makes the date being shown > correctly > when person is displayed. As I did say, I have been entering the dates in > this manner for other (real) people. What spooks me is that Benny tells me > that gramps would not be able to use it in computation. After reading your > email, I added an older brother of Charlie Farlie, Fred Farlie, Dr, who > was > born three years before Charlie - on 1980-10-29. Well, after 1980- is > entered, the field turns pink; after 1980-10- is entered it turns off the > warning and it stays turned off when the whole 1980-10-29 is entered. This > is suggestive that the date is accepted. So what is really wanted now, is > to > find and apply a report that does calculate some dates. > > If it turns out that it all works OK, I would consider the unnecessary > warning > (pink colour of the field) being a confusing behaviour of gramps. > A confusing behaviour that it would be desirable to eliminate. I think most people type sufficiently fast to never see the field turn pink ;-) About calculation with date, in the View menu, activate the filter sidebar. Then in birth date, enter for example: before 1982 Gramps should give the correct births. With pink fields this is not possible. Benny |
From: Algis K. <aka...@pc...> - 2008-10-30 01:42:29
|
Benny, On Wed, 29 Oct 2008 19:29:50 Benny Malengier wrote: > 2008/10/29 Algis Kabaila <aka...@pc...> > > > Doug, > > > > On Wed, 29 Oct 2008 14:42:07 Douglas S. Blank wrote: > > > > Benny, > > > > > > > > On Tue, 28 Oct 2008 19:20:41 Benny Malengier wrote: > > > >> ISO should work in GRAMPS in all locales, if not, something is > > > >> wrong, > > > > a > > > > > >> bug > > > >> or in your setup. > > > >> > > > >> And although there is only one english date parser, in linux the us > > > >> locale > > > >> says mm/dd/yyyy and in uk dd/mm/yyyy, and GRAMPS understands that > > > >> and changes the Numerical entry as the locale says. > > > >> > > > >> So, normally, if locale in Australia is set correctly, all should > > > >> just work, no extra work required. > > > >> > > > >> Benny > > > > > > > > [...] > > > > > > > > I used a fairly recent gramps v3.0.4-0.SVN11199, invoked from CLI. I > > > > decided > > > > to add to my smallish data base my "favorite" person, > > > > > > Al, > > > > > > [Don't know if that is a real person, but I'd be careful about putting > > > real names/birthdates on the internets.] > > > > > > [snip] > > > > > > > entering > > > > the date in the date field: 1983- . At this point the field turned > > > > to pink. > > > > > > That would be correct: "1983-" is a badly formed date. You should just > > > keep typing there to finish it off. Does that work for you? > > > > > > -Doug > > > > Yes, it kind of "works" in so far as it makes the date being shown > > correctly > > when person is displayed. As I did say, I have been entering the dates > > in this manner for other (real) people. What spooks me is that Benny > > tells me that gramps would not be able to use it in computation. After > > reading your email, I added an older brother of Charlie Farlie, Fred > > Farlie, Dr, who was > > born three years before Charlie - on 1980-10-29. Well, after 1980- is > > entered, the field turns pink; after 1980-10- is entered it turns off the > > warning and it stays turned off when the whole 1980-10-29 is entered. > > This is suggestive that the date is accepted. So what is really wanted > > now, is to > > find and apply a report that does calculate some dates. > > > > If it turns out that it all works OK, I would consider the unnecessary > > warning > > (pink colour of the field) being a confusing behaviour of gramps. > > A confusing behaviour that it would be desirable to eliminate. > > I think most people type sufficiently fast to never see the field turn pink > ;-) If they look what they are doing, they will. If they are not interested in it, they indeed may miss it. The question is this - is it good to show an error and then change it to "no error". > > About calculation with date, in the View menu, activate the filter sidebar. > Then in birth date, enter for example: before 1982 > Gramps should give the correct births. With pink fields this is not > possible. Are you saying that if the field was pink and later ceases to be pink, it is a pink field? Thank you for your comment. I put my reply to drafts folder in order to have a second look at it. Hence my late reply. Also, in the meantime I received a valuable and sensible suggestion from Doug - thank you! Al. PS: Benny, I gather you live in Belgium. In around 1969 I spent a little over a year in Liege, which is very, very Francophone. Do you consider yourself Valon or Flamand? (Very important distinction...) I remember driving to Tongres - Tongeren and the sign 16 km from Liege, pointing to Liege in two languages. A true frontier between Belgium and Belgium! Al. > > Benny |
From: Martin S. <mar...@ma...> - 2008-10-24 09:00:22
|
Martin Steer <mar...@ma...> writes: > > This default is wrong for Australia, which follows British date > conventions rather than US ones. > Sorry for the noise. Benny's reply to the OP suffices (almost): >> About the format of date not being correct, this depends on your >> installed locale. If the locale on your box says to use mm/dd/yyyy, >> then that will be used for numbers, otherwise dd/mm/yyyy. This is >> line 199 in _DateParser, using tformat to see the order of day and >> month in your locale In display however, GRAMPS shows what you set in >> the preferences, so you control that. Note that we cannot display >> something like 12/12/2008, but we can parse it (the reason being that >> you could then set something different as display than what the >> parser takes, leading to an obvious error of months and days >> switching everytime you save.) ...but 12/12/2008 does display here, with locale = en_GB.utf8. What am I failing to understand? -- Martin |
From: Benny M. <ben...@gm...> - 2008-10-24 09:33:24
|
2008/10/24 Martin Steer <mar...@ma...> > Martin Steer <mar...@ma...> writes: > > > > > This default is wrong for Australia, which follows British date > > conventions rather than US ones. > > > > Sorry for the noise. Benny's reply to the OP suffices (almost): > > >> About the format of date not being correct, this depends on your > >> installed locale. If the locale on your box says to use mm/dd/yyyy, > >> then that will be used for numbers, otherwise dd/mm/yyyy. This is > >> line 199 in _DateParser, using tformat to see the order of day and > >> month in your locale In display however, GRAMPS shows what you set in > >> the preferences, so you control that. Note that we cannot display > >> something like 12/12/2008, but we can parse it (the reason being that > >> you could then set something different as display than what the > >> parser takes, leading to an obvious error of months and days > >> switching everytime you save.) > > ...but 12/12/2008 does display here, with locale = en_GB.utf8. What am I > failing to understand? Sorry, I spoke from memory, and I have Dutch here on my box. I see that DateDisplayEn has format 'Numerical' which uses the tformat of the locale to show numerical day as 12/12/2008. So Numerical means something different depending on the english locale used, and all is consistent (the display and the parsing are done according to the locale for numerical). It follows there is theoretically an error in the code, a month can be %b instead of %m .... The eyeballs method of open source in action.... Let's hope no english locales have default 02 jan 2008, which is %d %b %Y Benny > > > -- > Martin > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |