If so, why do you need T('UTF8-string') after all? You can just simply
use "raw" utf8 string, such as:
{{= "Bragança"}}
or even:
<body> Bragança </body>
In other words, if you don't need i18n, you don't need to bother T
('...'). Fair enough?
On Jun17, 7:38pm, Francisco Gama <francisco....@gmail.com> wrote:
> That is not a solution. Personal Names have no language as well as
> city names like the one in the example: "Bragança".
> So T() should allow UTF-8.
>
> Massimo, how?
>
> On Jun 17, 7:18 am, Iceberg <iceb...@21cn.com> wrote:
>
>
>
> > On Jun17, 12:16pm, Francisco Gama <francisco....@gmail.com> wrote:
>
> > > ok, this one is solved but there is a situation where things still put
> > > me away.
> > > it's when I use T() in views with strings that contain special
> > > characters like ç, á, à...
>
> > > e.g.: {{=T('A pé em Bragança')}}
> > > This would fail the same way on the special characters.
>
> > > Thank you, best regards
>
> > I did not try that, but I assume that is not the way it supposed to
> > be. As a tradition, most people should do T('An English Message, in
> > ASCII of course'), then translate it into other language. But not the
> > reverse.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
