They also, and finally, told that the translation requirements I asked would be up to WP.COM, because once the them package is delivered to WP.COM, they can't do nothing about it.
Appologies accepted, I made the following suggestion to them:
So, once you deliver a theme package for WP.COM, it's up to them - and only to them - the way they handle it.
Which is perfectly reasonable, since the framework WP.COM is theirs.
As far as my computer science knowledge goes, I kind of suspected that this would be the answer you'll be giving me, which is perfectly fine to me.
And it's exactly because I know that WP.COM is probably much more difficult to change, that I enlisted a few requirements in terms of translating this theme.
Actually, I would add that the "Latest News" and "Continue Reading" labels are the top priorities, since they represent the most visible impacts for non-english speakers.
Now, I wonder: why don't you guys, knowing about WP.COM lack of flexibility, deliver your themes keeping in mind that not only english users may want to buy them, but also, non-english users?
This would mean, regarding Delicious Theme, adding two fields to the options pannel, the same way you already do to the "Spotlight" label, in the sub-featured section:
1) The blogroll heading section label (which today is fixed with "Latest News");
2) The button label (which today is fixed with "Continue Reading").
Wouldn't it be easier for you guys to implement these small changes, instead of burdening WP.COM with the mission of implementing a certainly bigger change that would apply all themes at once in their framework, just to allow some minor changes in third-party themes to comply with localization requirements?
In my humble opinion, I think that localization requirements should be addressed by theme builders, not by WP.COM.
But maybe I'm missing something, and adding two simple fields to the already existent options panel represents a huge implementing effort.
Nevertheless, think with care about this.