bnewbold

I redeployed and no change. As of today this problem seems to be happening even more frequently. I was able to reproduce with `wget`, so problem is definitely server-side, not...

After deploying some small translation updates this morning, I am no longer able to reproduce the problem. I suspect that the issue is related to our translation (i18n) infrastructure and...

Oh no, it is back! https://scholar.archive.org/search?q=Sidewalk+Measurements+from+Satellite+Images+Preliminary+Findings 

This issue has come and gone over the past couple months. Will prioritize getting a reproducible example of this bug and getting it fixed.

I pushed some changes to production just now which I hope have resolved this issue. There is a small impact on latency, which is unfortunate. --- A few notes on...

Numbers should be simple using http://babel.pocoo.org/en/latest/numbers.html ``` In [24]: format_number(14900, locale='hr') Out[24]: '14.900' ``` Though it doesn't seem to work for shorter numbers: ``` In [31]: format_number(2, locale='hr') Out[31]: '2'...

Shouldn't it be "2.", like we would use "Showing {num} out of {num}..." at the bottom of the page? Or maybe I am misunderstanding... is it only ordinals like "1."...

Finally revisiting this, and maybe I understand better. The ordinal/non-ordinal distinction can be handled in the _template_, as opposed to trying to get babel's number formatting routine to figure it...

Most of the numbers should be fixed now. I _believe_ that the year display will be fixed once the translation files are pulled from weblate; i'll keep this issue open...

Pushed updates, and they look correct to me (from a brief scan). @milotype if you get a chance, please verifiy and close this issue if it looks good. I'll close...