3 ms·
n̈ renders fine on my browser, but there is no compose-key sequence for it on my system. I suspect the reason it renders fine is that 'n' in the font I'm using
by cryptonector 2mo ago
n̈ renders fine on my browser, but there is no compose-key sequence for it on my system.
I suspect the reason it renders fine is that 'n' in the font I'm using is small enough that the combining mark can be rendered by "overstriking" a diaeresis.
- pseudohadamard 2mo agoIt seems to be font-related, when I edited the text it rendered fine but viewing the resulting page has the unlauts floating in space after the n.
- cryptonector 2mo agoI also see the same, and I suspect it is due to the lack of a precomposition for n̈.