i18n

Can you provide a little bit more information? Did you translate the error message using the translate interface?

Source language Dutch or English?

Any chance I can get access to the site?

This module just calls Drupal.t() from inside javascript, so it should work the same as t() on the server side. But i never tried it with changing the default language.

Also, we put all our error messages through a theme function that looks like this:

function theme_clientside_error($variables) {
  return t($variables['message'], $variables['placeholders']);
}

So they really should be translated/translatable...

Parts are translated, see screenshot. So triple check the translation interface

Default string for required is "'!title field is required.'", but is seems you're using something like "The field !title field is required." so search for all string containing "required", I assume you didn't translate at least one.

Did you define a prefix at admin/config/validation/clientside_validation - Field name prefix?

I created a webform at http://atix.be/ZkY and it seems ok to me, I translated the following strings:

@Michiel I assume it was the prefix?

#17 you're right "!title field is required." isn't at l.d.o., but "!name field is required." is.

The reason is that we added a theme wrapper function around the error messages (#6) so people can easily alter the message before it is translated.

I'll see how we can upload the regular messages to l.d.o.

We need to add all strings to clientside_validation.api.php, so they get detected by l.d.o.

Fixed in latest dev. Leaving this open for now so we can see if l.d.o updates correctly.

#22 that should be fixed whenever l.d.o. scans again, I assume they should be back somewhere tomorrow.

Just talked to Gabor on IRC, we need to create a new release before the strings are detected.

It appears that clientside_validation.api.php is not picked up, @Jelle_S is going to fix it

I moved the translations to clientside_validation.strings.php.

Fixed in 7.x-1.36