Quoting Ognyan Kulev ([EMAIL PROTECTED]):
Anton Zinoviev wrote:
The entry for Bulgarian in languagelist should be taken either from
version 1.32 or 1.30 but not 1.31.
1.32 (with kbd=) is preferred. And there is no problem to use it
without CP1251 support in termwrap.
So, even if
Christian Perrier wrote:
So, even if base-config is not modified, having the most recent
changes in languagechooser does not harm ?
It doesn't harm all cyrillic languages except Russian. The problem is
that sarge termwrap requires console-cyrillic when KOI8-R terminal is
wanted. Other cyrillic
Quoting Ognyan Kulev ([EMAIL PROTECTED]):
Christian Perrier wrote:
So, even if base-config is not modified, having the most recent
changes in languagechooser does not harm ?
It doesn't harm all cyrillic languages except Russian. The problem is
that sarge termwrap requires console-cyrillic
Christian Perrier wrote:
This means that I can use languagelist only if I put the following
entry back in it:
Russian;ru;ru_RU.KOI8-R;ru;;ru_RU:ru:en_GB:en;cyr=uni,16,koi8-r,ru_ms(ctrl_shift_toggle)
Correct?
I think yes.
The important thing is console-cyrillic to be installed. One of the
ways is
Quoting Ognyan Kulev ([EMAIL PROTECTED]):
Christian Perrier wrote:
This means that I can use languagelist only if I put the following
entry back in it:
Russian;ru;ru_RU.KOI8-R;ru;;ru_RU:ru:en_GB:en;cyr=uni,16,koi8-r,ru_ms(ctrl_shift_toggle)
Correct?
I think yes.
The important thing
Quoting Joey Hess ([EMAIL PROTECTED]):
Ognyan Kulev wrote:
I guess this applies to Bulgarian's CP1251 too. Now I see that last
changelog entry is for unstable, not UNRELEASED.
It is acceptable for Bulgarian language to revert the CP1251 support in
termwrap. Then jfbterm will be used.
Nikolai Prokoschenko wrote:
On Tue, Sep 14, 2004 at 01:46:11PM -0400, Joey Hess wrote:
Fixing the changelog would be a good first step.
Done.
Please remove the old KOI8-R code from termwrap. Currently there are
two KOI8-R handlers in case $ENCODING.
Regards,
ogi
--
To UNSUBSCRIBE, email to
On Wed, Sep 15, 2004 at 06:51:54AM +0200, Christian Perrier wrote:
Joey, I'm not really safe at creating a branch with SVN. Would you
mind doing it for me by using the tagged 1.31 version (I properly
tagged it before releasing)? Or if you prefer, just tell me what
exactly must be done for
On Wed, Sep 15, 2004 at 02:26:04PM +0300, Ognyan Kulev wrote:
Fixing the changelog would be a good first step.
Done.
Please remove the old KOI8-R code from termwrap. Currently there are
two KOI8-R handlers in case $ENCODING.
Ooops. Didn't see that one. Removed committed.
--
Nikolai
Anton Zinoviev wrote:
The entry for Bulgarian in languagelist should be taken either from
version 1.32 or 1.30 but not 1.31.
1.32 (with kbd=) is preferred. And there is no problem to use it
without CP1251 support in termwrap.
Regards,
ogi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Nikolai Prokoschenko wrote:
On Mon, Sep 13, 2004 at 06:07:15PM +0300, Eugeniy Meshcheryakov wrote:
If it's fine for Ukrainian, it should be good enough for Russian.
Committing patch. Hope it works, I'm not a console user... :(
If so you should also remove code that installs
On Tue, Sep 14, 2004 at 12:05:02PM -0400, Joey Hess wrote:
Done. I'm committing the changes to languagechooser and base-config right
now, could someone please check that they don't break stuff?
[bunch of mistakes]
Oh-oh. It couldn't be so easy.
I'm sorry, this mess was absolutely
Nikolai Prokoschenko wrote:
[bunch of mistakes]
Oh-oh. It couldn't be so easy.
I'm sorry, this mess was absolutely unintended. What should I do now?
Should I try to remove the changes?
To the point of testing: I've configured console-tools on my machine using
the setup I committed and
Joey Hess wrote:
By committing changes of this sort to base-config and languagechooser at
this point *without testing them*, you run the risk of getting a nice
errata item for your language for the final sarge release that says
does not work, pick another language. It's stupid, don't do it.
Also,
Ognyan Kulev wrote:
I guess this applies to Bulgarian's CP1251 too. Now I see that last
changelog entry is for unstable, not UNRELEASED.
It is acceptable for Bulgarian language to revert the CP1251 support in
termwrap. Then jfbterm will be used.
That change went in before base-config 2.45
On Tue, Sep 14, 2004 at 01:46:11PM -0400, Joey Hess wrote:
I'm sorry, this mess was absolutely unintended. What should I do now?
Should I try to remove the changes?
Fixing the changelog would be a good first step.
Done.
Then if you can explain to me why you need to make this change at
Christian Perrier wrote:
If the same is needed for Bulgarian, then I leave the decision to
Anton and Ognyan.
Fine by me. Updated patch is attached.
Regards,
ogi
Index: languagelist
===
--- languagelist (revision 21512)
+++
Ognyan Kulev :
Christian Perrier wrote:
If the same is needed for Bulgarian, then I leave the decision to
Anton and Ognyan.
Fine by me. Updated patch is attached.
I commited this patch to svn, but I do not close this bug because
console-cyrillic still used for Serbian and Russian and
Quoting Eugeniy Meshcheryakov ([EMAIL PROTECTED]):
Ognyan Kulev :
Christian Perrier wrote:
If the same is needed for Bulgarian, then I leave the decision to
Anton and Ognyan.
Fine by me. Updated patch is attached.
I commited this patch to svn, but I do not close this bug
Christian Perrier :
For Serbian, go ahead..the translation is still in very early
stages (indeed, the translator did not answer much of my mails).
I do not know what font to use for Sebian. ruscii_8x16 dose not contain
all letters needed for Serbian.
--
Eugeniy Meshcheryakov
Kyiv
On Mon, Sep 13, 2004 at 11:54:06AM +0200, Christian Perrier wrote:
For Russian, we, for sure, need some input by Nikolai
NIKOLA, DAVA!!:-)
If it's fine for Ukrainian, it should be good enough for Russian.
Committing patch. Hope it works, I'm not a console user... :(
--
Nikolai
Nikolai Prokoschenko :
On Mon, Sep 13, 2004 at 11:54:06AM +0200, Christian Perrier wrote:
For Russian, we, for sure, need some input by Nikolai
NIKOLA, DAVA!! :-)
If it's fine for Ukrainian, it should be good enough for Russian.
Committing patch. Hope it works, I'm not a console
On Mon, Sep 13, 2004 at 01:24:00PM +0300, Eugeniy Meshcheryakov wrote:
I do not know what font to use for Sebian. ruscii_8x16 dose not contain
all letters needed for Serbian.
For Serbian: kbd=iso05.f16(utf8)
(I commited this change.)
Anton Zinoviev
--
To UNSUBSCRIBE, email to [EMAIL
Eugeniy Meshcheryakov wrote:
If so you should also remove code that installs console-cyrillic and
console-terminus from languagechooser and make termwrap use ruscii_8x16
font instead unavailable console-cyrillic.
If such change is made in termwrap, I would recommend to use CP1251
support as
On Mon, Sep 13, 2004 at 06:07:15PM +0300, Eugeniy Meshcheryakov wrote:
If it's fine for Ukrainian, it should be good enough for Russian.
Committing patch. Hope it works, I'm not a console user... :(
If so you should also remove code that installs console-cyrillic and
console-terminus from
On Mon, Sep 13, 2004 at 06:39:04PM +0300, Ognyan Kulev wrote:
If so you should also remove code that installs console-cyrillic and
console-terminus from languagechooser and make termwrap use ruscii_8x16
font instead unavailable console-cyrillic.
If such change is made in termwrap, I would
Nikolai Prokoschenko wrote:
Done. I'm committing the changes to languagechooser and base-config right
now, could someone please check that they don't break stuff?
Seems fine, but you forgot the debian/changelog entry.
Regards,
ogi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Ognyan Kulev wrote:
Seems fine, but you forgot the debian/changelog entry.
debian/changelog of base-config should also be updated because of the
termwrap change.
Regards,
ogi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
tags 260227 + patch
thanks
I propose to not use console-cyrillic for Ukrainian in order to fix
this bug. User will be able to configure console-cyrillic in second
stage. Patch also allows user to use non-cyrillic console.
Patch if for Ukrainian only but the same font may be used for Russian
(acm
On Sun, Sep 12, 2004 at 04:57:27PM +0300, Eugeniy Meshcheryakov wrote:
I propose to not use console-cyrillic for Ukrainian in order to fix
this bug. User will be able to configure console-cyrillic in second
stage. Patch also allows user to use non-cyrillic console.
:-) I like this decision.
Quoting Anton Zinoviev ([EMAIL PROTECTED]):
On Sun, Sep 12, 2004 at 04:57:27PM +0300, Eugeniy Meshcheryakov wrote:
I propose to not use console-cyrillic for Ukrainian in order to fix
this bug. User will be able to configure console-cyrillic in second
stage. Patch also allows user to use
31 matches
Mail list logo
