Is it possible to have a secondary source language?

General Questions
1

I’m maintaining an application that has these languages:

  • Japanese
  • English
  • Others (French, Russian, etc)

I’m a native Japanese speaker, so I’d like to set Japanese as a source language, but 99% of translators cannot read Japanese, so I’d like them to refer English as a secondary source.
Also, I’d like to make Crowdin use English as a fallback, rather than Japanese.
Is it possible?

Let’s say that there’s three strings, A, B, and C.

  • A: Translated into English and French
  • B: Translated into English, but not French
  • C: Not translated

I’d like French to have:

  • A: French
  • B: English
  • C: Japanese

Is it possible?

2

Hi @sevenc_nanashi,

Crowdin projects can only have one source language, so setting Japanese as source and using English as a secondary reference isn’t natively supported in the Editor. However, there are a couple of options depending on your setup:

On our Crowdin Enterprise platform, you can use a Switch Source Language step in the workflow. This allows translating from Japanese to English first, and then from English to other languages like French. This way, translators work with English, not Japanese

To control what’s shown in your product when translations are missing, the Better Fallback app lets you define fallback languages, for example: French → English → Japanese

But the case you describe is impossible to achieve, sorry