. . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.5.6. Feature Categories and Feature Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.5.7. Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.5.9. Working with Feature Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Appendix A: HR Data Model Resource Book Difference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Appendix

. . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.5.6. Feature Categories and Feature Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.5.7. Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.5.9. Working with Feature Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Appendix A: HR Data Model Resource Book Difference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Appendix

. . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.5.6. Feature Categories and Feature Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.5.7. Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.5.9. Working with Feature Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Appendix A: HR Data Model Resource Book Difference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Appendix

strings to translate), while some trigger at component level (for example merge errors). These two groups of notifications are visually separated in the settings. You can toggle notifications for watched Platform Recommended format Python GNU gettext PHP GNU gettext [1] C/C++ GNU gettext C# .XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF [2] The proper review workflow is supported since Weblate 2.18. With dedicated reviewers you have two groups of users, one able to submit translations, and one able to review them to ensure translations are

strings to translate), while some trigger at component level (for example merge errors). These two groups of notifications are visually separated in the settings. You can toggle notifications for watched Platform Recommended format Python GNU gettext PHP GNU gettext [1] C/C++ GNU gettext C# .XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF [2] The proper review workflow is supported since Weblate 2.18. With dedicated reviewers you have two groups of users, one able to submit translations, and one able to review them to ensure translations are

strings to translate), while some trigger at component level (for example merge errors). These two groups of notifications are visually separated in the settings. You can toggle notifications for watched Platform Recommended format Python GNU gettext PHP GNU gettext [1] C/C++ GNU gettext C# .XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF [2] The proper review workflow is supported since Weblate 2.18. With dedicated reviewers you have two groups of users, one able to submit translations, and one able to review them to ensure translations are

strings to translate), while some trigger at component level (for example merge errors). These two groups of notifications are visually separated in the settings. You can toggle notifications for watched Platform Recommended format Python GNU gettext PHP GNU gettext [1] C/C++ GNU gettext C# .XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF [2] The proper review workflow is supported since Weblate 2.18. With dedicated reviewers you have two groups of users, one able to submit translations, and one able to review them to ensure translations are

strings to translate), while some trigger at component level (for example merge errors). These two groups of notifications are visually separated in the settings. You can toggle notifications for watched Platform Recommended format Python GNU gettext PHP GNU gettext [1] C/C++ GNU gettext C# .XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF [2] The proper review workflow is supported since Weblate 2.18. With dedicated reviewers you have two groups of users, one able to submit translations, and one able to review them to ensure translations are

strings to translate), while some trigger at component level (for example merge errors). These two groups of notifications are visually separated in the settings. You can toggle notifications for watched TermBase eXchange Translation Memory eXchange gettext MO CSV Excel Open XML JSON Android String Resource iOS strings Uploading translations When you have made your changes, use Upload translation in The proper review workflow is supported since Weblate 2.18. With dedicated reviewers you have two groups of users, one able to submit translations, and one able to review them to ensure translations are

strings to translate), while some trigger at component level (for example merge errors). These two groups of notifications are visually separated in the settings. You can toggle notifications for watched Platform Recommended format Python GNU gettext PHP GNU gettext [1] C/C++ GNU gettext C# .XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF [2] The proper review workflow is supported since Weblate 2.18. With dedicated reviewers you have two groups of users, one able to submit translations, and one able to review them to ensure translations are