Matteo

Thank you for your answer. > So I'm wary of adding anything here: the 'from' feels to me like an optional part of the text not a required part of...

> what I'm wondering is if you need it if you write the range without a word in it, e.g. do you write da X-Y kg or not? Even then,...

Thank you very much. Meanwhile, I would like to ask an off-topic question that perhaps does not need a separate discussion: why is it necessary to specify the `locale` option...

I imagined a similar response, but it leaves me a bit puzzled. When regular types are used the inconsistency is obvious, but as pointed out in some discussions on tex.stackexchange.com,...

No field should be dynamically deleted, nor `sortkey` field should be dynamically populated. The issue is only about using a different sorting scheme for a specific entry type. In the...

I admit that I'm not intimately familiar with how "sourcemapping" works, but my use case (as written above) involves that the non-standard driver using both the `eventdate` and `date` fields...

> You can already do that with the "sourcemapping" feature - replace/substitute fields during .bib parsing on a per-type basis. You are right, sorry. I lost sight of the bigger...

> You can just copy eventdate to date as that will sort first and is of the same type. It's not recommended to use the legacy year field whenever possible....

Thanks for the help, but the proposed solution, as the regular expression is set up, only works with `eventdate` fields containing different years. Consider, for example: `eventdate = {1000-01-01}`; `eventdate...

> You would just populate `month` and `day` from `eventdate`. Does this mean that the only solution is to create a custom sorting template? If so, we return to the...