Robert Dodier <robert.dodier at gmail.com> writes:
> On 2013-05-02, Raymond Toy <toy.raymond at gmail.com> wrote:
>
>> LANGUAGE=es_ES: maxima-Local
>
> Doesn't that want to be es_ES.UTF-8 ?
>
> I tried it with LANGUAGE=es_ES.UTF-8 and I get the expected result.
> Without UTF-8 I get an error or mixed up display. Maybe you mean to say
> that even without UTF-8 it should be displayed correctly?
>
>> AIUI, we basically just suck in a bunch of bytes and then send them
>> out directly because the info file has the text encoded using the
>> desired encoding.
>
> No -- first we seek to a file position (more about that below) and then
> read a number of characters and then output those characters.
>
> As we know, CLHS requires only that file position be monotonic. In
> practice, every Lisp implementation I have encountered uses byte offset
> as file position. (There may well be some which don't.) So, in effect --
> seek to byte position, then read characters.
>
> There is a reimplementation of cl-info on a branch, but anyway the
> current version on master works as described above.
May I suggest that no-one spends much time on this over the next couple
of days? I've been working on refactoring the parse-info branch into a
compile time thing (and I've got some way with it). Hopefully I'll have
something for people to poke holes in by the end of the weekend.
I think that my changes should fix the encoding problem Ray describes on
every lisp except GCL (because it doesn't have support for external
formats).
Rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: <http://www.math.utexas.edu/pipermail/maxima/attachments/20130502/9ed1c6b4/attachment.pgp>;