[
http://www.jahia.net/jira/browse/JAHIA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35689#action_35689
]
Stephane Croisier commented on JAHIA-3669:
------------------------------------------
... and you are not using the "translation roles" in the admin center. Because
if you are using them, this is just hidding the language flag in the engine
from the language on which you have no "modification" rights. So at the place
of having them in read-only mode, you do not see them at all any more! Quite
hard to translate the description metadata for example.
So yes we definitvely have to think about easing the role of translator. But
for that we will certainly need to have a better fine grained granularity on a
per language basis. This is for example quite strange that a german translator
can notify the page in english but can not see the content within the edition
engine! Typically the worklow is also not appropriate for translators. Usually
you create a text in one language and then you ask for translations which could
be optional. So the publishing process on the main mandatory language is going
faster than for the other languages. And roles in the NStep are not the same
according to the language.
Regarding the automated translation, I think Jay made an integration of a tool
for one US customer by using the XML import/export mechanism. In fact
transalating a whole site using the container engine is a suicide. There are
XML standards for translation purposes. So I think it would be better to
directly support such standards so that a webmaster could simply export its
whole site and give it to a translation agency which is compliant with the XML
standard and then reimport the whole in Jahia.
So Jahia supports multilanguage but it does not support collaborative working
in multilanguage mode for the moment, that's for sure.
> Add come translation management to Jahia
> ----------------------------------------
>
> Key: JAHIA-3669
> URL: http://www.jahia.net/jira/browse/JAHIA-3669
> Project: Jahia Web Content Management Server (WCMS)
> Issue Type: Improvement
> Components: Multilanguage
> Affects Versions: WCM 6.0 (Andromeda)
> Reporter: Benjamin Papez
> Fix For: WCM 6.0 (Andromeda)
>
>
> It would be cool if Jahia would offer more aid to translate content from one
> language to the other.
> Perhaps we could provide a Google translation integration (or alternative
> translation services), where the user could select from which language he
> would like to take the content and let it automatically translate to the
> current, so he would only have to make changes, were the automatic
> translation made mistakes. This could speed up translation.
> Perhaps we should also make it easier to see the text of the original
> language at the same time when translating to the current language. Now a
> user has to open the page in the original language in the browser, perhaps
> click on the container he wants to translate to see the details, open the
> engine popup, click on the language he would like to translate to and then he
> would see the original container language in the main browser, while the
> engine is opened for his new language. Now for the next container, he would
> want to use the navigation buttons in the engine, BUT if he wants to display
> that container in the main browser, the engine popup automatically closes,
> when clicking on a link in the main browser. So the navigation buttons in the
> engine are of limited use for translating jobs. Either we should display the
> text to be translated directly in the engine popup or should provide a button
> to open the original language text in a separate window.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
