Why not use the time to learn English first. It will be more useful to her than programming.
Learning a whole language first isn't much fun. Also, lots of people I know (me included) learned programming first, then (through programming) english. I started with GW-BASIC at age of 7 and almost everything was in english: the programs I had, even the manuals. I picked up basic english from this (after some trial and error you understand what certain words or phrases mean; I was pretty surprised when I learned at school that these words are pronounced totally differently than I imagined
I even knew a pretty good programmer who still does not speak english. He couldn't ask for directions if he'd get lost. Yet he manages to do hold up as a professional. Couldn't believe it at first, but it shows that knowing english does help when developing but it's not strictly necessary. The good thing about programming is that the syntax rules are so much more strict and easier to understand than natural language.
In Germany, if the court grants you an injunction it is not automatically enforced immediately. The winning party needs to explicitly enforce it.
Now a US court decided that the company Motorola may not enforce this injunction should it win it, since there are ongoing actions that have not been decided (like, whether the patent in question is actually invalid). So if Motorola were to enforce this injunction it would have an unfair disadvantage.
So the US court has not interfered with German courts: it only ruled what the company Motorola may do should it win this battle in Germany.
From the fine blog post (emphasize mine):
We spent about 20% of our total man-hours last year dealing with Android in one way or another - porting, platform specific bug fixes, customer service, etc.  Meanwhile, Android sales amounted to around 5% of our revenue for the year, and continues to shrink. Needless to say, this ratio is unsustainable.