imsky / imsky/PocketEuler

Unicode floor glyphs reversed

Open
#55 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C
Stars
118
Forks
11
PR merge metrics
No merged PRs in 30d

Description

When I look at Problem 197, now and before any of the recent changes, the unicode glyphs for floor (`⌊x⌋`) are reversed , with the tails at the bottom , turning outwards instead of inwards:

https://github.com/imsky/PocketEuler/blob/1e4be304b3e42702bf3e8e6fe9d0cb841e976db8/README.md#problem-197

floor glyphs on Firefox 47 on Ubuntu 16.04:
![floor glyphs on Firefox 47 on Ubuntu 16.04](https://cloud.githubusercontent.com/assets/15092/16716681/e8a66798-472d-11e6-928b-ff6b4c090654.png)

rfloor with tail out looks like an upper case `L`, so it is confusing.
This also occurs on Chrome 47.0.2526.106 / Ubuntu.

It doesnt occur when those glyphs are enclosed with `back-ticks`, and it also doesnt occur when I post those glyphs to https://en.wikipedia.org/w/index.php?title=Project:Sandbox&action=edit§ion=new , which makes me think it is a font choice by Github.

This problem doesnt occur on either of my Android devices.

fwiw, ceiling ( `⌈x⌉`) works well in the two cases where it was used.
https://github.com/imsky/PocketEuler/blob/1e4be304b3e42702bf3e8e6fe9d0cb841e976db8/README.md#problem-217
https://github.com/imsky/PocketEuler/blob/1e4be304b3e42702bf3e8e6fe9d0cb841e976db8/README.md#problem-255

Need to check some more devices to see if this is a widespread problem, or limited to just me, or just Ubuntu 16.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in README.md at Problem 197 and compare its floor glyphs with the ceiling glyphs in Problems 217 and 255. Reproduce the rendering in the reported Firefox and Chrome on Ubuntu environments, including the backtick-wrapped form, to determine whether the issue is controlled by the README markup. Done means the rendering behavior is understood and a repository-controlled correction or clear limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.