Pykata in languages other than English

[Andre Roberge]

Hi everyone,

I don't know if this has been raised in the past, but what about having "language subdomains" for Pykata, for languages other than English?   If everything goes according to plans, in about a year I should have a lot more time to devote to teaching related activities and I was thinking about the possibility of translating the examples/exercises in French.

Cheers,

André

[Andrew Harrington]

Internationalization is another worthy level.  Does Django/Web2Py ease that?  If it something that can be added later or is it much less work if it is encorporated immediately?

Andy

--
You received this message because you are subscribed to the Google Groups "PyWhip" group.
To post to this group, send email to pyw...@googlegroups.com.
To unsubscribe from this group, send email to pywhip+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pywhip?hl=en.

--
Andrew N. Harrington
 Director of Academic Programs
 Computer Science Department
 Loyola University Chicago
 512B Lewis Towers (office)
 Snail mail to Lewis Towers 416
 820 North Michigan Avenue
 Chicago, Illinois 60611

http://www.cs.luc.edu/~anh
Phone: 312-915-7982
Fax:    312-915-7998
g...@cs.luc.edu for graduate administration
u...@cs.luc.edu for undergrad administration
aha...@luc.edu as professor

[Abhishek Mishra]

Web2Py does have an easy solution for this - http://web2py.com/book/default/section/4/12

Basically what we are advised by the framework is to wrap around all language related text/strings with a T() Eg. T('School')

T is globally available and can be used at any level of code (views, controllers or model)

Right now I'm not aware of how we actually go about converting the strings.

Abhishek

[David MacQuigg]

It takes a lot of effort to write a problem description that is clear
and concise and avoids subtle ambiguities that will frustrate the
student. An automated translation will likely get it wrong. Automated
translations are better for applications that just need labels and
keywords translated.

If someone is serious about teaching Python in another language, they
should make the effort to translate our problems correctly. This is far
less effort than what went into creating the problems and creating our
website.

> Andr�
>

[Andrew Harrington]

Yes, I would not rely on automatic translation (though a knowledgeable human could start from there if useful).  The asumption is that if people wanted a group of problems in another language, they would translate. That is a lot less work than creating our site.  But the site also has the testing code and the sandbox, and likely links to related problems....   The idea would be to NOT reproduce all that, if we could just allow preferred languages in profiles and language tags for possibly multiple problem descriptions for the same problem. Python 3 is coming, where only the keywords need to be English or even ASCII.  If it is an additional provision that would take little work to retrofit later, then leave it for now - not the highest priority.

Andy

       André

--
You received this message because you are subscribed to the Google Groups "PyWhip" group.
To post to this group, send email to pyw...@googlegroups.com.
To unsubscribe from this group, send email to pywhip+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pywhip?hl=en.

[Andre Roberge]

On Mon, Apr 5, 2010 at 4:04 PM, Andrew Harrington <anharr...@gmail.com> wrote:

Yes, I would not rely on automatic translation (though a knowledgeable human could start from there if useful).  The asumption is that if people wanted a group of problems in another language, they would translate. That is a lot less work than creating our site.  But the site also has the testing code and the sandbox, and likely links to related problems....   The idea would be to NOT reproduce all that, if we could just allow preferred languages in profiles and language tags for possibly multiple problem descriptions for the same problem. Python 3 is coming, where only the keywords need to be English or even ASCII.  If it is an additional provision that would take little work to retrofit later, then leave it for now - not the highest priority.

Andy

Designing UI for translation is fairly easy to do ... and is best done when introduced early on.

I volunteer for translating the UI in French, so that the translation could be tested  (but can not do so right away...).  I expect that only a few strings will required to be translated (Home, All Problems, Contribution Guidelines, Help, About, Sign in .... and perhaps a couple more) with the corresponding pages.

I personally don't think that keywords/tags for problems should be translated.  My preference would be for a language button/link which brings one to the "home page" for that given language, with links only to problems available in that language.

André