/me notes this already works

http://commons.wikimedia.org/w/api.php?action=parse&text={{:File:Inde_bondo8658a.jpg}}&uselang=fr vs http://commons.wikimedia.org/w/api.php?action=parse&text={{:File:Inde_bondo8658a.jpg}}&uselang=en

and

http://commons.wikimedia.org/w/api.php?action=parse&page=File:Inde_bondo8658a.jpg&uselang=en

vs

http://commons.wikimedia.org/w/api.php?action=parse&page=File:Inde_bondo8658a.jpg&uselang=fr

(given that its not documented to work as such, i have no idea if that is a "feature" or a "bug").

(In reply to comment #1)

(given that its not documented to work as such, i have no idea if that is a
"feature" or a "bug").

You're right, this works by accident. It should be documented and given a different name for stability (who knows if this'll break when someone moves the uselang processing code to some other place).

Hm. That's what I get for just looking at the documentation (and I even did look at ApiParse.php, but didn't and don't see it there either). Next time I'll just experiment the hell out of it. :-)

Anyway, where's that uselang handling?

Could we keep it without renaming the parameter?

Presumably one of the parameters is passed into the parser or something...

Roan, if you decide how you want to do it, i'll take care of it

I'm fine with keeping the param name on principle. I think uselang is handled by the code that initializes $wgLang (Setup.php or something). The best way to go about this IMO would be to call the parameter uselang and check that $wgLang doesn't just happen to already be in the right language (as long as uselang works the way it currently does. this will always be the case) so we can do $lang = $wgLang; instead of creating our own Language object.

r63428