Re: Describing Scheme libraries (and thus SRFI's and R7RS) in a "machine readable" format (and rendering in various formats) Ciprian Dorin Craciun (10 Jul 2018 19:05 UTC)

Re: Describing Scheme libraries (and thus SRFI's and R7RS) in a "machine readable" format (and rendering in various formats) Ciprian Dorin Craciun 10 Jul 2018 19:04 UTC

On Tue, Jul 10, 2018 at 9:59 PM Arthur A. Gleckler <xxxxxx@speechcode.com> wrote:
>> > 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.

By "parsers" I meant S-expression parsers (and in fact other parsers,
that might be down the pipeline up to HTML).

(Although I still see from time-to-time some "broken" web pages which,
for some strange reason, make the browser want to apply "code-pages"
instead of UTF-8...)

Ciprian.