string to character code hex string

[lithium iodate via Digitalmars-d-learn]

On Saturday, 2 September 2017 at 17:41:34 UTC, Ali Çehreli wrote:
> You're right but I think there is no intention of interpreting 
> the result as UTF-8. "f62026" is just to be used as "f62026", 
> which can be converted byte-by-byte back to "ö…". That's how 
> understand the requirement anyway.
>
> Ali

That is not possible, because you cannot know whether "f620" and 
"26" or "f6" and "2026" (or any other combination) should form a 
code point each. Additional padding to constant width (8 hex 
chars) is needed.