Maths equations fail in Firefox

I am seeing a lot of errors around the maths equations of the task description. I am using Firefox 56.0.2 (32 bit) on Windows.

--Paddy3118 (talk) 15:46, 6 November 2017 (UTC)

Are they failing in and around the   dj = { ...  ?       If so, look (via edit) at the   commented out   (not normally visible)   HTML code   within   the Rosetta Code task   Leonardo numbers   preamble, which (on my FireFox and IE Explorer web browsers) causes Rosetta Code to fail to render the equation correctly, in fact, it causes Rosetta Code to get a "time out".   The HTML code that is commented out works correctly on Wikipedia, where the HTML code was originally copied from     (exactly copied).   -- Gerard Schildberger (talk) 18:01, 6 November 2017 (UTC)
This sounds like a firefox regression.
I've been seeing a lot of regressions "lately" (actually, the last three or four years ... maybe - it's hard to put strict boundaries on this kind of thing), in browsers and in OSes. I do not know how to address such systematic failures. --Rdm (talk) 18:38, 6 November 2017 (UTC)
In my case, the FireFox that I run hasn't been updated (on my computer) for over three years now.   So, ... no regression here.   -- Gerard Schildberger (talk) 21:42, 6 November 2017 (UTC)^
Let me explain a little further.   When I use the original Leonardo HTML text   (that fails),   and then I see the failure(s) in parsing the HTML code,   I then use (open)   another   Firefox session, I try to access the Rosetta Code site   (,   Firefox comes back (eventually) and tells me that   the Rosetta Code site is down or is busy, try again later.     I concluded that the Rosetta Code site is busy or stuck trying to complete and/or process the failing process and I also concluded that Rosetta Code is failing for all other requests/processes for all other Rosetta Code users during this time   ---   until I close the (Firefox) window that contains the error message(s).     -- Gerard Schildberger (talk) 02:58, 30 July 2019 (UTC)

This page seems to be talking about the Jaro similarity (0=completely distinct, 1=identical), rather than the Jaro distance which is the other way around (0=identical, 1=maximally far apart). Propose that the task be renamed and the description reworded as such. --Markjreed (talk) 17:36, 30 May 2021 (UTC)

Wrong last digit

Some Outputs show
instead of
Why is tat so?? --Walter Pachl 20:13, 20 December 2021 (UTC)

I'd wager it's just floating point inaccuracy. Not all languages handle them the exact same way. Operation order also matters: floating point addition is not commutative. Given that, slight variations are probably to be expected. --Not a robot (talk) 23:51, 20 December 2021 (UTC)
Return to "Jaro similarity" page.