Translation support?

[stramel]

I am having a hard time of figuring out how one would be able to use something like Angular Translate to translate titles, placeholders, validationMessages etc. I've thought about overriding all the templates but that would be a pain to upkeep. I have tried using a function to translate the fields needed before it hits the HTML form, but the data isn't always there by that point. I have also tried waiting until the data is in place, but the form has already been rendered at that point.

Any thoughts and/or suggestions would be greatly appreciated!

[davidlgj]

We use gettext via Jed, http://slexaxton.github.io/Jed/, mostly because we
already have an existing gettext infrastructure.
But basically if you can translate a string via a function then that is the
same :-)

So we solve it by setting description, title etc in the form definition to
the actually translated value or in some cases let the backend generate a
schema with titles and descriptions in the appropriate language. And of
course a global validationMessages with all the standard errors , and
sometimes override them in the form definition.

The translation all happens before we put schema and form on the scope.
So it all happens before schema form is even in the picture. Another way of
doing it would be to use a recursive postProcess function and translate
every title, description, placeholder and validation you can find in the
final form structure before the form is rendered.

Does that help?

Wed Jan 14 2015 at 17:37:59 skrev Michael Stramel <notifications@github.com

:

I am having a hard time of figuring out how one would be able to use
something like Angular Translate http://angular-translate.github.io/ to
translate titles, placeholders, validationMessages etc. I've thought about
overriding all the templates but that would be a pain to upkeep. I have
tried using a function to translate the fields needed before it hits the
HTML form, but the data isn't always there by that point. I have also tried
waiting until the data is in place, but the form has already been rendered
at that point.

Any thoughts and/or suggestions would be greatly appreciated!

—
Reply to this email directly or view it on GitHub
#213.

[stramel]

@davidlgj @Dervisevic I have been trying to do the postProcess function that translates every title but since the data is coming from the server asynchronously. The data isn't necessarily there at the time.

I was wondering if it would make sense to add a | translate/ translate directive to all existing templates. Then during initialization check if the translate filter/directive is defined, if not define them as pass through functions? This would allow users to take advantage of their defined translate functionality and the other users wouldn't have to worry about it.

Also, I had seen gettext, but not Jed, thanks for sharing!

[davidlgj]

Adding an empty directive and filter is a possible solution. But it will
need a service as well for those times when you need to translate a sting
in a add-on.

I guess we could do that but what I really don't get is why you just don't
wait for the translations to be loaded before you add schema and form to
scope?

That way you can translate schema and form definition beforehand or safely
do it in a postProcess

Thu Jan 15 2015 at 15:13:16 skrev Michael Stramel <notifications@github.com

:

@davidlgj https://github.com/davidlgj @Dervisevic

https://github.com/Dervisevic I have been trying to do the postProcess
function that translates every title but since the data is coming from the
server asynchronously. The data isn't necessarily there at the time.

I was wondering if it would make sense to add a | translate/ translate
directive to all existing templates. Then during initialization check if
the translate filter/directive is defined, if not define them as pass
through functions? This would allow users to take advantage of their
defined translate functionality and the other users wouldn't have to worry
about it.

Also, I had seen gettext, but not Jed, thanks for sharing!

—
Reply to this email directly or view it on GitHub
#213 (comment)
.

[stramel]

@davidlgj That works for me! It isn't the prettiest but it will do, thanks!

[lucasgranberg]

This is what I did and it seems to work.

        angular.forEach($scope.schemaDef.properties,function(property,key){
            $translate(property.title).then(function(translation){
                $scope.schemaDef.properties[key].title=translation;
            })
        });

edit:
This is a better way

        $scope.schemaDef = {
            type: 'object',
            properties: {
                title: {
                    type: 'string',
                    title: $translate.instant('views.article.edit.title')
                },
        };

[EnobaDevelopers]

How can i do it if my schema comes directly from a json file?

[HeidemannMarkus]

+1

[shravanmahankali]

Has anyone got this working better?

[shravanmahankali]

angular-translate (https://angular-translate.github.io/docs) seems to work very well for me as well! thanks for the pointers.