On Wed, Aug 24, 2016 at 02:37:30AM +0200, Vincent Lefevre wrote:
> On 2016-08-23 11:06:22 -0700, Kevin J. McCarthy wrote:
> > I think even keeping a $locale alias is still better with the changes
> > made.  $locale no longer affects the index or various other output, so
> > even goofed-up, it causes much fewer problems.  Perhaps we could create
> > the alias but not document it.  Or document it but mark it as
> > deprecated, and delete it in e.g. 1.9.
> 
> It would be bad to keep it if it no longer has the same behavior.
> An error due to the fact that the variable no longer exists is
> better than a silent change of the behavior, which could confuse
> the user, who may think that something is broken on his system.

In general, I agree, but I'm not sure that's true in this case.

We've merely reduced the effect of the (proposed alias) $locale.  Other
places it used to affect, such as the index dates, will now be
controlled by the user's locale environment variables.  I suspect that
most users who have customized $locale for the index dates won't notice
any change.

I like the idea of just getting it done and over with, but sympathize
with Eike, who has multiple environments.  Will deprecating and removing
a $locale alias over one major release really make the problem worse?

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

Attachment: signature.asc
Description: PGP signature

Reply via email to