This is based on our experience, but that can not cover all use cases, so always consider your environment when doing the choice. Platform Recommended format Android Android string resources iOS Apple files, so please double check that your files will not get corrupted before using Weblate in a production setup. Following things are known to be broken: Addition of new strings to a translation, every configure 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.haxx.se/docs/]) or by enforcing

configure 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 insert them into the DATA_DIR directory. Accept the certificate by using svn once with the $HOME environment variable set to the DATA_DIR: # Use DATA_DIR as configured in Weblate settings.py, it is /app/data ~/.config/weblate (see Configuration files for other locations), please create it to match your environment: [weblate] url = https://hosted.weblate.org/api/ [keys] https://hosted.weblate.org/api/ = APIKEY

configure 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 insert them into the DATA_DIR directory. Accept the certificate by using svn once with the $HOME environment variable set to the DATA_DIR: # Use DATA_DIR as configured in Weblate settings.py, it is /app/data ~/.config/weblate (see Configuration files for other locations), please create it to match your environment: [weblate] url = https://hosted.weblate.org/api/ [keys] https://hosted.weblate.org/api/ = APIKEY

configure 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 insert them into the DATA_DIR directory. Accept the certificate by using svn once with the $HOME environment variable set to the DATA_DIR: # Use DATA_DIR as configured in Weblate settings.py, it is /app/data ~/.config/weblate (see Configuration files for other locations), please create it to match your environment: [weblate] url = https://hosted.weblate.org/api/ [keys] https://hosted.weblate.org/api/ = APIKEY

This is based on our experience, but that can not cover all use cases, so always consider your environment when doing the choice. Platform Recommended format Android Android string resources iOS Apple files, so please double check that your files will not get corrupted before using Weblate in a production setup. Following things are known to be broken: Addition of new strings to a translation, every configure 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.haxx.se/docs/)) or by enforcing

This is based on our experience, but that can not cover all use cases, so always consider your environment when doing the choice. Platform Recommended format Android Android string resources iOS Apple files, so please double check that your files will not get corrupted before using Weblate in a production setup. Following things are known to be broken: Addition of new strings to a translation, every configure 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.haxx.se/docs/)) or by enforcing

configure 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 insert them into the DATA_DIR directory. Accept the certificate by using svn once with the $HOME environment variable set to the DATA_DIR: # Use DATA_DIR as configured in Weblate settings.py, it is /app/data ~/.config/weblate (see Configuration files for other locations), please create it to match your environment: [weblate] url = https://hosted.weblate.org/api/ [keys] https://hosted.weblate.org/api/ = APIKEY

configure 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 insert them into the DATA_DIR directory. Accept the certificate by using svn once with the $HOME environment variable set to the DATA_DIR: # Use DATA_DIR as configured in Weblate settings.py, it is /app/data ~/.config/weblate (see Configuration files for other locations), please create it to match your environment: [weblate] url = https://hosted.weblate.org/api/ [keys] https://hosted.weblate.org/api/ = APIKEY

This is based on our experience, but that can not cover all use cases, so always consider your environment when doing the choice. Platform Recommended format Android Android string resources iOS Apple files, so please double check that your files will not get corrupted before using Weblate in a production setup. Following things are known to be broken: Addition of new strings to a translation, every configure 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.haxx.se/docs/)) or by enforcing

This is based on our experience, but that can not cover all use cases, so always consider your environment when doing the choice. Platform Recommended format Android Android string resources iOS Apple files, so please double check that your files will not get corrupted before using Weblate in a production setup. Following things are known to be broken: Addition of new strings to a translation, every configure 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.haxx.se/docs/)) or by enforcing