That's a good question...we're still trying to work out those details. This is the way Lithium has recommended we go. We've seen the community-level pages handled on other Lithium-based sites that apparently have the same single-instance structure we do, so hopefully we can also solve that problem.
So it sounds like I'm going to need to get the language from the page, perhaps using CommunityJsonObject since I see that has node IDs which could identify the language for me thanks to our naming convention. I was just hoping for a cleaner solution.
Thanks.