Jump to content
M.N

Adding translations to EmailsBody.lang.xlf results error 500 for generating emails

Recommended Posts

As a lot of needed email translations are missing in EmailsBody translation files (in folders .../app/Resources/translations/...) then I decided to add these for generating correctly translated emails. Process:  generate emails at default state, list missing terms in notepad, open en-en translation file. locate listed terms, open other language translation files, search for terms, if not located search for en-en file file reference, look for file reference in other language file, if term translation is missing, copy it with the key from en-en file to target file, translate the texts, save changed file.

Cache cleared. At generating emails to core or classic theme error 500 happens. Checked file for tag pairs, all correct. Checked for repeated keys - none found.

What is wrong with the file with added translations or how to use it for generating correctly translated emails?

Sample of EmailsBody.fi-FI.xlf attached.

EmailsBody.fi-FI.xlf

Share this post


Link to post
Share on other sites

By debug there is following error message:

An exception has been thrown during the rendering of a template ("Invalid resource provided: "1.2"; Errors: [ERROR 1871] Element '{urn:oasis:names:tc:xliff:document:1.2}trans-unit': This element is not expected. Expected is ( ##other{urn:oasis:names:tc:xliff:document:1.2}* ). (in ... - line 948, column 0)").

How to resolve?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More