Implemented the bolt content translations #3378
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature adds the Content-Translation page:
This page allows to export content in the
xlf
format, which is the default format for translation agencies.After translating the files, they can be imported again and will replace localized text with the given file.
If content cannot be found by their id (which happens if content is changed between import and exporting), the controller searches for the original text and adds the translation to the found content field.
This also works with custom fields that are stored as json.
On export the controller even splits json content, so translation agencies do not need to read in between the json overhead:
HTML on the other side is not extracted, which was not a problem for the company that translated our last project (their tool was able to do it on its own).
This was tested on one project so far (without the fallback to the content query, if id's changed).
This has also been successfully tested on all supported databases:
mysql
,sqlite
andpostgresql
.