Chrome correctly shows the unicode character in the navigation box:
docs/html/dictionary/Function-∀.html [note the quantifier]
and it shows correctly in the source file:
<h1><i>
Function
</i><strong>
∀
</strong></h1>
But then Chrome on Linux renders it as:
Function ∀
.. viewed as file:/// ... etc. I guess this is a problem with the encoding that is assumed by Chrome when browsing files directly. .. wonder how to fix that, as the documentation will be viewed locally.
Placing this line in the head fixes the problem:
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
Last edit: programmer 2016-03-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Chrome correctly shows the unicode character in the navigation box:
docs/html/dictionary/Function-∀.html [note the quantifier]
and it shows correctly in the source file:
But then Chrome on Linux renders it as:
Function ∀
.. viewed as file:/// ... etc. I guess this is a problem with the encoding that is assumed by Chrome when browsing files directly. .. wonder how to fix that, as the documentation will be viewed locally.
Placing this line in the head fixes the problem:
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
Last edit: programmer 2016-03-28
Thanks for the heads up.
I suppose I need to generate the META tag on a per-needed basis.
I will add this.
Marco