On Tue, Jul 10, 2018 at 11:41 AM Ciprian Dorin Craciun <xxxxxx@gmail.com> wrote:

This is strange... All "code" items (including inline identifiers and
the snippets) are configured to be rendered with mono-space font,
namely `Fira Mono`.

Could you give me an example where such formatting is not applied?
Perhaps your browser doesn't support font loading (or has been
disabled). In any case I'll have to change my CSS to include other
fonts as fallback.

Interesting. The fonts work correctly on Github, but not on data.volution.ro. It looks like Chrome is falling back on default fonts because the network connection is slow:

Slow network is detected. See <URL> for more details. Fallback font will be used while loading: <URL>
FiraSans-Regular.woff:1 Failed to load resource: the server responded with a status of 404 ()
FiraMono-Bold.woff:1 Failed to load resource: the server responded with a status of 404 ()
FiraSans-Bold.woff:1 Failed to load resource: the server responded with a status of 404 ()
FiraMono-Regular.woff:1 Failed to load resource: the server responded with a status of 404 ()
FiraSans-Regular.ttf:1 Failed to load resource: the server responded with a status of 404 ()
FiraMono-Bold.ttf:1 Failed to load resource: the server responded with a status of 404 ()
FiraSans-Bold.ttf:1 Failed to load resource: the server responded with a status of 404 ()
FiraMono-Regular.ttf:1 Failed to load resource: the server responded with a status of 404 ()
FiraSans-Italic.woff:1 Failed to load resource: the server responded with a status of 404 ()
FiraSans-Italic.ttf:1 Failed to load resource: the server responded with a status of 404 ()

> Even better, it would be great if you could use a formatter that supports Scheme, so that keywords would be in bold face, etc.

I guess this is a little bit harder to do, especially since many
snippets are not 100% Scheme-compliant. (Or would a simple
regular-expression-based find-and-replace suffice?) However this is
quite low on my TODO list at the moment (I have to get back at
documenting my interpreter's builtin functionality)...

Yes, that makes sense. This is only a nice-to-have feature, anyway.

> I found a few instances of raw TeX formatting, e.g. "$\Sigma$" appears in the documentation of string-upcase. It would be good to fix those.

Yes, I forgot about those... I'll have to think how to best handle
these... I think the best would be to use HTML-compliant escape
codes; the other alternative would be to use the character's UTF-8
encoding, but this could break some parsers.

Ever serious browser supports UTF-8 these days. I'm not sure whether UTF-8 or HTML entity encodings would be more widely supported.

Unfortunately the SRFI's are again quite low on my TODO, but I'll add
them once I implement support for them in my interpreter.

I understand. Prioritizing is one of the most important practices for success, as far as I can tell.