#772 closed enhancement (fixed)
included translations sequences
| Reported by: | Owned by: | hugo | |
|---|---|---|---|
| Component: | Internationalization | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi there.
I put into django/contrib/comments/templatetags$comments.py in part FREE_COMMENT_FORM sequence for translations.
it's work, but I don't know is it a good idea. File is attachment .
Thank you for your work.
Regards
Vlado
Attachments (1)
Change History (4)
by , 20 years ago
| Attachment: | comments.py added |
|---|
comment:1 by , 20 years ago
comment:2 by , 20 years ago
| Status: | new → assigned |
|---|
comment:3 by , 20 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
they are translated in new_admin now, but please wait with translations until I give the "go" in the djanog-i18n list.
Note:
See TracTickets
for help on using tickets.
Comments aren't actually translated yet and I would like to bundle all translation hooks to only have one "big hit" on either trunk or new_admin. So comments and other parts will be translated (I already started on doing more translation hooks in new_admin and think I will go on with that over the next days), but it will just take time. No need to send patches, it's not a complicated job and can be better done by one person adding stuff and committing it. I'll close this ticket when new hooks are in new_admin for translation.