Date: Fri, 22 May 2020 09:24:00 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 246656] Unicode asterisks in ctime(3) may not render correctly Message-ID: <bug-246656-9@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246656 Bug ID: 246656 Summary: Unicode asterisks in ctime(3) may not render correctly Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Manual Pages Assignee: bugs@FreeBSD.org Reporter: danfe@FreeBSD.org CC: doc@FreeBSD.org When tm structure is described in the ctime(3), it's supposed to be rendere= d as C code, with asterisks for char pointer (tm_zone) and comments (/* ... */).= =20 However, they may not be displayed correctly, depending if the user's font = has the glyph for U+2217 (=E2=88=97) ASTERISK OPERATOR (hex e2 88 97). For exa= mple, Luxi, DroidSans, DejaVuSans monospaced fonts have it, but e.g. Consolas does not = (it renders nothing). With traditional "fixed" font, dotted square is drawn. = On the FreeBSD virtual console with default settings, a square is drawn. Would it be possible to use the simple ASCII asterisks instead, like everyw= here else in that page? As I read in the commit history of this file, although = it is under contrib, it has diverged sufficiently from upstream (including a f= ull whitespace commit and large portions rewritten), so perhaps we can also rep= lace these Unicode asterisks with ASCII ones so it renders correctly everywhere. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246656-9>