Translating Visopsys OS
Re: Translating Visopsys OS
I've used "jenswagner20 at ovi dot com"... maybe check your Spam folder..
Re: Translating Visopsys OS
Nice! now we have to wait for the builds to be ready, and should we have different isos with diferent languages or a way to select the language at runtime?
Re: Translating Visopsys OS
Hm... I think one single iso would be better and easier. Like an Ubuntu Live CD : one CD with all languages and on installation, install only the selected language. What do you think?
Re: Translating Visopsys OS
That's the way to go, in my opinion. Do you guys have any ideas about how the language selection should look/work in the GUI?
Re: Translating Visopsys OS
Maybe a language selection dialog should come before the "install or continue without installing"-dialog. With all languages in a dropdown box.
Re: Translating Visopsys OS
The GUI doesn't have dropdown menu widgets, yet. I'm in the middle of rewriting the implementation of menus (menu bars, right-click menus, etc).
I think what needs to happen is:
- Language choice is an environment variable used by programs when they're launched
- A button or other widget to select the language on the 'welcome' (install/continue) dialog that runs at first boot (always for read-only 'live' media)
- A button or other widget to select the language in the Users program, when user accounts are created
- a way to save per-user settings (language being the first of many to come, I'm sure).
a) in per-user home directories, say under /users, in a settings file; or
b) in a single centralized configuration file
- The installer would get the current choice from the environment variable (set by the welcome dialog, or when the current user logged in) and use that to set the language for 'admin' in the new installation (could maybe still offer a choice at install time)
Sound reasonable? And/or should there be an overall 'system' language variable? For the login screen? Or just force 'admin's language to be the default?
I think what needs to happen is:
- Language choice is an environment variable used by programs when they're launched
- A button or other widget to select the language on the 'welcome' (install/continue) dialog that runs at first boot (always for read-only 'live' media)
- A button or other widget to select the language in the Users program, when user accounts are created
- a way to save per-user settings (language being the first of many to come, I'm sure).
a) in per-user home directories, say under /users, in a settings file; or
b) in a single centralized configuration file
- The installer would get the current choice from the environment variable (set by the welcome dialog, or when the current user logged in) and use that to set the language for 'admin' in the new installation (could maybe still offer a choice at install time)
Sound reasonable? And/or should there be an overall 'system' language variable? For the login screen? Or just force 'admin's language to be the default?
Re: Translating Visopsys OS
Or under /system/config/ for global language settings, and /system/config/users/.... for per-user override?andymc wrote:- a way to save per-user settings (language being the first of many to come, I'm sure).
a) in per-user home directories, say under /users, in a settings file; or
b) in a single centralized configuration file
I guess I think this is a design decision that's about more than just this particular language issue. It would be the basis for any future per-user stuff, too.
Re: Translating Visopsys OS
I would use the "A" option. That way you have two disctint advantagesandymc wrote: a) in per-user home directories, say under /users, in a settings file; or
b) in a single centralized configuration file
1) If you have a single settings file, if you lose it or it gets corrupted, you have to reenter configurations for all users, while a single config file per user allows you to backup your individual config without needing to edit sensitive files, and also if one user becomes corrupted, you can still log in with another user and restore the config.
2) You're not putting all your eggs on a single basket.