Also, I think that HTTP got it right when encoding is returned with the document (rather than specified in the link), but if you've already made the mistake of dealing with byte offsets you're tied to a particular representation.
Also, I think that HTTP got it right when encoding is returned with the document (rather than specified in the link), but if you've already made the mistake of dealing with byte offsets you're tied to a particular representation.