On Fri, Aug 27, 2021 at 10:31:45AM -0700, Per Bothner wrote: > > > On 8/27/21 10:21 AM, Patrice Dumas wrote: > > > I don't really have a good answer, of course. I'd think to try U+0361 or > > > its HTML equivalent, as my test here > > > <p>test o͡o test o͡o</p> > > > but I honestly have no idea which browsers show what, and which fonts > > > support the character ... > > > > Actually, this looks quite good on firefox, both with the actual utf8 > > encoded diacritic and entity. You can obtain the utf8 encoded diacritic > > when converting to html with --enable-encoding. I guess that we can > > generate numerical diacritic entities in the default case, it'll > > probably be better than the plain text accent markers. > > It works fine also on Google Chrome, and on Epiphany (based on the > Safari/WebKit engine).
Ok. I just committed the change. Some combinations of accents do not look so well, but they probably do not make much sense. > Just generate 'oo͡o' and be done with it. > (I would prefer using the hex value - one reason is it's easier to search for > its meaning.) For now we use numerical entities everywhere. If this changes, it should be everywhere too. -- Pat