Weblate Manual, Release 4.5 2.1.9 Production setup For a production setup you should carry out adjustments described in the following sections. The most critical settings will trigger a warning, which is Can access billing info (see Billing). 2.6.6 Custom access control To gain more access control adjustments in a project, you can set Access control to Custom to switch over to using the Django admin-interface Allows using this component as a glossary. You can configure how it will be listed using Glossary color. The glossary will be accessible in all projects defined by Share in projects. It is recommended

Weblate Manual, Release 4.5.1 2.1.9 Production setup For a production setup you should carry out adjustments described in the following sections. The most critical settings will trigger a warning, which is Can access billing info (see Billing). 2.6.6 Custom access control To gain more access control adjustments in a project, you can set Access control to Custom to switch over to using the Django admin-interface Allows using this component as a glossary. You can configure how it will be listed using Glossary color. The glossary will be accessible in all projects defined by Share in projects. It is recommended

Configuration, Access control Production setup For a production setup you should carry out adjustments described in the following sections. The most critical settings will trigger a warning, which is Billing Can access billing info (see Billing). Custom access control To gain more access control adjustments in a project, you can set Access control to Custom to switch over to using the Django admin-interface Allows using this component as a glossary. You can configure how it will be listed using Glossary color. The glossary will be accessible in all projects defined by Share in projects. It is recommended

Configuration, Access control Production setup For a production setup you should carry out adjustments described in the following sections. The most critical settings will trigger a warning, which is Billing Can access billing info (see Billing). Custom access control To gain more access control adjustments in a project, you can set Access control to Custom to switch over to using the Django admin-interface Allows using this component as a glossary. You can configure how it will be listed using Glossary color. The glossary will be accessible in all projects defined by Share in projects. It is recommended

id)/ Returns information about a glossary. id (int) – Glossary id name (string) – Language code color (string) – Text direction source_language (object) – Object of language plura information projects see GET /api/projects/(string:project)/ Example JSON data: { "name": "Hello", "id": 1, "color": "silver", "source_language": { "code": "en", "name": "English", "plural": /api/glossary/(int: id)/ Changes the glossary parameters. id (int) – Glossary id name (string) – Language name color (string) – Language direction source_language (object) – Language plural details PATCH /api/glossary/(int:

Parameters • id (int) – Glossary id Response JSON Object • name (string) – Language code • color (string) – Text direction • source_language (object) – Object of language plural information • projects projects; see GET /api/projects/ (string:project)/ Example JSON data: { "name": "Hello", "id": 1, "color": "silver", "source_language": { "code": "en", "name": "English", "plural": { "id": 75, (continues Manual, Release 4.3 • id (int) – Glossary id Request JSON Object • name (string) – Language name • color (string) – Language direction • source_language (object) – Language plural details PATCH /api/glossary/(int:

id)/ Returns information about a glossary. id (int) – Glossary id name (string) – Language code color (string) – Text direction source_language (object) – Object of language plura information projects see GET /api/projects/(string:project)/ Example JSON data: { "name": "Hello", "id": 1, "color": "silver", "source_language": { "code": "en", "name": "English", "plural": /api/glossary/(int: id)/ Changes the glossary parameters. id (int) – Glossary id name (string) – Language name color (string) – Language direction source_language (object) – Language plural details PATCH /api/glossary/(int:

Parameters • id (int) – Glossary id Response JSON Object • name (string) – Language code • color (string) – Text direction • source_language (object) – Object of language plural information • projects projects; see GET /api/projects/ (string:project)/ Example JSON data: { "name": "Hello", "id": 1, "color": "silver", "source_language": { "code": "en", "name": "English", "plural": { "id": 75, "source": Object 114 Chapter 1. User docs The Weblate Manual, Release 4.4 • name (string) – Language name • color (string) – Language direction • source_language (object) – Language plural details PATCH /api/glossary/(int:

Weblate Manual, Release 4.5.3 2.1.9 Production setup For a production setup you should carry out adjustments described in the following sections. The most critical settings will trigger a warning, which is Allows using this component as a glossary. You can configure how it will be listed using Glossary color. The glossary will be accessible in all projects defined by Share in projects. It is recommended Glossary 232 Chapter 2. Administrator docs The Weblate Manual, Release 4.5.3 Glossary color Display color for a glossary used when showing word matches. 2.7.5 Template markup Weblate uses simple

Weblate Manual, Release 4.5.2 2.1.9 Production setup For a production setup you should carry out adjustments described in the following sections. The most critical settings will trigger a warning, which is Allows using this component as a glossary. You can configure how it will be listed using Glossary color. The glossary will be accessible in all projects defined by Share in projects. It is recommended Glossary 232 Chapter 2. Administrator docs The Weblate Manual, Release 4.5.2 Glossary color Display color for a glossary used when showing word matches. 2.7.5 Template markup Weblate uses simple