LTSP scripts break with Estonian locale

this highlights a number of problems in much of our code; I suspect a few uses of "sort" will also be impacted by locale settings.

From a quick glance at LTSP (not including LDM), I've found such code used by "tr", "sed", "expr", and even "perl" where they may not consistantly use the same regex.

We may need to selectively force the locale to C or C.UTF-8 for certain operations...

Looks like we need a bit of an audit...

Hi again, one potential fixes would be sourcing /etc/default/locale right before LDM starts. This way initscripts would not be affected by the locales.

Test case:
# locale-gen et_EE.UTF-8
# echo _abcdefghijklmnopqrstuvwxyz_ | LANG=et_EE.UTF-8 LANGUAGE= LC_ALL= sed 's/[a-z]//g'
_tuvwxy_
# echo _abcdefghijklmnopqrstuvwxyz_ | LANG=et_EE.UTF-8 LANGUAGE= LC_ALL= sed 's/[[:alpha:]]//g'
__

I.e. the locale needs to be generated before it's functional,
and LANGUAGE and LC_ALL need to be unset in order for LANGUAGE to take effect.

Note that `tr` seems unaffected, maybe its developers are automatically replacing [a-z] with [[:alpha:]] internally.

I think that any occurrences of [a-z] in the code should be fixed whether we also decide to use LANG=C.UTF-8 or not.

Fix committed in
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2664
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/revision/1579

The part about setting/unsetting LANG, LANGUAGE, LC_ALL etc should be reviewed again in LTSP 6, where LDM will be removed, systemd will be properly supported etc.

Fix released in LTSP 5.5.5.