> Suppose for some reason, the system decides that en_GB is a valid > locale, but should actually be called en_UK as the closest available.
The closest match will always be found by dropping variant first, and then by dropping region. So if en_GB is valid, so either locales en_GB or en will be used. In the example you describe any resource file will be loaded with closest match locale "en", and both requests using en_GB and en_UK will use this resource. ~mck
signature.asc
Description: This is a digitally signed message part
