Re: [e-users] E-16 in spanish

[Kim W. <ki...@wo...>]

jacinto calvo sintes wrote:
> Hy, as i can't program more than html and web things, and want to do something 
> for E, (no time for theme drawing), I started this weekend to translate full E-Help to 
> spanish language. My idea is ending with full translated and functional E in spanish 
> language, help, menus, actions, names and so on (i'll try Eterm help but it's 
> amazing :-) )  
> Maybe there's no point to do that becouse there are more important things to do 
> in, but i can't understand more than <b>bold</b> simple code. 
> If there's anything to write more or help needed in easy things i'd pleased to help if 
> i've time. 
> If there's no way to introducing spanish language in E doesn't matter at all, once 
> Help is finished it might help someone to improve his E. 
> At the moment only got half of help translated in dirty quick spanish, as soon as i 
> got something readeable, if you're interested i'll pass it. Also help is welcome. 
>  
Documentation updates and translations are most welcome. Much of that is
probably a bit old, to put it mildly :)

The documentation and other stuff that could be translated comes in
a number of pieces:

a) The on-line help. This would be E-docs/MAIN.es for a spanish version.
Entirely straightforward, I believe.

b) Localized text strings within E. Spanish version is in po/es.po.
I know next to nothing about this (gettext) stuff but I believe it is
pretty standard and there are tools to help doing it.
I don't know for sure but I assume that much of the E16 .po stuff is
somewhat outdated.

c) Localized configuration stuff. Some of the menu and tooltip texts are
in config/<thisandthat>.cfg.<lang>. I'm not really happy with this.
If possible, I think that the localization should be done when E reads
the (english) configuration files, i.e. that the translation again goes
into the .po file.

d) Localized theme stuff, e.g. <sometheme>/tooltips.cfg.<lang>. I'm not
entirely sure what it's there for. Maybe to speed up some X11 font
handling. In any case, I don't think this possibility should be used.
If there is a reason to do something locale dependent here, it should be
possible to use the configuration preprocessor (epp) to set up things
(font?) in one place only.

e) Localized "maintenance scripts" (e.g. scripts/e_cache_clean.<lang>).
Again, I think the localization should be done within E via gettext.

f) Did I forget someting? I hope not. There are already way too many
pieces :)

/Kim