45 lines
1.9 KiB
Plaintext
45 lines
1.9 KiB
Plaintext
|
|
Source: python-django-translatable-fields
|
||
|
|
Section: python
|
||
|
|
Priority: optional
|
||
|
|
Maintainer: Holger Sielaff <holger@backender.de>
|
||
|
|
Build-Depends: debhelper-compat (= 13),
|
||
|
|
dh-python,
|
||
|
|
python3-all,
|
||
|
|
python3-setuptools,
|
||
|
|
pybuild-plugin-pyproject,
|
||
|
|
python3-django (>= 4.2)
|
||
|
|
Standards-Version: 4.6.0
|
||
|
|
Homepage: https://repo.backender.de/holger/Django-Translatable-Fields
|
||
|
|
Vcs-Git: https://repo.backender.de/holger/Django-Translatable-Fields.git
|
||
|
|
Vcs-Browser: https://repo.backender.de/holger/Django-Translatable-Fields
|
||
|
|
Rules-Requires-Root: no
|
||
|
|
|
||
|
|
Package: python3-django-translatable-fields
|
||
|
|
Architecture: all
|
||
|
|
Depends: ${python3:Depends},
|
||
|
|
${misc:Depends},
|
||
|
|
python3-django (>= 4.2)
|
||
|
|
Recommends: python3-djangorestframework (>= 3.14.0)
|
||
|
|
Description: Django plugin that mimics Odoo's translate=True functionality
|
||
|
|
Django Translatable Fields provides automatic language-aware field handling
|
||
|
|
with a beautiful admin interface integration, similar to Odoo's translate=True
|
||
|
|
functionality.
|
||
|
|
.
|
||
|
|
Key features:
|
||
|
|
* Language-Aware Fields: Automatic translation handling based on Django's
|
||
|
|
current language
|
||
|
|
* Rich Admin Interface: Modal overlay with WYSIWYG editor for easy
|
||
|
|
translation management
|
||
|
|
* JSON Storage: Efficient storage of translations in a single database column
|
||
|
|
* Easy Integration: Drop-in replacement for Django's standard fields
|
||
|
|
* Draggable & Resizable: Modern modal interface with drag and resize
|
||
|
|
capabilities
|
||
|
|
* DRF Support: Built-in Django REST Framework serializers for API development
|
||
|
|
* Field Validation: Proper validation for Email, URL, and Slug fields per
|
||
|
|
language
|
||
|
|
* Type Safety: Full support for Django's field types with translation
|
||
|
|
capabilities
|
||
|
|
.
|
||
|
|
The plugin supports CharField, TextField, EmailField, URLField, and SlugField
|
||
|
|
with automatic JSON-based translation storage and language-aware access
|
||
|
|
patterns.
|