Re: [Plone-developers] LinguaPlone : permitting users not to select a language before translating

Hi there,
I have only now subscribed to to i18n discussion list. so I might raise things 
that have discussed before.

To my mind the fact that an object can not be language neutral to be translated 
is a fundamental flaw in LinguaPlone.
Of course every object is written in a language but that has nothing to do with 
the fact that it acts as language neutral document.
The correct workflow would:
- create a document which is by default language neutral
- before you translate it you must declare its "native" language
     You the have two choices:
     - keep it as language neutral
     - assign it to be the the translated document of its native language

This needs a field "native language" added to each document.
We did that in several projects and where thus able to provide default documents.

robert

On 28.05.2011 18:44, thomas desvenain wrote:
> On Sat, May 28, 2011 at 5:49 PM, Hanno Schlichting<[email protected]>  wrote:
>> Hi.
>>
>> Please keep discussions of LinguaPlone to the plone-i18n mailing list.
>> LinguaPlone isn't part of core Plone.
>>
>> On Sat, May 28, 2011 at 5:37 PM, thomas desvenain
>> <[email protected]>  wrote:
>>> This constraint has been added :
>>>
>>> "Force the user to select a language before attempting to translate
>>>   neutral content items. One content item can be either neutral or have
>>>   translations, but not a mix of the two."
>>>
>>> I think it is very annoying for users. It is not intuitive to set the
>>> language, and then, translate (and 4 clicks are necessary)
>> The usability of the current approach is definitely not good.
>>
>>> Wouldn't it be better to allow a user to translate a neutral content
>>> into any language, and to change neutral content to language 'from'
>>> which it has been translated ?
>> The problem is, that we cannot know the language from which we
>> translate, as a neutral item doesn't have one. Neither any of the
>> containers the item is in nor the current UI language have to match
>> the actual content language of the neutral item.
>>
>> So we have to force the user to make an explicit choice, then change
>> the original which might move it to a different part of the site
>> hierarchy and finally render the translation form.
> I suggest the language change on neutral content should be done AFTER
> translation form submit,
> and the 'language from' should have been set by default to user language,
> so there wouldn't be, by default, any user action neither magic behaviour.
>
>> Probably some kind of intermediate page rendered in a jquerytools
>> dialog box would make the experience better here. The dialog could
>> contain a language selection choice for the original item, then call
>> setLanguage on it, find the new location for it and redirect to the
>> translation form.
>>
>> Maybe there's a different approach to this.
>>
>> Hanno
>>
>
>


------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1