To translate the menus you need edit the files that you find in the
neuros-bsp/rootfs/etc/menu directory of the OSD source code.
You need to translate the *_it.menu files.
For the first line in each file you need to translate only the part
after "Title="
For each other line in each file you need to translate only the part
between "Name=" and the "|" character.
After you do this you should re-build the firmware with the language
support enabled.
I don't remember right now the exact details on how to do this.
Maybe someone in this mailing list will be able to give you more help
on this part.
Buona fortuna,
--
nero
> After you do this you should re-build the firmware with the language
> support enabled.
> I don't remember right now the exact details on how to do this.
> Maybe someone in this mailing list will be able to give you more help
> on this part.
>
> Buona fortuna,
> --
> nero
>
Ugo,
I remember I asked a while ago about this (but to do the Spanish
translation) and got more or less the same answer.
Getting a Virtualbox VM image to do this is essential. It should be
possible for anyone to download a VM image, run it, and get an
up-to-date, ready-to-work build environment with scripts that download
from the Net the latest source from CVS or subversion or whatever.
I have no problem making one, if you agree to do the necessary
hand-holding for the time it takes me to get it to work. The latest
release of Virtualbox that apparently makes moving VM images much
easier across systems will surely be of help.
FC
Well, I have not been touching OSD1 code since quite a while.
I had a working OSD1 build env setup on my desktop but that machine
was dismantled when I moved to another country some months ago.
I can try to setup a build env on my laptop and help you out
throughout the process of setting up one yourself in a VM.
However please note that I will be doing this in my spare time and
that my spare time at the moment is very limited.
Therefore be ready to have long delays between responses.
Another option may be to check with OSDng's author and see if he still
has around the dev env that he used for his project.
If he can somehow give the dev env tree to you, and you can install
all the necessary dependencies to the VM where you copy it to, it may
simplify the whole process a lot.
In any case, feel free to ask questions here as you go along, and I
(and hopefully others) will try to answer the best we can.
Cheers,
--
nero