How to internationalize custom validation messages?

[brylie]

We have a multi-language application, and are trying to ensure that all user facing text is translated into supported languages. We are using tap:i18n for internationalization.

How can we internationalize the SimpleSchema custom validation text?

Related

• AutoForm issue #483 discusses i18n in general
• meteor-autoform-i18n issue #3 discusses the need for internationalized custom error messages

[brylie]

When we call TAPi18n.__(...); from within SimpleSchema.messages();, we get the following error:

TypeError: Object [object Object] has no method 'en'

[brylie]

tap:i18n doesn't support at the moment server side translations before startup. (source)

Is there a way to perform the SimpleSchema string translation after startup?

[brylie]

One possible solution is to load the translation strings before other code:

your translation.json files must load before the file where you do a translation ([source](your translation.json files must load before the file where you do a translation))

E.g. putting translation strings in /lib/i18n may work.

[brylie]

In any case, there may be other SimpleSchema users who are facing this problem. So, some sort of documentation may prove helpful.

[levino]

I think i18n should not be performed on the server. The field "autoform" should not be evaluated on the server at all.

[brylie]

@levino what do you suggest?

[levino]

Just ignore the field "autoform" on the server. It does nothing on the server anyhow, right?

[brylie]

OK, we can try that.

[levino]

Btw. the issue is as follows:

With TAPi18n the language is set on the CLIENT. It is usally not set on the server. If no language is set, it defaults to 'en'. If there is only say a German language file 'de' it will produce this error as it is missing an 'en' language file. One can fix the issue by adding an english language file next to the say German. This is also why evluation on the client will pass, but not on the server. Another hack is to set the language to 'de' on the server but that is of course poor because then it is kinda global.

[Sojourneer]

Since users may also change their preferred language, it would be better to evaluate the message when it is actually used rather than when it is declared.
I might take a look at patching the SimpleSchema.messages whenever the language changes.

[mirkogeest]

I've the same problem, I don't know how to translate the error message. I'm using autoform + accounts-t9n + tap:i18n.

With this code:

    passwordConfirmation: {
        type: String,
        custom: function() {
            if (this.value !== this.field('password').value) {
                return T9n.get('useraccounts.passwordMismatch');
            }
        }
    }

I get "Unknown validation error".

If I write this:

    passwordConfirmation: {
        type: String,
        custom: function() {
            if (this.value !== this.field('password').value) {
                return "passwordMismatch";
            }
        }
    }

    ...

UserProfileSchema.messages({
  "passwordMismatch": T9n.get('useraccounts.passwordMismatch')
})

Then I get ">useraccounts.subtitleRegister<", I guess because it is processed on server side. I've tried some other combinations, all without success.

[brylie]

Jep. We have been working to internationalize our entire app, and the custom validation messages are one of the few, if only, places we cannot reach. ☹️