Simon Poole
Simon Poole
Just to explain to the behaviour in the first two examples: There are two different mechanisms at work which both only change the end time if there is actually a...
> > except if we are in strict mode (then it is an error). ^^^ time > > According to (current version of?) the specification, `16:00-04:00` is valid, though. It's...
This would seem to be related to https://github.com/simonpoole/OpeningHoursParser/issues/81
> However, a less ludicrous opening hours sign may say > > > "open on odd dates, i.e. every 1st, 3rd etc of each month" > > If I understood...
@archanox I had forgotten that this issue was still open :-). There was a 2021 GSOC project to write an evaluator, utilizing this parser: https://github.com/goodudetheboy/OpeningHoursEvaluator This works quite well as...
https://github.com/simonpoole/OpeningHoursFragment/issues/14
In principle _Wd_ could be supported in a non-conflicting way, but it would need a clear definition (and even if that boils down to "the days considered as work days...
https://github.com/simonpoole/OpeningHoursParser/commit/732edc67d642f28e01658d711abea39b2a5d1bb5 adds some translations of "to" for use in non-strict mode. I've had a look at supporting 4 digit times, but it is a bad case of diminishing returns, ~10...
> > > What do you mean with > > > ~10 changes in 160'000 examples > > ? It changed the parsing of ~10 of the values from our...