View Single Post
Old 09-21-2017, 08:47 AM   #384
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by dsestero View Post
but: do we really need this detailed matching? Would'nt be possible just to match everything from the pipe sign to the end of line? In that way everybody would get the date/time string in his/her own language and the code would be simpler and more general. What do you think?
Internally, the date/time string is converted to a timestamp. That is used in a few ways including sorting and as part of the key. And as part of the mechanism for merging annotations that have been fetched over time.

Also, I realised I was wrong about the matching for Italian. It should be working. But, the example file you sent, the month for a lot of the entries is "Luglio". The code I have has this in lower case only. That will break the parsing of the timestamp.

Last edited by davidfor; 09-21-2017 at 09:42 AM.
davidfor is offline   Reply With Quote