<p>Currently, Sprout Forms (v1.1.0) is translatable, but we have not yet added support for Craft's localization feature.</p>

<p>You can find a <a href="https://github.com/BarrelStrength/Sprout-Plugin-Translations" rel="nofollow noreferrer">template of a translation file</a> on our Github Account.</p>

<p>We want to support localization in the long run. The main reason we have not yet is mostly just one of priority. In comparison to other advanced features, we have had very few requests for it (feel free to send us a note and advocate for how this needs to work for you) and development for it isn't documented anywhere (feel free to send Pixel and Tonic a request for documenting it better too!). At the time of this posting, I posted a question here about the topic 7 months ago [February 2015] and the question has received one upvote and 41 views:</p>

<p><a href="https://craftcms.stackexchange.com/questions/7124/how-do-you-add-support-to-manage-content-in-multiple-languages-in-a-plugin-with">How do you add support to manage content in multiple languages in a plugin with a custom Element Type?</a></p>

CC BY-SA 3.0
2016-06-08T07:40:00.993Z
Any updates on this? Have an upcoming project where this would come in handy as well.
peirix
CC BY-SA 3.0
2016-06-08T15:05:15.837Z
Still on the list, and the answer above is still more or less accurate.
Ben Parizek
CC BY-SA 3.0
2015-10-02T15:29:47.747Z
2016-06-08T15:03:11.577Z
2017-04-13T12:50:59.930Z
Ben Parizek
<p>What about <a href="http://buildwithcraft.com/help/static-translations" rel="nofollow">translation files</a>.</p>

CC BY-SA 3.0
2015-10-02T14:02:22.517Z
2015-10-02T14:02:22.517Z
user1070143
<p>Does  the <strong><a href="http://sprout.barrelstrengthdesign.com/craft-plugins/forms/docs" rel="nofollow">Sprout Forms</a></strong> plugin tap into the <a href="http://buildwithcraft.com/docs/localization-guide" rel="nofollow">internationalization feature</a> of Craft Pro, i.e. does it support <strong>adding localized versions of existing forms</strong>, similar to translated section entries?</p>

<p>What I'm looking for is creating forms where <em>all field names and values</em> are identical between language variants, but <em>labels and notifications</em> may differ per locale. (This is opposed to setting up multiple forms that are not tied together and write to separate tables in the back-end.)</p>

<p>In the <a href="http://sprout.barrelstrengthdesign.com/craft-plugins/forms/docs" rel="nofollow">docs</a>, all I can find is a reference to <a href="http://sprout.barrelstrengthdesign.com/craft-plugins/forms/docs/examples/translating-error-messages" rel="nofollow">translated <em>error messages</em></a>, which are the smallest of my concerns. — That same approach might work for the main conent of the form as well, but it could not be managed via the plugin's control panel.</p>

CC BY-SA 3.0
2015-10-02T13:55:38.037Z
For labels I just used global fields and hardcoded the whole form. For those translated notifications I don't think that's possible.
KSPR
<localization><form><plugin-sproutforms>
Sprout Forms: Localized version of form with translated labels?
# Sprout Forms: Localized version of form with translated labels?

(Asked by: username_0 on 2015-10-02)

Does the **[Sprout Forms](http://sprout.barrelstrengthdesign.com/craft-plugins/forms/docs)** plugin tap into the [internationalization feature](http://buildwithcraft.com/docs/localization-guide) of Craft Pro, i.e. does it support **adding localized versions of existing forms**, similar to translated section entries?

What I'm looking for is creating forms where *all field names and values* are identical between language variants, but *labels and notifications* may differ per locale. (This is opposed to setting up multiple forms that are not tied together and write to separate tables in the back-end.)

In the [docs](http://sprout.barrelstrengthdesign.com/craft-plugins/forms/docs), all I can find is a reference to [translated *error messages*](http://sprout.barrelstrengthdesign.com/craft-plugins/forms/docs/examples/translating-error-messages), which are the smallest of my concerns. — That same approach might work for the main conent of the form as well, but it could not be managed via the plugin's control panel.

**Tags:** localization, form, plugin-sproutforms
> **Comments:**
> **username_1**: For labels I just used global fields and hardcoded the whole form. For those translated notifications I don't think that's possible.  

---

## 2 answers

### Answer by username_2 on 2015-10-02. Score: 4

Currently, Sprout Forms (v1.1.0) is translatable, but we have not yet added support for Craft's localization feature.

You can find a [template of a translation file](https://github.com/BarrelStrength/Sprout-Plugin-Translations) on our Github Account.

We want to support localization in the long run. The main reason we have not yet is mostly just one of priority. In comparison to other advanced features, we have had very few requests for it (feel free to send us a note and advocate for how this needs to work for you) and development for it isn't documented anywhere (feel free to send Pixel and Tonic a request for documenting it better too!). At the time of this posting, I posted a question here about the topic 7 months ago [February 2015] and the question has received one upvote and 41 views:

[How do you add support to manage content in multiple languages in a plugin with a custom Element Type?](https://craftcms.stackexchange.com/questions/7124/how-do-you-add-support-to-manage-content-in-multiple-languages-in-a-plugin-with)

> **Comments:**
> **username_3**: Any updates on this? Have an upcoming project where this would come in handy as well.  
> **username_2**: Still on the list, and the answer above is still more or less accurate.  

---

### Answer by username_4 on 2015-10-02. Score: 1

What about [translation files](http://buildwithcraft.com/help/static-translations).


---

