Did you also change the language node?

<language name="Dutch"
id="nl">

Given that nl is the correct culture to use for Dutch

Yes I did

Where is your language file located? Does other translations in that file work?

The english version is working. My file is exactly in the same folder as the english one created by default ('modules\_protected\EPiServer.Forms\EmbeddedLangFiles') and the name of the file is EPiServer.Forms_NL.xml

<p>And if you add another translation into your Dutch file and wants to use it, for example in a view. Does it work?</p>

By the way, I recommend that you keep your changes outside the modules folder for Forms. Can you move your Dutch file to the same folder as your project's other translation XML files?

Ok I will do that. Thanks for your answers.

I removed EPiServer.Forms_NL.xml and I added the translations to my resource file and now is working fine. Thanks a lot

Great that it was solved, don't forget to mark this thread that you found a solution :)

Basically, if you have XML file for language translation,  you will put them into the folder where Episerver is told to read them. In case of AlloyMVC, it is \wwwroot\Resources\LanguageFiles

You can also embbed into your DLL, so you don't have to put XML into the above folder.

Default (English) language translation of Forms is embbed in the EPiServer.Forms.dll file.

The XML file you see in wwwroot\modules\_protected\EPiServer.Forms\EmbeddedLangFiles is just a sample (and helper) for you, if you want to translate into another language. It is not the actual language translation Forms use for its UI.

So, if you want , you clone our Forms.En.XML to Forms.NL.XML, translate it, change the id="nl", put it in the  \wwwroot\Resources\LanguageFiles

Good news: Forms will be translated into 12 languages by default (in next release, v2.2). So if you are not hurry, just wait for 1 month.

There are still a few keys not present in that language XML, or some values are hard coded.

Also, setting fallbackCulture to anything other than "en" breaks edit mode when using EPiServer Forms.

Hi @Stephan, please give me the info, which version you use, which values is hardcoded, I will file the bug to fix it.

I will recheck the fallbackCulture.  Are you mention about this config in episerver.framework.config? http://world.episerver.com/documentation/Items/Developers-Guide/Episerver-Framework/7/Configuration/Configuring-episerverframework-Section/

I cannot reproduce it when I switch to sv or fr as fallbackCulture.

Yes, that's the config. I should have been more specific, but changing it to something other than "en", and not running CMS in English, causes server errors that break javascript functionality. In my case, changing fallbackCulture to "sv", and setting globalization configuration to use culture "sv-SE" and uiCulture to "sv", causes it.

The texts "Basic Elements" and "Action Elements" doesn't have any corresponding keys in the XML file, so they are still in English after i have translated the XML.

Thank you, I will put your info to the bug. fallbackCulture . AFORM-620

"Basic Elements" and "Action Elements" is (ContentTypeAttribute) group name of the ElementBlock. Hmm, with "space charactor" inside. Bug. AFORM-619

<p>Whats the status of this? The bug&nbsp;<span>AFORM-620 is closed and links to an internal jira bug.</span></p>

We found out that the root cause is not in Forms, so AFORM-620 does not solve the root problem (fallback to the non-tranlated language).

This will be fixed in CMS, Bug CMS-3455 Exception loading localization resource when setting fallbackCulture to "sv"

F̶o̶r̶ ̶w̶o̶r̶k̶ ̶a̶r̶o̶u̶n̶d̶ ̶w̶i̶t̶h̶ ̶F̶o̶r̶m̶s̶,̶ ̶p̶l̶e̶a̶s̶e̶ ̶u̶s̶e̶ ̶F̶o̶r̶m̶s̶ ̶2̶.̶1̶,̶ ̶u̶s̶e̶ ̶t̶h̶e̶ ̶S̶v̶.̶x̶m̶l̶ ̶(̶f̶o̶u̶n̶d̶ ̶i̶n̶ ̶\̶w̶w̶w̶r̶o̶o̶t̶\̶m̶o̶d̶u̶l̶e̶s̶_̶p̶r̶o̶t̶e̶c̶t̶e̶d̶\̶E̶P̶i̶S̶e̶r̶v̶e̶r̶.̶F̶o̶r̶m̶s̶\̶E̶m̶b̶e̶d̶d̶e̶d̶L̶a̶n̶g̶F̶i̶l̶e̶s̶)̶,̶ ̶p̶u̶t̶ ̶i̶n̶ ̶y̶o̶u̶r̶ ̶l̶a̶n̶g̶u̶a̶g̶e̶ ̶f̶o̶l̶d̶e̶r̶ ̶(̶w̶i̶t̶h̶ ̶A̶l̶l̶o̶y̶M̶V̶C̶,̶ ̶i̶t̶ ̶i̶s̶ ̶~̶/̶R̶e̶s̶o̶u̶r̶c̶e̶s̶/̶L̶a̶n̶g̶u̶a̶g̶e̶F̶i̶l̶e̶s̶)̶

The text in that Sv.xml file is in English...

My current installed version of EPiServer.Forms is 2.1.0.2. If I copy the file  \wwwroot\modules_protected\EPiServer.Forms\EmbeddedLangFiles\EPiServer.Forms_SV.xml to my language folder the error occurs, if fallbackculture in web.config is "sv".

Yes Stephan, the sv.xml file is in English. Next month, Forms will be translated to several language.
It is just a work around I suggest at the moment.

This might be the wrong thread to ask in if the bug is in CMS but, what is the status of CMS-3455 ? This currently stops us from updating EPiServer.Forms since it breaks edit mode (not missing translations but exceptions).

<p>@peter If you set fallbackCulture to "en", things will work, but default to english, if a swedish translation is missing.</p>

<p>@<a href="/System/Users-and-profiles/Community-Profile-Card/?userid=794e9dc0-fe10-e511-9afb-0050568d2da8">Peter Emilsson</a>:</p> <p>&nbsp;<a href="https://jira.ep.se/browse/CMS-3455" data-issue-key="CMS-3455">CMS-3455</a>&nbsp;is still in Backlog.</p> <p></p> <p>If</p> <ul> <li>It this is blocking you</li> <li>and you can't wait</li> <li>if you don't mind with some undocumented breaking change</li> </ul> <p>please file a SupportCase, quote my name and this thread into the content. I can introduce a hotfix.</p> <p></p>

@Peter Emilsson:

@THACH Lockevn:

Whats the status of CMS-3455? Just asking since I cant find it in the public bug list.

/Peter

CMS-3455 is resolved, will be in EPiServer.CMS.UI 9.7.0