Forums

Hello -

I was wondering what Language Packs are available for ChronoForms. Is there a list of supported languages with links to download them? I'm considering Chronoforms for a new project and need to be able to support Spanish and Chinese. Both typical Chinese would be great, Simplified and Full. Any help on finding this info would be great, I was not able to find a post or page dedicated to listing the language support at this point and links to get the files. A link and some info to this would be great.

Thanks in advance!
Chris

Hi Chris,

There are no language packs available for ChronoForms v4 - there is very little component language shown in the front end and the admin is only in English. There have been a couple of attempts in past years to create a multi-language version but Max has never picked them up for inclusion in future releases.

As far as the form go you can easily create forms with the user visible text in any language, or in multi-language if you need it.

Bob

Hi,

If you can go with v5 instead then v5 interface has full multi language support, assuming that you can translate the language file!

However, if you mean the ability to translate validation messages or fields labels...etc then this is supported in both versions as Bob noted!

Regards,
Max

Thanks for your responses Bob and Max. I'm mostly concerned with frontend language translation for field labels and validate messages. The admin side is not really important. Let me clarify my understanding of your replies, are there language files available (Spanish, Chinese simple and normal) for the front end? Or would I need to create them myself? If the languages are available in language packs already where can I get them? Thanks!

Hi rjrinc,

For this you only need to use the "Multi language" action in v4, it should help you translate any form content, including the validation messages, which can be replaced by adding your own text in the "Title" field in your element settings.

Links:
https://www.chronoengine.com/faqs/54-cfv4/cfv4-validation/2590-how-can-i-change-the-language-used-in-validation-messages.html
https://www.chronoengine.com/faqs/52-cfv4/cfv4-emails/2669-how-can-i-translate-emails.html

Regards,
Max

@Max
Is this still valid for v5? In your 1st link I read

Single language sites
You can set the language using the JS Validation Language option on the JS Validation tab (click the Form Name link in the Forms Manager to see this).

The currently listed languages are:

English (default) Chinese, Danish, Deutsch, Dutch, Farsi, French, Greek, Italian, Japanese, Latvian, Norwegian, Polish, Portuguese, Romanian, Russian, Slovenšcina, Spanish and Turkish.
....

I can't see that listed languages?!
I want to have (at least) the validation messages in german language.

I've looked into the code... do I have to overwrite the file libraries/cegcore/assets/gplugins/gvalidation/gvalidation.js for that? What happens after updates... hmmm

Thanks

Hi Heart,

You have v5, but this is for v4, please check the following FAQ on how to do the same for v5:
http://www.chronoengine.com/faqs/70-cfv5/5230-validation-customization-in-cfv5.html

You will have to enter your "own" messages, there is not yet full translation sets for v5 validation messages.

Regards,
Max

Ok thanks Max... got it.

Adding the title of each fields works perfect (but is more work), so I tried adding a "load javascript" in on load section (below the "HTML (Render Form)". I simply put one line in for testing

GValidation.errors.required = "test required custom message";

That doesn't work. I get "Uncaught ReferenceError: GValidation is not defined index.php?option=com_chronoforms5&view=form&Itemid=442&chronoform=Ankauf_Formular:416
(anonymous function)". And I think I found the reason why...

In your gvalidation.js file (libraries/cegcore/assets/gplugins/gvalidation/gvalidation.js) you have:

var GValidtaion = {...

Is GValidtaion a typo!? This typo is 4-6x more often in this gvalidation.js file present...

Hi Heart,

Exactly, good catch, this typo has been found only recently, it has been fixed here, so you can fix it in your gvalidation file then use the code in the FAQs, the next update is expected very soon and will have this fix and more stuff!

Regards,
Max

[[>> fixed spelling of gvalidation : Bob <<]]