Editing Talk:2657: Complex Vowels
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 38: | Line 38: | ||
::[same person as previous above] looks great now, let me check innthe browser that it had issues in.... [[Special:Contributions/172.70.214.45|172.70.214.45]] 02:24, 12 August 2022 (UTC) | ::[same person as previous above] looks great now, let me check innthe browser that it had issues in.... [[Special:Contributions/172.70.214.45|172.70.214.45]] 02:24, 12 August 2022 (UTC) | ||
:::[different person...] It's never looked Ok for me, on multiple browsers and platforms it always rendered as two separate overstrikes, and even the first does not connect to the √ bit. As an extended root-overstrike is more useful for visually bracketting ambiguities, like the central bit in "(-b±√(b²-4ac))/(2a)" I consider it superfluous for what would be "√(-1)" but cannot be "√(-).1". Nice try, though. | :::[different person...] It's never looked Ok for me, on multiple browsers and platforms it always rendered as two separate overstrikes, and even the first does not connect to the √ bit. As an extended root-overstrike is more useful for visually bracketting ambiguities, like the central bit in "(-b±√(b²-4ac))/(2a)" I consider it superfluous for what would be "√(-1)" but cannot be "√(-).1". Nice try, though. | ||
− | :::Related, I've exchanged "<sup>1</sup>/<sub>2</sub>" for ½. On this device it looks similar (slanted numerator/denominator bar and still an offset, unlike the drawn comic which is vertically aligned | + | :::Related, I've exchanged "<sup>1</sup>/<sub>2</sub>" for ½. On this device it looks similar (slanted numerator/denominator bar and still an offset, unlike the drawn comic which is vertically aligned, but it might look better. And, like the former, probably ''read'' better as screen-readers process the Transcript for the visually impaired. |
:::If it weren't for that latter point, I'd take the idea used in [[2614]] for the in-Explanation <table style="display: inline-table; line-height: 0.6em; vertical-align: middle; font-size:7pt; text-size-adjust: none;"><tr><td>2</td></tr><tr><td>2</td></tr></table> (<code><nowiki><table style="display: inline-table; line-height: 0.6em; vertical-align: middle; font-size:7pt; text-size-adjust: none;"><tr><td>2</td></tr><tr><td>2</td></tr></table></nowiki></code>) and put it as: <table style="display: inline-table; line-height: 0.6em; vertical-align: middle; font-size:7pt; text-size-adjust: none;"><tr><td><u>1</u></td></tr><tr><td>2</td></tr></table> [[Special:Contributions/172.70.85.221|172.70.85.221]] 10:41, 12 August 2022 (UTC) | :::If it weren't for that latter point, I'd take the idea used in [[2614]] for the in-Explanation <table style="display: inline-table; line-height: 0.6em; vertical-align: middle; font-size:7pt; text-size-adjust: none;"><tr><td>2</td></tr><tr><td>2</td></tr></table> (<code><nowiki><table style="display: inline-table; line-height: 0.6em; vertical-align: middle; font-size:7pt; text-size-adjust: none;"><tr><td>2</td></tr><tr><td>2</td></tr></table></nowiki></code>) and put it as: <table style="display: inline-table; line-height: 0.6em; vertical-align: middle; font-size:7pt; text-size-adjust: none;"><tr><td><u>1</u></td></tr><tr><td>2</td></tr></table> [[Special:Contributions/172.70.85.221|172.70.85.221]] 10:41, 12 August 2022 (UTC) | ||
:::Ok, back to the 'root' bit: the (Explanation, not Transcript) current use of <code><nowiki>√<span style="border-top: 1px solid currentColor">-1</span></nowiki></code> is ok''ish'' but hovers the line above the "√" top by about ¾ of the initial down-tick's height (as rendered here... Chrome on Android, for reference), which is clearly not pixel-perfect. Maybe this is an outlier (obscure browser and OS that applies to hardly anyone, right?) so not gonna edit it away, but "√-1" is already unambiguous for anyone who knows what "√" is actually used for. Do we absolutely ''need'' to solve this rendering problem at all? At least until we persuade Unicode to release a special arbitrary-width over-kerning version of the √-character. [[Special:Contributions/172.70.162.77|172.70.162.77]] 09:09, 15 August 2022 (UTC) | :::Ok, back to the 'root' bit: the (Explanation, not Transcript) current use of <code><nowiki>√<span style="border-top: 1px solid currentColor">-1</span></nowiki></code> is ok''ish'' but hovers the line above the "√" top by about ¾ of the initial down-tick's height (as rendered here... Chrome on Android, for reference), which is clearly not pixel-perfect. Maybe this is an outlier (obscure browser and OS that applies to hardly anyone, right?) so not gonna edit it away, but "√-1" is already unambiguous for anyone who knows what "√" is actually used for. Do we absolutely ''need'' to solve this rendering problem at all? At least until we persuade Unicode to release a special arbitrary-width over-kerning version of the √-character. [[Special:Contributions/172.70.162.77|172.70.162.77]] 09:09, 15 August 2022 (UTC) |