Hello,
I'm in the process of translating XAF into french.
There are nearly 10 000 texts to translate.
Sometimes the French value is the same as the English one (Visible for example is the same word in English and in French).
Sometimes the value should not be translated. Very often the ObjectCaptionFormat property is defined as {0:Name} and this value should stay like this (in most cases).
What comes in mind here is just to let the translated value as is, so it's not translated.
The problem arrives when you open the translator. You select the filter Unstranslated and boom, you get 2000 untranslated values. In fact 1800 of these are values that should not be translated.
So what I'm asking is a way to copy the default language value in the translated value. Just select a few lines, press a key and you're done.
This will have 2 benefits :
1/ For the problem I described above.
2/ When the translated value is close to the default one. You copy the default value and make just small modifications.
Many thanks for listening … hope to get this into 11.2 as it's very easy to do and it will greatly enhance the translaters experience
Julien
Localization - Make it possible to copy the default language value into the translated value
Answers approved by DevExpress Support
We have implemented the functionality described in this ticket. It will be included in our next update(s).
Please check back and leave a comment to this response to let us know whether or not this solution addresses your concerns.
Starting with version 13.1, you can use the new "Mark As Translated" command or the Control+T shortcut for selected records in the Localization Tool. Please refer to the following video for more details: http://screencast.com/t/gh0NrHMfk
Thanks,
Dennis
- v13.1.4Download Official Update
Hello Julien,
Thank you for your suggestion. From my point of view, it makes sense. We will discuss it with our developers.
Thanks,
Anatol
Hi Anatol,
are there any news? I think it would be quite important for us because our translators do still have the problem described above.
Thank you for your feedback
Christian
@Julien, Christian:
We are having difficulties understanding your original requirements and need your help with the following:
>>
The problem arrives when you open the translator. You select the filter Unstranslated and boom, you get 2000 untranslated values. In fact 1800 of these are values that should not be translated.
So what I'm asking is a way to copy the default language value in the translated value. Just select a few lines, press a key and you're done.
<<
By default the "Translated Value" column will contain the same values as the "Default Language Value" one. So, it is not quite clear what you want to copy, why and where. Please refer to the attached screenshot and describe your current difficult and needs in greater detail. Thanks in advance.
Hello Dennis,
sometimes the german translation is equal to the english one. For example the word "Name". Because the german translation is equal to the english default our translators do not need to/cannot translate those words. The problem is, that the translation tool cannot distinguish between words that aren't modified but already translated correctly an word that really must be translated.
In your screenshot it would be nice to check the isTranslated column. At the moment a word is only checked as translated, if the spelling is diffent to the default language.
I hope you do understand the problem. Please feel free to ask any further questions
Best regards
Christian
Please do also have a look at http://www.devexpress.com/Support/Center/Question/Details/Q394260
Am I correct that if you had a way to set the IsTranslated column value via an Action, mouse click or keystroke, you would be happy?
Hi Dennis,
that would help. It must be possible to flag an entry as translated, that has the same spelling in german as in the defaultLanguage. At the moment it is possible to force an entry in the german xafml (add an empty space leave the cell, save and close the tool, restart the tool and remove the empty space). After that it's put in the german model, but it's not marked as translated.
We think that the following code is responsible for the wrong value of the translated flag:
Have a look at Class LocalizationItemBind:
public bool IsTranslated{
get {
if(isTranslated == null) {
isTranslated = DefaultLanguageValue != TranslatedValue;
}
return isTranslated.Value;
}
}
It should be possible that this property returns true with the same value in defaultLanguage as in the translated language.
To be able to flag the property as translated with a check in the translation-tool would be a nice additional feature.
Thank you for your help
Christian
Thank you for the confirmation, Christian. We will see to improving this situation.
Thank you for listening Dennis. I stopped translating because it became too time consuming as I have to check again all the !IsTranslated texts every time.
For sure you will get the French version up to date much more often if this is implemented.
And be able to check the IsTranslated column would be a perfect way to accomplis this.
Thanks for the update, Julien. We are on it already. Please bear with us.
Good news !!!