Collin Funk <[email protected]> writes:

> Paul Eggert <[email protected]> writes:
>
>> On 2025-11-07 12:13, Basil L. Contovounesios wrote:
>>> Is there a reason not to match Unicode en dashes too?
>>
>> Not that I know of.
>
> Okay with me as well. I can add it and some simple test cases later
> today.
>
> No complaints if anyone beats me to it, of course. :)

Actually the change isn't obvious since we base it off of the file
extension, e.g. "--" for Texinfo files.

Perhaps we need an optional UPDATE_COPYRIGHT_YEAR_SEPARATOR environment
variable to determine what is used when converting:

    2001, 2002, 2003, 2004

into:

   2001 - 2004

For existing ranges we can use a capture group and preserve the existing
dash. The default if unset would just be the existing behavior.

I'll think about it for a bit.

Collin

Reply via email to