We have a client website that has English (/en/) as a **default language**, and we've created other languages in preparation for translation and globalizing the site. We've turned on item level language fallback and field level language fallback. We've also turned on "Enforce Version Presence". One of the client requirements is to regionalize certain pieces of content so that only certain items show up within certain language/regions.

For our Spanish language, English is our language fallback and it is working correctly.

With Spanish (Mexico) selected, I've created a product page in Spanish (Mexico) (/es-mx/), and I can see the version just fine, however it also creates an English version (because it's the default language of the site?) and I can't find a way to remove the english version successfully.

I've Unchecked **Enable Item Fallback** and checked **Enforce Version Presence**, as well as made the English version **unpublishable**. I've been able to switch to the Web database and remove the english version, and everything works as expected, /en/product-page comes back as a 404, while the /es-mx/product-page displays as expected. 

The moment I try to publish the Spanish version of the page, the English version gets re-created within the web database even with the English version marked as unpublishable, and it's now accessible through /en/product-page.

Is it possible this is a bug, or is this working as intended and I have to custom develop an alternate solution to get around this (item resolver pipeline?).