Re: \=d in a table: weird behaviour

["Mojca Miklavec" <mojca.miklavec.lists@gmail.com>]

On 4/18/06, Hans Hagen wrote:
> Mojca Miklavec wrote:
> > Hello,
> >
> > It seems that \= and table interact in a strange way in the following example:
> >
> > \starttable[|c|]
> > \NC \=d \NC\NR
> > \stoptable
> >
> > \=d alone works OK. I suggested to use $\rm\overline{d}$ to the one
> > who asked me about it, so it's not really crutial to fix that, I just
> > find it a bit strange.
> >
> is dmacron a valid char? ... up to mojca

Thanks, it works this way, but there's no need to add it to the
definitions in the core since it's not even in unicode. (The only
strange thing is that \=a ("valid" char) or \=d work OK in text flow,
but not in the table, where faking the character seems to interact in
a strange way with the table typesetting.)

But this solution is OK for me, thanks again,
    Mojca

> \unprotect
>
> \startencoding[default]
>
>   \definecommand Dmacron {\buildtextaccent\textmacron D}
>   \definecommand dmacron {\buildtextaccent\textmacron d}
>
>   \defineaccent = D {\Dmacron}
>   \defineaccent = d {\dmacron}
>
> \stopencoding
>
> \starttable[|c|]
> \NC test \dmacron\ test\NC\NR
> \stoptable
>
> \end