POST /api/translations/(string:project)/(string:component)/( string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit See also Formatted strings, Qt i18n guide [https://doc.qt.io/qt-5/i18n-source- translation.html#handling-plurals] Ruby format Ruby format string does not match source translated strings weblate.checks format was added. Hint In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct.

POST /api/translations/(string:project)/(string:component)/( string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit See also Formatted strings, Qt i18n guide [https://doc.qt.io/qt-5/i18n-source- translation.html#handling-plurals] Ruby format Ruby format string does not match source translated strings weblate.checks format was added. Hint In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct.

POST /api/translations/(string:project)/(string:component)/(string:languag e)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit See also Formatted strings, Qt i18n guide [https://doc.qt.io/qt-5/i18n-source-translation.html#handling- plurals] Ruby format Ruby format string does not match source translated strings weblate.checks format was added. Hint In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct.

POST /api/translations/(string:project)/(string:component)/( string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit See also Formatted strings, Qt i18n guide [https://doc.qt.io/qt-5/i18n-source- translation.html#handling-plurals] Ruby format Ruby format string does not match source translated strings weblate.checks format was added. Hint In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct.

POST /api/translations/(string:project)/(string:component)/( string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit See also Formatted strings, Qt i18n guide [https://doc.qt.io/qt-5/i18n-source- translation.html#handling-plurals] Ruby format Ruby format string does not match source translated strings weblate.checks format was added. Hint In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct.

POST /api/translations/(string:project)/(string:component)/( string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit See also Formatted strings, Qt i18n guide [https://doc.qt.io/qt-5/i18n-source- translation.html#handling-plurals] Ruby format Ruby format string does not match source translated strings weblate.checks format was added. Hint In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct.

POST /api/translations/(string:project)/(string:component)/( string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit See also Formatted strings, Qt i18n guide [https://doc.qt.io/qt-5/i18n-source- translation.html#handling-plurals] Ruby format Ruby format string does not match source translated strings weblate.checks format was added. Hint In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct.

POST /api/translations/(string:project)/(string:component)/ (string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit format was added. Hint: In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct. status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- work setup, by default json and

POST /api/translations/(string:project)/(string:component)/ (string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit format was added. Hint: In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct. status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- work setup, by default json and

POST /api/translations/(string:project)/(string:component)/ (string:language)/file/ Conflicts handling Defines how to deal with uploaded strings which are already translated. Strings needing edit format was added. Hint: In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct. status codes and parameters here apply to all endpoints as well. Query Parameters • format – Response format (overrides Accept). Possible values depends on REST frame- work setup, by default json and