There is nothing like that on my wishlist.
Logging, Threading, GUI interfacing and about anything else that takes place at runtime belongs into a library. I wish some of the good existing solutions for these topics were official, generally accepted (and implemented!) standards, but it's OK the way it is.
Version control does not belong into language, and never should - like editing, it is strictly outside the language. You don't use the source to check it in itself, don't you. You use an IDE or something - and that's where these features belong. Bug tracking, versioning, collaboration, all these are activities and therefore belong into the tools used in working on the source.
Documentation is part of that, too, but needs a bit of linking with the source. Oxygene and JavaDoc aren't exactly bad ideas IMHO, but I would much prefer an accepted standard for liniking from source with a single (G)UUID to the documentation which is placed in a separate file - would be the cleanest way. Comments are to comment the source, not really suitable for extensive documentation.
About internationalization, that is also a non-issue. Outside of testing, you shouldn't put any text into your source that is intended for the user to read. It's separate resources, and there are well established tools for handling them as well. And if you are lazy and still need internationalization, there is the gettext family of tools.
Strings are supposed to be Unicode or UTF-8 anyways, IMHO. This should be the default, and can be set as such in many environments.
Most things are there already, really. You just need to know about them and use them.
Languages should be concise and tight, in my opinion. Few keywords, powerful syntax. Everything else belongs outside, into libraries and tools.
And if there is/were a good set of free and open standard libraries, I would be pleased.