presenter icon indicating copy to clipboard operation
presenter copied to clipboard

Incomplete / partial translation source with fallback translations

Open bhajneet opened this issue 5 years ago • 2 comments

If a translation source is marked "incomplete" for it's given source material (e.g. a translation steek on Jap Ji Sahib only), then we should ask the user to denote a fallback translation.

Can start with a BoS translation which only converts translation lines of Sri Guru Granth Sahib where it says "Lord" to "Vaheguru" as an example partial translation.

This is required for multiple translation sources in our backlog.

bhajneet avatar Feb 03 '20 21:02 bhajneet

Should the translation source specify the fallback translation source, or should the user? Because, in the BoS case, they'd only replace a few words etc, but if you use a fallback translation that's drastically different, it may be a very jarring experience

Harjot1Singh avatar Feb 04 '20 16:02 Harjot1Singh

For ease of use to the consumer it can be hardcoded by the translation source. For more flexibility the user can choose.

I suppose if we consider these as "derivations" and not as "incomplete" works then hardcode makes sense. But in the case of partial translations which are not meant (or not capable) to be completed by anything else, then user choice makes more sense.

I think I'd prefer user choice with a popular default setting. Pretty sure everyone mostly uses the SSKJ translation. It may help if there is a "suggested" fallback source which can be changed and if no suggested fallback source then use the most popular fallback source?

bhajneet avatar Feb 05 '20 22:02 bhajneet