Translation templates dashed-slug.net › Forums › General discussion › Translation templates Tagged: i18n, l10n, language, language domain, pot This topic contains 1 reply, has 2 voices, and was last updated by alexg 7 months ago. Viewing 2 posts - 1 through 2 (of 2 total) Author Posts February 21, 2019 at 2:11 am #5884 vorticismParticipant There are two translation templates per plugin. E.g wallets-exchange, wallets-exchange-front. Is there an advantage to doing this? I’ve translated both files, but only one translation file is recognized, and the other does not work. February 21, 2019 at 10:37 am #5886 alexgKeymaster Most of the extensions have these two language domains. The reason is that most users will not care to translate the strings that appear in the backend, while the strings that appear in the frontend are the ones that need to be translated more often. Which translation file did you find is not recognized? Author Posts Viewing 2 posts - 1 through 2 (of 2 total) You must be logged in to reply to this topic.