Translating Visopsys OS

General discussion about Visopsys.
Post Reply
User avatar
andymc
Posts: 589
Joined: Tue Nov 16, 2010 7:20 pm

Re: Translating Visopsys OS

Post by andymc »

ap0r wrote:So we have Russian, Spanish and English.... Now we only need chinese and we have covered the 80% of world population :P

Can't wait for the release!
World domination awaits :twisted:

I'm currently slogging through a redesign of some of the GUI stuff. Man, it's complicated. Maybe that's my fault, I dunno. Or else GUIs are just complicated.

After that's finished, I should be able to work the new translations and a system for managing them into a new release.
User avatar
andymc
Posts: 589
Joined: Tue Nov 16, 2010 7:20 pm

Re: Translating Visopsys OS

Post by andymc »

Alright my friends. I've made a bunch of changes to support these translations, and it would be great if a couple of you could take them for a spin.

I have implemented user home directories (for everyone except 'admin') under /users.

There is now a config file called environment.conf. There's one for the system as a whole, in /system/config/environment.conf.

User-specific settings (.conf files) go in /users/<username>/config. The admin account uses the system settings for everything.

At login time, the kernel first loads environment variables from the system environment.conf file, then overrides them with any found in the user's home directory.

The environment variable 'LANG' specifies the user's language choice. Locale-specific things, such as binary .mo message (language) files, are installed under /system/locale.

I'm still working to integrate language choice - for the user at login time, and for the system at install time, into the programs. So far, I've created a 'language chooser' dialog window that can be invoked from programs, and I've built that into the 'User Manager' (/programs/users) program. You'll find a 'set language' button there now.

To test things out in the current form, you should login to the system as admin, start up the user manager, create a new user, and then select a language for him. Log out, and back in as the user you created. The user environment propagates down through a process tree, so logging in will set it for everything that follows, but you can also open a command window, use the 'setenv' command to set 'LANG', and then any programs you launch from the command line will inherit that. You can also set it system-wide in /system/config/environment.conf, but I'm still working on making that affect everything, such as the initial login windows.

It looks pretty good! Could you guys click around, try things out, and possibly update the .po files with any missing strings? It looks like the 'View' program is missing some things, for example. Note that the .po files are now saved with the ISO-8859-15 character set. Visopsys doesn't support UTF-8 yet. I've created a couple of scripts, utils/makepot.sh and utils/mergepot.sh in the source tree, for automating updates. makepot.sh is designed for individual program source files, though; you have to do manual xgettext command when you want to combine messages from a bunch of different source files into a single .pot, a la libwindow.pot.

Of course, a lot of the things the user sees are defined in the config files, such as /system/config/desktop.conf, etc. Any chance you guys could translate those? I'll work out a system to use different ones, based on the current language.

Source code zipped here: http://visopsys.org/files/visopsys/viso ... 09-src.zip
fosforito

Re: Translating Visopsys OS

Post by fosforito »

Nice! I'll download the source and try it out when I get home. And I can translate the desktop.config file and view-program to German and Spanish. :D
User avatar
ap0r
Posts: 105
Joined: Tue Feb 14, 2012 12:40 am

Re: Translating Visopsys OS

Post by ap0r »

I'll try it as soon as i am free from some other stuff!
Image
Image
User avatar
andymc
Posts: 589
Joined: Tue Nov 16, 2010 7:20 pm

Re: Translating Visopsys OS

Post by andymc »

8-) Thanks fellas
User avatar
ap0r
Posts: 105
Joined: Tue Feb 14, 2012 12:40 am

Re: Translating Visopsys OS

Post by ap0r »

I seem to get an error when compiling that code

Code: Select all

make[4]: Leaving directory `/home/ap0r/Desktop/VISOPSYS/source/ports/ntfsprogs/libntfs'
make -C de
make: Entering an unknown directory
make: *** de: No such file or directory.  Stop.
make: Leaving an unknown directory
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/ap0r/Desktop/VISOPSYS/source/ports/ntfsprogs'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/ap0r/Desktop/VISOPSYS/source/src/lib'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/ap0r/Desktop/VISOPSYS/source/src'
make: *** [all] Error 2
ap0r@ap0r-vm:~/Desktop/VISOPSYS/source$ 

Image
Image
User avatar
andymc
Posts: 589
Joined: Tue Nov 16, 2010 7:20 pm

Re: Translating Visopsys OS

Post by andymc »

Oops, sorry! The archive-source script was deleting all the 'de' directories, because I never wanted to distribute the old translations. The link above should retrieve a fixed version now.
User avatar
ap0r
Posts: 105
Joined: Tue Feb 14, 2012 12:40 am

Re: Translating Visopsys OS

Post by ap0r »

Well, spanish seems to be OK, except that some strings are still english. as was discussed above. The strings that I translated seem OK, but ofcourse i will do a complete revision in search of errors, out of context, etc.

You should probably modify the set language dialog so that once a new language is chosen, you get a messagebox telling you that you have to reboot in order for changes to be seen.
Image
Image
User avatar
ap0r
Posts: 105
Joined: Tue Feb 14, 2012 12:40 am

Re: Translating Visopsys OS

Post by ap0r »

ap0r wrote:You should probably modify the set language dialog so that once a new language is chosen, you get a messagebox telling you that you have to reboot in order for changes to be seen.
Did it myself, see attached file
Attachments
users.c.zip
(5.19 KiB) Downloaded 892 times
Image
Image
User avatar
andymc
Posts: 589
Joined: Tue Nov 16, 2010 7:20 pm

Re: Translating Visopsys OS

Post by andymc »

Cheers ap0r. It should only require logging out, and back in. I'd like to fix that, though. If I can get the window shell to notice the change to the config file, or add a call to the window system, then it won't be required. Still working on it!
Post Reply