Re: Can't get natural language recognition to work
- From: Jim Nelson <jim yorba org>
- To: Hugo Osvaldo Barrera <hugo barrera io>
- Cc: california-list gnome org
- Subject: Re: Can't get natural language recognition to work
- Date: Tue, 21 Oct 2014 15:57:08 -0700
Thanks for your patience in my response.
Parsing time is not locale-specific in California. It attempts to recognize a variety of forms and translates them no matter the format.
Unfortunately, one format that is too ambiguous for California is "1900". Because this can also be a street address number (and hence a location) the parser does not strictly convert it to a time. For 24-hour time, the only format recognized is "19:00". (This very example, coincidentally, is discussed on the Quick Add help page at
https://wiki.gnome.org/Apps/California/HowToUseQuickAdd)
I'm open to hearing suggestions on other ways time formatting can be improved. For example, 1900h or 1900hs would be a possibility, but of course that looks limited to certain Western languages. There might be other common formats I'm not familiar with. Do you have any suggestions?
-- Jim
On Wed, Oct 8, 2014 at 6:22 PM, Hugo Osvaldo Barrera <hugo barrera io> wrote:
I've been trying to add an event using the natural language feature, but I just
can't get it to work. :(
I'm clicking on a day and typing "Reunión con J at 1900" ("Reunión con J" is
the name I want for my event), but it just adds the whole thing as an event
name, and makes this a full-day event.
I've tried the following variations:
At 1900hs reunión con J
At 1900 reunión con J
Reunión con J at 1900
Reunión con J at 1900hs
None of these were recognized properly.
I *did* try to use US-formated time: "Reunión at 7pm", and this *did* work,
however, my locale is set to properly, and does not use US-format for the time
(or date for what that matters):
$ env | egrep ^LC
LC_MONETARY=en_US.UTF-8
LC_NUMERIC=en_GB.UTF-8
LC_COLLATE=C
LC_TIME=en_DK.UTF-8
I'm using version 0.2.0, git commit gc09c3d3.
Do I need to do anything else? Am I doing something wrong?
Thanks,
--
Hugo Osvaldo Barrera
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below the quoted text?
[
Date Prev][Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]