Mailinglist Archive: opensuse (4570 mails)
| < Previous | Next > |
Re: [SLE] OOo 2_0 enters dates as MM/DD/YY violating global KDE and YaST settings
- From: "Carlos E. R." <robin1.listas@xxxxxxxxxx>
- Date: Mon, 28 Nov 2005 13:35:50 +0000 (UTC)
- Message-id: <Pine.LNX.4.61.0511281423440.15924@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Monday 2005-11-28 at 07:26 +0530, Shriramana Sharma wrote:
> > > KDE Control Center > Regional & Accessibility > Country/Region & Language
> > > Short date format: DD-MM-YYYY
> >
> > That does not affect OOo, I think.
>
> Why should it not? I agree with John, that if it's set here, it should be
> global.
Because OOo reads the "locale" environment variables instead. Notice that
there are more than one "desktop": there is gnome, there is fwmn... each
one with its own settings.
> > What does the command "locale" say? Mine says:
> >
> > en_US.UTF-8
> >
> > and if I leave OOo at "default" the same date as above shows as
> > "11/26/05", ie, US locale.
>
> LC_TIME="en_US.UTF-8"
>
> Now why is this? KDE Control Center has Country or Region pointing to India
> with all the previews at the bottom in the appropriate Indian format.
Yes, probably kde should alter the locale environment variables, but it
doesn't, it seems.
> > Therefore, either correct your system/user locale (it can be different for
> > each user, mind!), or simply tell OOo what is the exact "locale" you want.
>
> My point was, when I set OOo to "default" locale and I specify the active
> locale to be India, then why does not OOo behave as such? I will check this
> in Windows, and if same problem there too (or even if not) I will report it
> as an OOo issue.
I think it is rather a kde issue. It would be interesting to know what the
OOo developers think and why they did it that way: I'm sure they have
thought about it a lot.
In windows, I dunno.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD4DBQFDiwajtTMYHG2NR9URAlJMAJdloLqByJ4g4umo1dxzUxIMIsUEAJ4jmnl6
IiPJemzdBP49p0UVp0MI/A==
=qmpT
-----END PGP SIGNATURE-----
Hash: SHA1
The Monday 2005-11-28 at 07:26 +0530, Shriramana Sharma wrote:
> > > KDE Control Center > Regional & Accessibility > Country/Region & Language
> > > Short date format: DD-MM-YYYY
> >
> > That does not affect OOo, I think.
>
> Why should it not? I agree with John, that if it's set here, it should be
> global.
Because OOo reads the "locale" environment variables instead. Notice that
there are more than one "desktop": there is gnome, there is fwmn... each
one with its own settings.
> > What does the command "locale" say? Mine says:
> >
> > en_US.UTF-8
> >
> > and if I leave OOo at "default" the same date as above shows as
> > "11/26/05", ie, US locale.
>
> LC_TIME="en_US.UTF-8"
>
> Now why is this? KDE Control Center has Country or Region pointing to India
> with all the previews at the bottom in the appropriate Indian format.
Yes, probably kde should alter the locale environment variables, but it
doesn't, it seems.
> > Therefore, either correct your system/user locale (it can be different for
> > each user, mind!), or simply tell OOo what is the exact "locale" you want.
>
> My point was, when I set OOo to "default" locale and I specify the active
> locale to be India, then why does not OOo behave as such? I will check this
> in Windows, and if same problem there too (or even if not) I will report it
> as an OOo issue.
I think it is rather a kde issue. It would be interesting to know what the
OOo developers think and why they did it that way: I'm sure they have
thought about it a lot.
In windows, I dunno.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD4DBQFDiwajtTMYHG2NR9URAlJMAJdloLqByJ4g4umo1dxzUxIMIsUEAJ4jmnl6
IiPJemzdBP49p0UVp0MI/A==
=qmpT
-----END PGP SIGNATURE-----
| < Previous | Next > |