Geographic-region-based resource search

Description

We have a fair number of resource bundle files that contain nothing but "%%Parent { en_150 }" or something similar. These exist to because if they didn't exist at all, the resource-bundle search code would fall back to a resource bundle containing the wrong thing. This is because the resource-bundle search code simply handles missing resource bundle files by lopping fields off the locale ID and trying again. That is, if you ask for en_VA, we find that en.VA.txt doesn't exist and fall back to en.txt. But en.txt contains US English locale data where what we really want is European English locale data. We end up adding an en_VA.txt just so that we can specify that it should fall back to en_150. [The same thing happens for en_001 and es_419, and probably also for other languages, such as pt_BR.]

The problem is that we have no mechanism analogous to the %%Parent directive for when resource files don't exist at all. And yet we do have enough data in other resources to know when our search should do something other than lop fields off the end of the locale ID. Using this would allow us to get rid of the otherwise-empty locale files, and might also let us get rid of the %%Parent directives in many other locale files (because it'd happen by default).

Assignee

Rich Gillam

Reporter

Rich Gillam

Components

Labels

None

Reviewer

None

Priority

medium

Time Needed

None

Fix versions

Configure