On Wed, Apr 8, 2009 at 8:54 PM, Tim Langeman <[email protected]> wrote:
> The implication of this is that different amounts of content from a
> single template would be translated, depending up the "level" of
> translation desired.
I think that, basically, most people want only one level at any given
time. For example, if I want only navigation to be translated, I would
only add {% trans %} that, and leave anything else alone. Even if I go
about tagging all strings for translation, I could still just not
translate all generated strings. In most cases I translate
*everything*, including content. So tagging tags as basic, medium,
complete, or whatnot is not very nice. Of course, some people might
want more than 5 or 6 or 20 levels, some might want only 3. And so on.
If you really want all that, perhaps you should attack it more
semantically. Like tagging something as navigation, rather than
'basic'. And then simply generate all strings, but group them as
navigation, etc. That would also be helpful when the translator
doesn't know the exact context of the string.
Best,
--
Branko
eml: [email protected]
alt: [email protected]
blg1: http://sudologic.blogspot.com/
blg2: http://foxbunny.blogspot.com/
blg3: http://brankovukelic.blogspot.com/
img: http://picasaweb.google.com/bg.branko
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django I18N" 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-I18N?hl=en
-~----------~----~----~----~------~----~------~--~---
