Is there any support for cm:mlContainer in the web client?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2007 04:41 AM
Hi,
Its looks like the repository has full multilingual document support.. However, I can find any support in the web client?
I would expect something like "Create Multilingual Content" alongside the "Create space" option?
Just not implemented yet or am I missing something?
Damon.
Its looks like the repository has full multilingual document support.. However, I can find any support in the web client?
I would expect something like "Create Multilingual Content" alongside the "Create space" option?
<type name="cm:mlContainer"> <title>Multilingual Container</title> <parent>sys:container</parent> <associations> <child-association name="cm:mlChild"> <source> <mandatory>false</mandatory> <many>false</many> </source> <target> <class>cm:mlDocument</class> <mandatory>true</mandatory> <many>true</many> </target> </child-association> </associations> <mandatory-aspects> <aspect>cm:versionable</aspect> </mandatory-aspects> </type>
Just not implemented yet or am I missing something?
Damon.
Labels:
- Labels:
-
Archive
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2007 05:59 AM
Hi,
This is support for one of our customers. They have written the implementations that manipulate the cm:mlContainer and associated child files. We don't have any plans for extending the ML services any further, but all the necessary hooks are in place.
The only default visible ML support is available via the user preferences page, Content Language Filter. You might have noticed that the cm:titled aspect properties are of type mltext. You can therefore enter different values for the title and description of documents and spaces depending on the particular value selected for the Content Filter Language.
Regards
This is support for one of our customers. They have written the implementations that manipulate the cm:mlContainer and associated child files. We don't have any plans for extending the ML services any further, but all the necessary hooks are in place.
The only default visible ML support is available via the user preferences page, Content Language Filter. You might have noticed that the cm:titled aspect properties are of type mltext. You can therefore enter different values for the title and description of documents and spaces depending on the particular value selected for the Content Filter Language.
Regards

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2007 08:13 AM
Yes, I've been looking in more detail now and have a custom action calling the mltranslation service.. Looks like it will do exactly what we need so far..
Regards,
Damon.
Regards,
Damon.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2007 11:45 AM
Hello,
I'm very interested about this, can you explain me how can i do that??
Thanks
Hector Martin
Yes, I've been looking in more detail now and have a custom action calling the mltranslation service..
I'm very interested about this, can you explain me how can i do that??
Thanks
Hector Martin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2007 06:39 AM
Hi,
We have a service that will allow you to manipulate content in an multilingual manner, written by Philippe Dubois and myself. The service makes use of the cm:mlContainer to link content together according to language. It has the notion of an edition. Apart from the masking and manipulation of multilingual properties (as explained above), there is no UI or any other client code that uses the MultilingualContentService. See the org.alfresco.repo.model.ml package for the implementation of the service provided by the interface org.alfresco.service.cmr.ml.MultilingualContentService.
Regards
We have a service that will allow you to manipulate content in an multilingual manner, written by Philippe Dubois and myself. The service makes use of the cm:mlContainer to link content together according to language. It has the notion of an edition. Apart from the masking and manipulation of multilingual properties (as explained above), there is no UI or any other client code that uses the MultilingualContentService. See the org.alfresco.repo.model.ml package for the implementation of the service provided by the interface org.alfresco.service.cmr.ml.MultilingualContentService.
Regards

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2007 11:01 AM
Hi Derek,
you said:
I'm using the v2.1.0 (482) Community.
I would expect to be able to add translations for the properties of a space; is it possible to configure this by adding a kind of
Translatable aspect to the properties of a custom space?
Do you have another idea?
Thanks in advance,
Gilles
you said:
You can therefore enter different values for the title and description of documents and spaces depending on the particular value selected for the Content Filter Language.but I can't find out how to enter the different translation for the title and description via the web client !? I added an aspect 'Translatable' to a space, but the only consequence is the possibility to add multiple paths as value for a 'Translations' property. (Actualy, it's not clear, what is the translation of what?)
I'm using the v2.1.0 (482) Community.
I would expect to be able to add translations for the properties of a space; is it possible to configure this by adding a kind of
Translatable aspect to the properties of a custom space?
Do you have another idea?
Thanks in advance,
Gilles
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2007 05:29 AM
Look at the contentModel.xml. You'll see that the cm:title and cm:description are of type d:mltext. This type of property is inherently multilingual. To edit it in different languages just change the Content Filter Language in the UI. There'll not be anything specific on the UI to allow modifying the values in different languages.
