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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation) or by enforcing it in the VCS configuration, for example:

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation) or by enforcing it in the VCS configuration, for example:

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation) or by enforcing it in the VCS configuration, for example:

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation [https://curl.se/docs/]) or by enforcing it in the VCS

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation [https://curl.se/docs/]) or by enforcing it in the VCS

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation [https://curl.se/docs/]) or by enforcing it in the VCS

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation [https://curl.se/docs/]) or by enforcing it in the VCS

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation) or by enforcing it in the VCS configuration, for example:

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation [https://curl.se/docs/]) or by enforcing it in the VCS

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 the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables, (as described in the cURL documentation) or by enforcing it in the VCS configuration, for example: