#34493 closed Cleanup/optimization (invalid)
wrong translation
| Reported by: | caesartylor | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 3.2 |
| Severity: | Normal | Keywords: | wrong translation text in Chinese version document |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | yes |
Description
location: https://docs.djangoproject.com/zh-hans/3.2/howto/custom-model-fields/#database-storage
Paragraph III
original text: Different databases provide different sets of valid column types, but the rule is still the same: those are the only types you have to work with.
version: 3.2, zh-hans
modify: 不能 ---> 不同
Change History (3)
comment:1 by , 20 months ago
| Has patch: | unset |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
follow-up: 3 comment:2 by , 20 months ago
Maybe, you don't comprehend the meaing. I want to report wrong translation, the original text should be right. I advise your report this issue to translation team.
comment:3 by , 20 months ago
Replying to caesartylor:
Maybe, you don't comprehend the meaing. I want to report wrong translation, the original text should be right. I advise your report this issue to translation team.
I understood the report :) Again translations are handled at Transifex and not in this tracker, see docs.
Thanks for the report, however, translations are handled at Transifex and not in this tracker.