Hi Alejandro,
I agree. The best we can do is to localize the English text from the
original texi files. Special characters (ñ, á, ü, etc.) might be encoded
using either some macro (@'a) or direct input (after choosing the proper
encoding, i.e., UTF-8 for the texi files) - that was the same case for
Octave's Spanish package http://octave.sourceforge.net/es/index.html.
On other related business, on May 26 I've applied for the registration
of a new project at the Savannah repository. At the moment I'm still
waiting for its approval. The idea is to store the Spanish translation
GSL Reference Manual on that server, it that OK for you? Otherwise we
can explore other alternatives.
Javier
On 28.05.2010 03:40 PM, Alejandro Cámara Iglesias wrote:
Thanks Daisuke,
I think that's the best way to do it, since, as Daisuke pointed out, it's
just to replace the English macros and text for its Spanish translation. How
do we do it Javier? I already cloned the git repository (I guess the Bazaar
is not ready yet) and see the texinfo sources of the manual.
--
Alejandro Cámara
2010/5/28 Daisuke TOMINAGA<[email protected]>
Hi Ivan and Alejandro,
Japanese translation do not use the original texinfo files because of
localization confusion among tools (texinfo, latex, etc.) I could not
resolve it and newly wrote latex sources. So Japanese version do not have
texi files.
I think the best way is replacing English texts in texi files with your
language. I wanted to do so.
The latex source:
http://www.cbrc.jp/%7Etominaga/translations/gsl/index.html
http://www.cbrc.jp/%7Etominaga/translations/gsl/gsl-1.14/gsl114platex.tar.gz
--
Daisuke TOMINAGA, Ph. D.
Computational Biology Research Center, AIST
2-4-7 Aomi, Koto, Tokyo 135-0064, Japan
Tel:+81-3-35998080, Fax:+81-3-35998081
[email protected]
_______________________________________________
Help-gsl mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gsl
