Hi Eugene,
Eugene Yudin wrote,
Yes. In that particular case loop iterates through
en_US (from buildroot),
en_US and en_GB.
Of cause, that list can be patched but I don't know if that's correct.
It's look a bit strange if user passes locale which actually absent.
Waldemar, what you think about it?
I made several tests with different locales (en_US, en_GB, ru_RU, C.UTF-8 and
C).
The generated header is the same for all the above locale except pure C.
Comment in the same makefile tells about problem with some locales.
I think it would be better to use C locale for fallback.
I attached the tested patch to modify fallback behavior based on Arnout draft.
I also changed the order of calls to raise priority of C.UTF-8 locale.
Looks good to me. First trying the user configured locale (.UTF-8)
and if it does not exist fallback to C.UTF-8.
Not sure if we should do configured locale (en_US.UTF-8) then
C.UTF_8 and then even C, when C doesn't build workable output?
best regards
Waldemar