Ralf Hemmecke wrote:
>
> Hi Waldek,
>
> what does this change mean?
>
> https://github.com/fricas/fricas/commit/6282cdc03ed979c1af4407b5da5782a1d9e=
> 248f2#diff-51fbd4ac56903360e42b455fa1f38a9dL269
>
> -These "rules" are hardcoded into the /\ , \/ and =C2=AC implementations
> +These "rules" are hardcoded into the /\ , \/ and - implementations
>
> FriCAS does not understand UTF-8 input files?
FriCAS is mostly agnostic about encoding. But Lisp-s choose
encoding based on locale and signal error on what they consider
invalid codes. That actually problem caused by Unicode
support: Lisp have to transcode on input to Unicode and
does not know what to do when code is not in translation
table.
Currently anything beyond 7-bit ASCII causes trouble in
C locale. Lisp can fall back to C locale when you select
locale which is not installed. In other words it dangerous
to assume that anything beside C locale is available.
> It's probaly OK for now, but I'd prefer to have proper latex in the
> literate parts of the .spad file. The above is certainly not. Neither
> before nor after the change.
Yes, it was not latex. AFAICS you were the only person who
actually get close to LP principles.
> I'm much in favour of 1) non-splitting .spad files and 2) the )if
> LiterateDoc convention. If we can fix that, I would try to put the few
> files with literate content into a shape that one can turn into a .pdf
> file, just like the xhash.spad example.
Splitting (or not) .spad files is a technical thing. How long
it will last depends on resolving technical problems.
--
Waldek Hebisch
[email protected]
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.
