Font display issue - font characters with accent marks render incorrectly
Font display issue - font characters with accent marks
This also relates to Italic display / Problems / Discussion Area - TenFourFox Support [ https://tenfourfox.tenderapp.com/discussions/problems/2 ], but since "Comments are currently closed" for that discussion, I'm starting this thread.
I went NiftyTelnet 1.1 SSH r3 for Mac OS 8.6 - Mac OS 9.2.2 download page at the site of Jonas Wallden
The accented "e" in Walden rendered incorrectly
TenFourfox v17.0.4 under OS X 10.4.11
Fonts for: Western
Proportional: Serif
Serif: Times
Sans-serif: Helvetica
Monospace: Courier
Default Character Encoding: Unicode (UTF-8)
Note: The accented "e" in Walden rendered incorrectly with the same issue with "Allow pages to choose their own fonts, instead of my selections above" checked or unchecked.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Chris (chtrusch... on 28 Mar, 2013 09:27 AM
Hello Martin,
this is unrelated to font rendering, it's just the wrong character encoding (the website doesn't provide any character encoding information, which is invalid html). In this case, TenFourFox has to guess (or fallback to UTF-8), and it's guessing wrong. If you change character encoding to "Western ISO 8859-1" (View>Character Encoding) the é will be displayed correctly, as it is here in my post.
2 Posted by Martin A. Totus... on 28 Mar, 2013 10:07 AM
Thanks!
I'd also previously tried setting the Default Character Encoding to Western ISO 8859-1, via Preferences > Content > Default Font > Advanced > Default Character Encoding:, but that didn't have any effect on the accented "e" in Walden rendering incorrectly.
Doing it instead through View > Character Encoding - from the TenFourFox Menu bar, as you suggested, does the trick.
Support Staff 3 Posted by Cameron Kaiser on 29 Mar, 2013 04:56 PM
Glad to hear it. I'll go ahead and close this issue. If you still have issues with it, just reply and it will reopen automatically; otherwise, no reply is needed. Good luck!
Cameron Kaiser closed this discussion on 29 Mar, 2013 04:56 PM.