Bugzilla

Proposal: We want to be able to have a non US specific feeds for en-US browsers outside of the US.

Problem: There are only three English locale browser builds, en-US, en-CA, and en-GB, the rest use one of those three. Our current system only looks at locale, limiting our feeds to one of those three.

For example:

1. en-US browsers in the US region get the en-US feed. Pretty logical.
2. en-GB browsers in the GB region get the en-GB feed. Also works.
3. de browsers in the DE region get the de feed. This works because it's not English.

These all make sense, but if we keep expanding these, it starts to get weird.

4. en-GB browsers in the IR region get the en-GB feed. Not an Irish or generic feed.
5. en-US browsers in the IN region get the en-US feed. not en English India feed or generic feed.

Would an Irish or India feed make more sense? Currently we cannot do that.

Options:
1. Let the server look at the geo/lang in the header, or similar, and the locale we pass. With these three bits of info, the server can make the decision on what to return.
2. Have the client pass along region with locale. Server can then make the decision on what to pass.
3. Have the client infer and update the locale code based on region. Example, if the client sees the locale code en-US and region as IR, we can pass in en-IR. This seems brittle to me, and also confusing because it suggests a browser locale that doesn't exist.

Proposal: We want to be able to have non US feeds for en-US browsers outside of the US.

Problem: There are only three English locale browser builds, en-US, en-CA, and en-GB, the rest use one of those three. Our current system only looks at locale, limiting our feeds to one of those three.

For example:

1. en-US browsers in the US region get the en-US feed. Pretty logical.
2. en-GB browsers in the GB region get the en-GB feed. Also works.
3. de browsers in the DE region get the de feed. This works because it's not English.

These all make sense, but if we keep expanding these, it starts to get weird.

4. en-GB browsers in the IR region get the en-GB feed. Not an Irish or generic feed.
5. en-US browsers in the IN region get the en-US feed. not en English India feed or generic feed.

Would an Irish or India feed make more sense? Currently we cannot do that.

Options:
1. Let the server look at the geo/lang in the header, or similar, and the locale we pass. With these three bits of info, the server can make the decision on what to return.
2. Have the client pass along region with locale. Server can then make the decision on what to pass.
3. Have the client infer and update the locale code based on region. Example, if the client sees the locale code en-US and region as IR, we can pass in en-IR. This seems brittle to me, and also confusing because it suggests a browser locale that doesn't exist.