Support for multilanguage sites, Internationalization (I18N)

[vinta9e]

I do use GS 3.0 with I18N v1.7

I did assign the $LANG='pl_PL' within gsconfig.php just to try it. It would force the socialize plugin output to polish and throw a funky handful of warnings right at the beginning of html page output:

Warning: include_once(/admin/lang/pl_PL.php) [function.include-once]: failed to open stream: No such file or directory in /admin/inc/common.php on line 163

Warning: include_once() [function.include]: Failed opening '/admin/lang/pl_PL.php' for inclusion (include_path='.:/:/usr/local/php/pear5') in /admin/inc/common.php on line 163

Warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /admin/inc/basic.php on line 560

My site's pages are in Polish when unspecified (as set in the admin) + most pages translated to english under slug_en.

EDIT: Well I still don't know why or how things go about that but I've decided to just include an iframe [like it!] button instead. I think I will just keep it that way.

But here comes my next thought: Do you think GS+I18N could be modified (custom fields?) for the ability to override the page slug for translated pages? I mean: keeping the _en suffixes for XML file storage is great because it makes it easy for GS to "connect" the two language versions of the same content, organize the backend menu etc.

However, it could be beneficial for SEO to have meaningful URLs in every language.
I am no expert but wouldn't it ease Googlebot crawling too?