AFAIK the time zone is preselected according to the language. So we should perhaps remove it from the content file. You may try to set the language in the content file instead.

Languages are not identical to countries. e.g. I want my PC in English, yet I live in Belgium. Belgium in itself has three languages, Dutch, French and German. Most people I know install their system in English, because it won't confuse them as much and makes it easier to find solutions for problems.

It is not a real big issue, so perhaps setting it to WONTFIX is the best for now.

I'll add a check for content/control file before setting timezone; but not now.

reopen

I'm not sure what should be correct solution if content file includes time zone - should the setting of timezone according to language be skipped at all? But current content file always includes time zone...

Maybe we should leave out the time zone from content file at all, but might introduce optional timezone value to control file.

Andreas, this needs to be defined (not urgently now, of course).

I suggest to remove it from the content file, seems this is the only sane default.

Who will do this?  Is this a job for autobuild team?

Rudi?

I think removing this can be done in the content file, but removing the
support for having it there is just wrong.

The language is only a first guess for the timezone, and that guess will
be more often wrong than right.

so: yes, I can remove it from the content file, the question is what other
uses we might break by doing so ...

> The language is only a first guess for the timezone, and that guess will
> be more often wrong than right.

maybe - but yast doesn't look to content file anyway (not because it wouldn't be possible, but because it is not defined how should it use such info)

Does linuxrc use it?

no, linuxrc does not look at /content at all

So, back to autobuild: looks like noone uses this value so it can be removed. Or provide correct definition of how should yast/linuxrc use it.

LANGUAGE: default language yast should start up with
TIMEZONE: default timezone yast should present to the user

these have been defined since the original UL media description ...
(http://w3.suse.de/~kkaempf/specifications/UL-media-description/media-descr.html)

YaST usese the LANGUAGE entry, this bug is not about this one.

With TIMEZONE, we're back to comment #5. It is clear what should TIMEZONE mean when it conflicts with the timezone based on language. Just look - currently it always conflicts, as content file contains US/Los Angeles which is  not used even for english as default. That's why I asked (see comment #5) how the define the behaviour which is totally unclear. (I assume) that's why AJ asked for removing that info from content file. But yes, it might have a sence to have hard-written timezone default on CD. For that we must define the way when such default should be used (and override the default language-based one); btw, having such info in control rather than content file might be more practical.


If the original specifications doesn't have sense, we must change them. AJ, back to you.

I'm fine with removing it.

let's close this one,
and remove the TIMEZONE entry from content (post alpha4)