sorry for the delay.
.jon, thanks for your comments. Again a great inspiration!!
some ideas:
the ngettext function is a good idea. Difficult is language, see russian for
example.
In basque we say different 0,1 or more.
I suggest:
__plural ( if_0, if_1, if_more, count, domain==current)
example __plural ("no email", "1 email", "%d emails", NUMBER) ..
fallback translation for en_EN cases: when language have two parts, first
search "en_US", and if not found translates using "en" as language (the
actual code must be changed)
before bzr the code..some change must be done in language and url. The
language must be inserted in url in first place:
For example: www.openclipart.org/es/browse. or
www.openclipart.org?q=es/browse. Url class must detect language, check if is
valid (so a site have a list of allowed languages), and then shift language
in url. So, we don't need change all widget and display_urls (1) MUST BE
specified without language. (2)
(1) Christopher called rightly display_url as routes and proposed a elegant
solution for this problem.
(2) if you realy want two different pages in spanish and english, for
welcome, you must use welcome-es and welcome-en...but not
es/welcome or en/welcome.
about f3 markup..i will respond in few minutes
_______________________________________________
Mailing list: https://launchpad.net/~aikiframework-devel
Post to : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework-devel
More help : https://help.launchpad.net/ListHelp
