uptime: Avoid overriding more locale categories than necessary

[markj]

Summary

uptime(1) prints floating point numbers to represent the current load
averages. When emitting JSON, these numbers cannot use a comma as the
decimal separator. Commit bd490be57438 fixed a bug along these lines,
but in so doing it overrides all locale categories. As a result, we
emit 12h time in non-text mode, but for that field we should probably
just respect the user's configured locale.

PR: 290328
Fixes: bd490be57438 ("w(1): fix libxo output being locale dependant")

[des]

I don't think this is the correct solution either. For one, it is a local fix for a problem that affects all libxo consumers. For another, it will use the wrong decimal separators when emitting HTML (which should be localized, but won't if this patch is committed). I think libxo should be modified to always use the C locale when formatting numbers in json output, and bd490be57438 should be reverted.

[markj]

In D53539#1222315, @des wrote:

I don't think this is the correct solution either. For one, it is a local fix for a problem that affects all libxo consumers. For another, it will use the wrong decimal separators when emitting HTML (which should be localized, but won't if this patch is committed). I think libxo should be modified to always use the C locale when formatting numbers in json output, and bd490be57438 should be reverted.

This all makes sense. @phil do you have any comments on the libxo side of things? Does libxo have a particular stance on this kind of problem?

[bapt]

In D53539#1222315, @des wrote:

I don't think this is the correct solution either. For one, it is a local fix for a problem that affects all libxo consumers. For another, it will use the wrong decimal separators when emitting HTML (which should be localized, but won't if this patch is committed). I think libxo should be modified to always use the C locale when formatting numbers in json output, and bd490be57438 should be reverted.

I agree, we should fix this in libxo itself, libxo is broken in many places regading locales and encodings

[bapt]

This comment was removed by bapt.