Multi-Region + Multi-Language?
Has anyone ever done a multi-region + multi-language implementation?
The very specific use case is starting with English, and moving to American English, American Spanish, Canadian English, Canadian French, Mexican Spanish, and Mexican English.
Regions are very important because even within english, something like the ADA (Americans with Disabilities Act) isn't applicable in Canada, so within english there needs to be multi-region content.
We could use the translatable package but I have worries about conflicting with the
<html lang=...> tag. Are there specific region tags to use for markup? We could always build out new locales using a custom separator and pre-parse that before lang=... but it would be great to inform Google and other crawlers that this content is meant for consumption in a specific region.
Does anyone have any ideas about how to go about this? I'm going to guess that the multi-lingual package can handle both and we need to come up with some additional schema for further granularity between regions?
Would be awesome to have some clarification or even just thoughts on this from someone else before we really go down a committal path.3 Replies
Or I suppose that would be the google spec for lanuage suffixed by region? So the languages we create for translatable possibilities would all have to be
en-ca
fr-ca
en-us
es-us
es-mx
en-mx
yeah, that's exactly how I would go about it, use those in translatable.php. now you may have different content, not just translations of the same content, so the language switcher may not be the most relevant. We've done it at the block level too for localized content, where each block can be published to different regions
Thank you, very much appreciate the second set of eyes and will pursue this route then