Translation Manager

[aussen2]

I am currently implementing a multi-lingual website on the basis of Web Quick Start (Alfresco Community 3.4d). As there is no out-of-the-box support for managing different translations of the same content in Share yet, I put the translations into different language folders and connected them via my own type of associations (ws:tranlsationOf and ws:translations). These associations are automatically established when a new translation is added (via workflows).

This method works just fine but form the viewpoint of the Alfresco repository the different translations are still just different content objects that exist independently of each other. Thus, multi-lingual support for search and other relevant things is limited. So I was happy to discover what seems to be your plans for introducing a translation manager for Web Quick Start in the code on HEAD. I assume that this will provide UI support in Share for facilitating the built-in multi-lingual capabilities of Alfresco. Could you provide some more information on this approach? I would also be interested in any information on how stable this feature already is.

Multi-lingual content management is a ver important aspect of my current project and if there is some native solution emerging in Web Quick Start I definitely want to adopt that for my project in order to guarantee the best possible compatibility with future versions of Alfresco.

[aussen2]

Okay, I will try an easier solution for now. What about adding an aspect that contains peer associations to all the translations of an asset? I could extend the TemporaryMultilingualAspect behavior to manage these associations. As far as I can see this behavior is already triggered whenever a new translation is added. Peer associations should work fine with publishing and in the web tier, shouldn't they? And as the assets are all cached in the web tier anyway retrieving the properties of the translations of an asset shouldn't have any impact on the performance. Do you see any problems with this solution?

[bremmington]

That seems like a reasonable approach, yes. Be a little careful of managing your associations when translations are deleted. I've seen cases where associations are not removed when nodes are archived. That may have been fixed, but just test for it.

[aussen2]

The client api (community version 3.4.d) does not return any associations from my new aspect when I use the getRelatedAssets function. I think you mentioned a change in this functionality in another forum thread (https://forums.alfresco.com/en/viewtopic.php?f=52&t=39253). Is that something that only works from 4.0 upwards? Or is this change already in 3.4.e (r26676)?

[bremmington]

Oh, sorry. My head's been in 4.0 for so long now I'm forgetting what functionality is available where 

The functionality that provides access to custom properties and associations went in on the 3.4 Enterprise stream initially, and, although it was immediately merged onto HEAD, this didn't happen until after 3.4.e. Given that a problem with the CMIS query engine in 4.0.a has caused WQS to break in that version, I don't have any brilliant suggestions to make right now for how to get to where you want to be. Once the issue on 4.0.a has been sorted out then I would suggest moving up to that.