would be better to fix it in the source string. Multiple unnamed variables New in version 4.1. Summary There are multiple unnamed variables in the string, making it impossible for translators to reorder ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the go-i18n JSON v1 and v2 variants. Please choose correct file format matching your environment. See also: JSON, go-i18n, updating-target-files, Customize JSON output, Cleanup translation files

would be better to fix it in the source string. Multiple unnamed variables New in version 4.1. Summary There are multiple unnamed variables in the string, making it impossible for translators to reorder ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the go-i18n JSON v1 and v2 variants. Please choose correct file format matching your environment. See also: JSON, go-i18n, updating-target-files, Customize JSON output, Cleanup translation files

would be better to fix it in the source string. Multiple unnamed variables New in version 4.1. Summary There are multiple unnamed variables in the string, making it impossible for translators to reorder ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the go-i18n JSON v1 and v2 variants. Please choose correct file format matching your environment. See also: JSON, go-i18n, updating-target-files, Customize JSON output, Cleanup translation files

Check class:: Check identifier:: Flag to ignore:: Multiple unnamed variables New in version 4.1. There are multiple unnamed variables in the string, making it impossible for translators to reorder them ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the go-i18n JSON v1 and v2 variants. Please choose correct file format matching your environment. See also JSON [http://docs.translatehouse.org/projects/translate-toolkit/en/latest/formats/json

Check class:: Check identifier:: Flag to ignore:: Multiple unnamed variables New in version 4.1. There are multiple unnamed variables in the string, making it impossible for translators to reorder them ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the go-i18n JSON v1 and v2 variants. Please choose correct file format matching your environment. See also JSON [http://docs.translatehouse.org/projects/translate-toolkit/en/latest/formats/json

Check class:: Check identifier:: Flag to ignore:: Multiple unnamed variables New in version 4.1. There are multiple unnamed variables in the string, making it impossible for translators to reorder them ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the go-i18n JSON v1 and v2 variants. Please choose correct file format matching your environment. See also JSON [http://docs.translatehouse.org/projects/translate-toolkit/en/latest/formats/json

would be better to fix it in the source string. Multiple unnamed variables New in version 4.1. There are multiple unnamed variables in the string, making it impossible for translators to reorder them ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the i18next JSON v3 and v4 variants. Please choose correct file format matching your environment. The v2 and v1 variants are mostly compatible with v3, with exception of how plurals are handled

would be better to fix it in the source string. Multiple unnamed variables New in version 4.1. There are multiple unnamed variables in the string, making it impossible for translators to reorder them ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the i18next JSON v3 and v4 variants. Please choose correct file format matching your environment. The v2 and v1 variants are mostly compatible with v3, with exception of how plurals are handled

would be better to fix it in the source string. Multiple unnamed variables New in version 4.1. There are multiple unnamed variables in the string, making it impossible for translators to reorder them ignore-unnamed-format There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the go-i18n JSON v1 and v2 variants. Please choose correct file format matching your environment. See also JSON [http://docs.translatehouse.org/projects/translate-toolkit/en/latest/formats/json

would be better to fix it in the source string. Multiple unnamed variables New in version 4.1. There are multiple unnamed variables in the string, making it impossible for translators to reorder them Flag to ignore:: There are multiple unnamed variables in the string, making it impossible for translators to reorder them. Consider using named variables instead to allow translators to reorder them supports the i18next JSON v3 and v4 variants. Please choose correct file format matching your environment. The v2 and v1 variants are mostly compatible with v3, with exception of how plurals are handled