RE : Seeking Help with Windows Maxima installer localization


> -----Message d'origine-----
> De?: maxima-bounces at math.utexas.edu [mailto:maxima-bounces at math.utexas.edu] De la part de
> Robert Dodier
> Envoy??: vendredi 17 novembre 2006 03:16
> ??: fateman at cs.berkeley.edu
> Cc?: Maxima at math.utexas.edu
> Objet?: Re: [Maxima] Seeking Help with Windows Maxima installer localization
> 
> On 11/16/06, Richard Fateman <fateman at cs.berkeley.edu> wrote:
> 
> > I think that the current typesetting convention uses a painfully large
> > amount of space for examples (at least in the version I look at); the
> > on-line Mma manual which provides for "click here for more examples" makes
> > excellent use of space.
> 
> Certainly in the html docs it should be possible to fold up the
> examples by default, and then show them in response to a click.
> Probably some simple script embedded in the html could do that.
> (Something I don't know anything about.)

I suspect that it will be difficult to do that because you need to have 
a call to a script function for each examples. And it is certainly not 
easy to do that manually regarding the numbers of examples in the manual.
The best would be to automate this but I don't think that it can be done
easily because the Html manual is generated by texi2html.
More precisely you need to include something like the following in each
example.

<img id="img1" src="IconActionHide.jpg" onclick="javascript:reverseVisibility('img1')"
width="16" height="16"> 
title of example
<div id="div1">
the body of example
</div>

Note the use of ID in img and div tags. Because id must be unique you need to 
Use different one in the same Html file. For example you need to use img2 and 
div2 as id for the next example and img3, div3 for the next etc..
the only way to avoid this would be to include the body of the function
reverseVisibility() in each image tag.
But the body of this function is relatively big. This imply a big time to load
The file. Particularly if an anti-virus software is configured to scan the script.
Also, by the use of id we can't force to have only on item to be open/visible at the same time.
This is not possible without the use of id.

I have already written this for the site of my laboratory.
http://www.lpn.cnrs.fr

But in this case the JavaScript is dynamically generated by server side PHP script.



> > Also keywords and distinctions would be useful.  E.g. factor/ factorize
> > /roots should refer to the factor command but also root finding commands
> > like realroots and Newton and polynomial approximate zeros etc.
> 
> I want to implement a category system in the near future,
> the notion being that an item can belong to multiple categories.
> E.g. the category illustrated above could be "Roots of equations"
> or something like that, but polynomial factorization could also
> be categorized under "Polynomials" and Newton's method under
> "Numerical methods". There would be a separate documentation
> item for each category, with a list of the topics which fall into
> that category, plus maybe a summary or overview.

Very interesting! Note that I read something about a case like this
in po4a documentation. If you do that, translator team must do the same.
Then the "same" work must be doing many times. It seems that po4a can manage
this case by extracting the text from the file by the use of gettext.
But I read too that the texinfo module for po4a is not in production state.
May be it can by interesting to wait for.


Laurent.