Localization FAQs

No. Contentstack does not give its users the provision to manually enter content from right to left. However, users can paste Arabic and Hebrew content copied from any source file into the text fields within Contentstack. Learn how localization works.

No, Contentstack does not provide any translation service.

The default language of a stack is known as the master language of a stack. Once it is set while creating a stack, it cannot be changed. Read more about master language.

No. You need to perform the following steps to localize an entry. 

1. Select the language using the language selector option, say French - France.
2. The entry page for ‘French - France’ shows an Unlocalized, unpublished copy of the main entry in Master language.
3. Now, make changes in this entry in order to localize it in ‘French - France’, and click on Save or Publish.

This will create a new copy of the same entry. This new copy will then cease to fetch data from the main entry in master language, and the entry will be considered as localized in ‘French - France’.

Yes, you can retrieve content from the fallback language version of an entry or asset if the current localized version hasn’t been published. Pass the include_fallback=true query parameter to fetch the published version from the fallback language. Learn more about how the fallback logic works while retrieving published content.

You can also refer to our Content Delivery API documentation on entries and assets to understand how you can fetch fallback content for published entries.

If the fallback language for the specified locale is the master language itself, then the include_fallback:true query parameter is rendered inapplicable.