OK, the bug with \.{32} appearing in the text is due to the following
function in tex-accents.C:

string DoAccent(char c,tex_accent accent)
{
        return DoAccent(tostr(c),accent);
}

Currently, I have changed it to 

string DoAccent(char c,tex_accent accent)
{
        return DoAccent(string(1,c),accent);
}

and, sure enough, it works. 

My question is: what is the right way of translating a char to string?
Using string(1,c) seems a bit strange to me. On the other hand, is it
reasonable that tostr(char) use the char as a number? Shouldn't it use
it a real char instead?

JMarc

Reply via email to