Scott Pakin

> It would be nice if we could add SVG files into the repo, showing how each example script's render would look like. Then we could also link the preview...

I'm just a "normal" user, not a style developer. I do, however, find myself increasingly frequently citing papers (most typically `@article`) that use nontraditional page numbering. My preference would be...

> It's interesting to see that people are so fond of displaying the number of pages in the bibliography. As I mentioned, I personally don't much care if `pagetotal` is...

The behavior stays the same.

I just plugged that into my "real" code, and it works! Thanks for the workaround.

In this case, it was [MiniSat](https://github.com/niklasso/minisat), an old but still often used C++ code. MiniSat normally doesn't output times in scientific notation, but I suspect that it uses `printf("%g", …)`...

> Conceptually, time.Duration is fixed-point. Allowing scientific notation may lure one into the false believe that e. g. "1e-10s" is a representable duration. But how is that different from "0.0000000001s",...

> "0.0000000001s" looks funky. I don't follow. We're talking about parsing input, not producing output. Who cares what inputs look funky? They'll be normalized on output. > "100ps" and "1e-10s"...

I wouldn't expect it to accept "+InfhNANns" because that can't be represented by a `time.Duration` (`int64` nanoseconds). The others, while unlikely ever to be used, ideally should be accepted because...

`time.ParseDuration` _already_ uses `float`s (see [line 1668](https://cs.opensource.google/go/go/+/refs/tags/go1.22.2:src/time/format.go;l=1668)) and _already_ performs inexact conversions. Consider parsing `"0.0000000000005h"`, for example: https://go.dev/play/p/gvs16-UT0N8 Once again, the core of my proposal is for `time.ParseDuration` to accept...