issue 1 - this has already been fixed internally and will be part of the next release (which should be soon).
issue 2 - I see what you're describing, looks like it applies to both HTML & XSL results. It's now been logged in our tracking system, and will be fixed in a future release.
In the meantime, here's an XSL workaround for problem #2. In the XSL, find the source that looks like