(I know, this was sent a long time ago, I just reviewed it)
On Mon, Aug 16, 2004 at 10:24:13PM +0300, Konstantinos Margaritis wrote:
So, should I remove the @euro extension from the locales?
Some users might already have them, it's best to consider them but also add
the sans '@euro'
Hi,
At 15 Aug 04 21:25:02 GMT,
Konstantinos Margaritis wrote:
http://people.debian.org/~markos/localization-config/
Main changes:
1) update-locale-config has 2 modes of operation:
pre-install and post-install. If -p command line option is used, it
calls the pre-install scripts,
2. xfree86-kbd gets kbdmap from language. But I think it
would be taken from d-i value or console-data. When I use US pc104
keyboard with Japanese locale, mismatch occurs.
I'm thinking of reading the values from console-data, it should not be
very difficult, but there are some
On 18 2004 09:20, Christian Perrier wrote:
It would be far better. I'm pretty sure that the message I
forwarded to my fellow french colleagues will trigger answer like
why doesn't he use the settings from console-data.
because there is no 1-1 mapping unfortunately, as i said in my
previous
Quoting Petter Reinholdtsen ([EMAIL PROTECTED]):
As far as I know, nl_NL is using the EURO, and need to use a charset
capable of representing the currency symbol. ISO-8859-1 is not able
to represent the EURO symbol, so these countries need to use a locale
with a different charset.
Dutch
[Christian Perrier]
What you're saying here indeed, is that the nl_NL as well as fr_FR and
so on locales are indeed inconsistent and should *never* be used
Not quite, but almost. The fr_FR listing in SUPPORTED should not be
used, as it uses the ISO-8859-1 charset. But it can not be
On 17 2004 09:14, Christian Perrier wrote:
All this goes further: why do we keep these locales if they are
not consistent?
Why don't we just use UTF-8? I've been using for Greek for more than a
year and it's been much easier (and Greek is a difficult case
anyway). And it solves all these
[Konstantinos Margaritis]
Why don't we just use UTF-8? I've been using for Greek for more than a
year and it's been much easier (and Greek is a difficult case
anyway). And it solves all these silly problems of @euro and weird
encodings. Not to mention it's more universal.
Ah, to boldly go
On 17 2004 06:47, Kenshi Muto wrote:
Hi,
Hi Kenshi,
That's interesting. Good job, Konstantinos.
Thanks though the great work was already done by the Skolelinux
guys :-)
I tested this in Japanese.
1. update-locale-config uses ja_JP, but Japanese locale has
always encoding name also.
On 17 2004 23:21, Petter Reinholdtsen wrote:
[Konstantinos Margaritis]
Why don't we just use UTF-8? I've been using for Greek for more
than a year and it's been much easier (and Greek is a difficult
case anyway). And it solves all these silly problems of @euro and
weird encodings. Not
* Petter Reinholdtsen [2004-08-17 22:21:44+0200]
[Konstantinos Margaritis]
Why don't we just use UTF-8? I've been using for Greek for more than a
year and it's been much easier (and Greek is a difficult case
anyway). And it solves all these silly problems of @euro and weird
encodings.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 17 August 2004 22:52, Konstantinos Margaritis wrote:
1. update-locale-config uses ja_JP, but Japanese locale has
always encoding name also. ja_JP.eucJP (this is default locale
for Japanese, and d-i creates this) or ja_JP.UTF-8 (UTF-8,
[Frans Pop]
Hmmm. Shouldn't the locale be ja_JP.EUC-JP?
That's the value that's in the languagelist for d-i.
At least EUC-JP is the name of the charset in glibc. The other names
are aliases.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Quoting Petter Reinholdtsen ([EMAIL PROTECTED]):
[Christian Perrier]
Weprobably now have to think how we could use it during a complete
system install.
My first idea is adding the package to each language task. Maybe
should we try first with French and Greek?
What about installing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 15 August 2004 23:25, Konstantinos Margaritis wrote:
4) Please, please check the configuration values for each package
for your locale entry.
I have taken a quick look at the scripts for nl_NL and I have a couple of
questions/comments.
On 16 2004 13:06, Frans Pop wrote:
- The test is for [EMAIL PROTECTED]
However, d-i currently does not (yet) set the locale to
[EMAIL PROTECTED], but to nl_NL. Do the tests still work in that case?
I think the same goes for other euro countries.
Hm, i copied the values from the former
Quoting Konstantinos Margaritis ([EMAIL PROTECTED]):
technique to disregard it... Though, to be frank, I'm confused as to
which countries should/are using the @euro extension. Shouldn't every
Currently, none..:-)
Just try a diff between /usr/share/i18n/locales/fr_FR and
On 16 2004 14:47, Christian Perrier wrote:
These two locales are here because one most often uses the
ISO-8859-1 charset and the other one used ISO-8859-15.
Ok, this one i knew so far.
Keeping these locales is indeed only a matter of backward
compatibility...and I'm even not sure this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 16 August 2004 21:24, Konstantinos Margaritis wrote:
On 16 2004 14:47, Christian Perrier wrote:
Keeping these locales is indeed only a matter of backward
compatibility...and I'm even not sure this makes sense.
Ok, now I'm confused,
[Frans Pop]
The only problem is that I've not yet found/seen/heard anywhere what
the function is of the pointer in locales to a specific charset
(i.e. where this is actually used and what goes wrong if you point
to the wrong charset).
As far as I know, nl_NL is using the EURO, and need to use
Hi,
At 15 Aug 04 21:25:02 GMT,
Konstantinos Margaritis wrote:
I have just uploaded to ftp-master the localization-config package,
which is an slightly redesigned version of locale-config-skolelinux,
so that it is able to work with sarge as well as woody (and of course
future releases).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I have just uploaded to ftp-master the localization-config package,
which is an slightly redesigned version of locale-config-skolelinux,
so that it is able to work with sarge as well as woody (and of course
future releases).
For those
Quoting Konstantinos Margaritis ([EMAIL PROTECTED]):
I have just uploaded to ftp-master the localization-config package,
which is an slightly redesigned version of locale-config-skolelinux,
so that it is able to work with sarge as well as woody (and of course
future releases).
[Christian Perrier]
Weprobably now have to think how we could use it during a complete
system install.
My first idea is adding the package to each language task. Maybe
should we try first with French and Greek?
What about installing it from languagechooser, and add base-config
fragments
24 matches
Mail list logo
