#3804: Filter for translation instead of block
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: hugo
Status: closed | Component:
Internationalization
Version: SVN | Resolution: wontfix
Keywords: | Stage: Design decision
needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
This is only a space-saver in the relatively rare case when you want to
translate a single variable's content. Translation strings should normally
be extracted in blocks of text so that translators have some context to
work with and because translations are not made on a word-by-word basis.
Working on a block basis for internationalising content is the right thing
to do here. I don't see any value in also including this filter.
If you have a more realistic example that requires this that doesn't make
things any harder for translators, please bring it up on the django-
developers list where we can discuss it. We're not going to include it as
"another way to do something", though -- it would have to fix a problem
that isn't already solved.
--
Ticket URL: <http://code.djangoproject.com/ticket/3804#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
