Resolution: Won't Fix
Affects Version/s: None
Fix Version/s: None
I know this is a big one and which afaik so far was intentionally left out of the spec. Right now JCR does not cover i18n at all. There are obviously different strategies, like namespacing the property names for different locales, or storing the translateable content pieces in child nodes .. or referencing nodes with the translations etc. Another topic are fallback rules, ie. it might make sense to show content in english if there is no text in german for the given node/property.
For PHPCR we have actually created a solution that abstracts this inside PHPCR ODM (a hibernate like layer on top of PHPCR):
But its obviously not so trivial to then deal with this in the context of search:
At any rate the question is if i18n might be a topic that eventually could be covered in the core spec?