On Mar 22, 11:55 pm, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> On Sun, 2009-03-22 at 21:38 +0000, JohnHandelaarwrote:
> > Hello
>
> > So if my translation string in a template currently looks like this:
>
> > A book called "Gulliver's Travels"
>
> > ...how do I convert that into something starting with "{% trans" ?
>
> You would mark the whole string for translation and, in the course of
> translating it, the translators would replace "..." with «...» or „...“
> or whatever. It's generally ill-advised (and very fragile) to mark only
> a portion of a sentence for translation,
[snip]
> If that doesn't answer your question, could you explain a bit more what
> the problem is?
Specifically I'm looking at something I've inherited which writes out
a tiny snippet of JS which calls i18n/setlang and (ironically) appears
to be resistant to being localised itself. If I were able to use both
single and double quotes in a string I could put those 20 characters
in a translated string and have done with it. But i18n doesn't
support escaping, it seems.
A better way of writing out a different link in a template based on
whether it's in one language or the other (this app uses only two)
would of course also be welcome.
jh
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
