Re: [sugar] Printing et al.

2008-01-04 Thread Benjamin M. Schwartz
On Fri, 2008-01-04 at 13:40 -0500, Jim Gettys wrote: Sample 1: OLPC Trial School in Arahuay, Peru: Needs printing: but not for the kids (too expensive) for any routine printing. The teachers need to be able to use an XO for preparing tests and handouts for the kids, as conventional

[sugar] internationalization problem

2008-01-04 Thread Erik Blankinship
Trying to run Record in Spanish is causing a problem. I will outline the steps which create this problem. Hopefully someone can clarify where the bug is. In Constants.py, we define the following string: #TRANS: photo by photographer, e.g., Photo by Mary istrBy = _(%(1)s by %(2)s) Which was

Re: [sugar] internationalization problem

2008-01-04 Thread Walter Bender
the problem is that your asking the translator to not just translate strings, but also your python code. that won't work. -walter On Jan 4, 2008 4:45 PM, Erik Blankinship [EMAIL PROTECTED] wrote: Trying to run Record in Spanish is causing a problem. I will outline the steps which create this

Re: [sugar] internationalization problem

2008-01-04 Thread Erik Blankinship
Sometimes translators have to include variables in their translations. Most po files have their source strings set up using just %s as the variable name. test = hi there %s test % 'erik' 'hi there erik' However, the order of those variables might be different in different languages. That is

Re: [sugar] internationalization problem

2008-01-04 Thread Erik Blankinship
I have found the bug. I thought I was working with a Spanish laptop, but I now see it is a Brazilian laptop. The Spanish translator included the ss and the Brazilian translator did not. It all looked like Latin based languages to me, and therefore I could not tell the difference :-) I will go

Re: [sugar] API Change Notification: Moving Rainbow's Spool - #5033

2008-01-04 Thread Michael Stone
Dear Everyone, This is your notification that I am about to commit the previously mentioned changes to sugar-datastore, rainbow, and olpc-utils. The current plan is that rainbow's spool will move into /home/olpc/isolation/1/ This way, fewer package changes are required (we can leave olpcrd