Jaime Villate <villate at fe.up.pt> writes:
> I'm in favor of this proposal. The current method is too complicated,
> takes too much time and (at least in my case) it is frustrating not
> being able to look up the manual after all that trouble.
>
> Also, as a translator I have given up the translation job because it
> is very hard to write in a foreign language without being able to use
> UTF8 characters. Not to mention that the PDF version of the
> documentation produced by Texinfo is ugly. I could do much better
> with a simple Wiki.
Obviously this sounds like me harping on, but... I think UTF-8
characters will "just work" if we fix our currently broken Texinfo
parsing. The current perl script does a heroic job, but can't possibly
deal correctly with variable length encodings. I would shut up and show
you the code... but I left my Windows laptop at work this evening.
> Why do the binary files that describe() opens have to be rebuilt by
> everyone? Couldn't they be placed in the Sourceforge files area for
> those who are not willing to spend the two hours it takes to build
> them in the Raspberry Pi?
Binary files? I thought the files were just alists in text format?
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/20131205/5b87494c/attachment-0001.pgp>;