Jump to content

Talk:Simple precedence parser

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

HTML entities

[edit]

@AHMartin: Greetings! Regarding this revert: https://en.wikipedia.org/w/index.php?title=Simple_precedence_parser&oldid=prev&diff=1102340703&diffmode=source The idea behind converting these characters is to keep markup simple, make wikitext a little more WYSIWYG, and avoid the need for editors to learn about HTML entities. My change didn't make an observable difference in the rendered article to me on Firefox. What are you seeing that looks like the change "broke many precedence relations"? -- Beland (talk) 16:48, 4 August 2022 (UTC)[reply]

All (and I do mean all) of the ≐ symbols were replaced with ⋖'s.
(The equal-sign-dots were replaced with less-than-dots).
And I can see that in the pre-reverted version using my Firefox ESR 52.9.0 (64-bit),
as well as Microsoft Edge 103.0.1264.77 (Official build) (64-bit).
(I'd also love to spruce up the example execution trace
at the end of the Example section with the proper characters
instead of vanilla less-than, equals, and greater-than.
But trying those same HTML entities, the PRECEDENCE column entries
wander side to side proceeding down the page.
Either they come out in a proportional font,
or the column spacing just needs to be massaged.
I didn't have time to figure it out (and I might have picked
a bad solution even if it worked).
FWIW, I didn't try copy/pasting characters from
your edit, but perhaps that would render better.
Or maybe a different markup than pre (code?) would work better).
Sorry to have thrown the baby out with the bathwater by the reversion,
but this stuff is not my forte, and I wasn't positioned to tweak
what you had done. If you can reapply your edit without busting
the equal-sign-dots, and achieve a level of taste and style
above my casual understanding, I have no objection.
If the actual rendered text wasn't busted,
I would never have looked under the hood.
I didn't come in to this with a preconception of how
best to render those characters.
Hope this clears it up; sorry to harsh your mellow.
/AHM/THX AHMartin (talk) 04:13, 5 August 2022 (UTC)[reply]
@AHMartin: Ack! That's a major problem; thanks for clarifying. Turns out I had pasted the wrong character in my code, and my manual review missed it, twice. Thanks for catching that! -- Beland (talk) 18:54, 13 September 2022 (UTC)[reply]
I've copied-and-pasted what I assume are the correct characters into the "pre" section of Examples. The alignment seems to be working for me, but it would be a good idea if you checked to make sure I did it correctly. -- Beland (talk) 19:05, 13 September 2022 (UTC)[reply]