Corpus configuration file contain wrong timespan
Closed this issue · 1 comments
matyaskopp commented
The end year is 2022, but the CZ corpus also contains 2023 data.
I don't know how the regi file is created if it is a bug in some script(fix needed) or a human error(will be fixed in the next release) due to manual modifications.
TomazErjavec commented
a human error
Yes, my error, sorry. Fixed now, also in concordancders.