From chouy at ematters.com.tw Thu Jun 7 10:09:46 2007 From: chouy at ematters.com.tw (Tina Chou) Date: Thu, 7 Jun 2007 18:09:46 +0800 Subject: [Fedora-i18n-list] Thunderbird language problem Message-ID: <20070607100844.M67117@ematters.com.tw> Hi, I have a question about thunderbird. Although the language I installed for FC5 is LANG=zh_TW.UTF-8, my thunderbird is in simplified Chinese. And since I saw the zh_TW version in http://www.mozilla.com/en-US/thunderbird/all.html, I wonder if yum is not correct or is missing something. Thanks! --------------------- Tina chouy at ematters.com.tw From cchance at redhat.com Fri Jun 8 00:47:23 2007 From: cchance at redhat.com (Caius Chance) Date: Fri, 08 Jun 2007 10:47:23 +1000 Subject: [Fedora-i18n-list] Re: [Tina] Thunderbird interface in Simplified Chinese on zh_TW locale. In-Reply-To: <20070607160024.9EE0473705@hormel.redhat.com> References: <20070607160024.9EE0473705@hormel.redhat.com> Message-ID: <4668A71B.5070708@redhat.com> Hi Tina, Thank you very much for your continue support on open source testing. I have tested and reproduced the problem as well, and I have submitted a bug for the maintainer to be followed up: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243225 I have CC'ed you in case if he/she needs any further information from you. You could keep track the progress by that bug. Appreciates for your kindly help and have a nice day. P.S. BTW I would recommend you to try the Fedora 7 for some new and cool features. Best Regards, Caius CAIUS CHANCE | CCHANCE AT REDHAT DOT COM X8116 | SW ENG | ENG-I18N | RED HAT APAC APAC DOT REDHAT DOT COM SLASH DISCLAIMER ===== Tina mentioned: Hi, I have a question about thunderbird. Although the language I installed for FC5 is LANG=zh_TW.UTF-8, my thunderbird is in simplified Chinese. And since I saw the zh_TW version in http://www.mozilla.com/en-US/thunderbird/all.html, I wonder if yum is not correct or is missing something. Thanks! --------------------- Tina chouy at ematters.com.tw From petersen at redhat.com Mon Jun 25 08:09:28 2007 From: petersen at redhat.com (Jens Petersen) Date: Mon, 25 Jun 2007 18:09:28 +1000 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting Message-ID: <467F7838.9080505@redhat.com> We are thinking that it would be a good to have a meeting of the Fedora I18n project to discuss various technical issues openly. Some of the things to discuss include: - installation package defaults - input method desktop defaults and configuration (xinput/im-chooser) - renaming of fonts-* to reflect upstream projects - adding a IM package group? If you are interested in joining this discussion please reply and let us know when you would prefer the meetings and also any potential agenda items. Obviously it is going to be hard to find a time that is good for everyone all the time so we might try alternating between morning and evening in East Asia to give people in other regions some chance to participate also. I would like to have the first meeting in #fedora-i18n on Freenode this week. Jens -- Jens Petersen Fedora and Red Hat I18n From nicolas.mailhot at laposte.net Mon Jun 25 08:36:35 2007 From: nicolas.mailhot at laposte.net (Nicolas Mailhot) Date: Mon, 25 Jun 2007 10:36:35 +0200 (CEST) Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <467F7838.9080505@redhat.com> References: <467F7838.9080505@redhat.com> Message-ID: <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> Le Lun 25 juin 2007 10:09, Jens Petersen a ?crit : > We are thinking that it would be a good to have a meeting of > the Fedora I18n project to discuss various technical issues openly. > > Some of the things to discuss include: > > - installation package defaults > - input method desktop defaults and configuration (xinput/im-chooser) > - renaming of fonts-* to reflect upstream projects > - adding a IM package group? I'd like to attend, but probably only could in the evening (western european time). I'd like the following topics discussed: + extented (multimedia) key Fedora target (wait-and-see, active Fedora push, to evdev or not to evdev?) + font policy/comps i18n group organisation -> some fonts bring support for scripts used by existing desktop locales, others for scripts associated to langages we don't have localisation for (tiffinagh, n'ko, inuktikut, tibetan?), others are purely decorative and no one will use them in real life by default, others are for historical scripts (dead languages, medieval variants, old greek, church scripts...). How all this stuff is supposed to be organised in comps? How will it appear in anaconda/yum guis? + what to do when upstream is dormant or end-user unfriendly? Where and how should user feedback be directed? Do we need a Fedora-level i18n technical hub? Do we have the resources for it? (hunspell dicts, xkb maps, console maps, abandonware fonts, etc) -- Nicolas Mailhot From ryo-dairiki at users.sourceforge.net Mon Jun 25 14:50:46 2007 From: ryo-dairiki at users.sourceforge.net (Ryo Dairiki) Date: Mon, 25 Jun 2007 23:50:46 +0900 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <467F7838.9080505@redhat.com> References: <467F7838.9080505@redhat.com> Message-ID: <467FD646.3030300@users.sourceforge.net> An HTML attachment was scrubbed... URL: From dimitris at glezos.com Mon Jun 25 21:37:32 2007 From: dimitris at glezos.com (Dimitris Glezos) Date: Mon, 25 Jun 2007 22:37:32 +0100 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <467FD646.3030300@users.sourceforge.net> References: <467F7838.9080505@redhat.com> <467FD646.3030300@users.sourceforge.net> Message-ID: <4680359C.9050407@glezos.com> O/H Ryo Dairiki ??????: > Jens Petersen wrote: >> We are thinking that it would be a good to have a meeting of >> the Fedora I18n project to discuss various technical issues openly. I'm interested in participating as well. > I would like to join this. > I have some topic to discuss there: > > + Localized official information for End Users > - Actually, there is a Japanese Fedora Community called "Fedora JP", > but this seems to be dying. > - End Users need Up-to-date official information in their own language. > - Translation of official documents is not enough, but language > specific information is also needed. Localization is handled by the Fedora Localization Project. The project has many teams handling transaltions and localization in general, many of which have their own website, mailing list etc. More info at: http://fedoraproject.org/wiki/L10N I believe that bringing the topics about translations, language-specific information, and local communities on the FLP mailing list will result in feedback from a lot of people having similar concerns. IMO, this would apply for most of the (very interesting) topics below. :-) > + Localized configurations, and language specific packages > - Font configuration for Java. > - Japanese specific tex sub packages. > - Language specific packages should be firstly reviewed by local > people. (Not directly sent to FE) > > + Translation infrastructure like bugzilla. > + Localized bugzilla > + Localization QA > [...] > >> If you are interested in joining this discussion please reply and let us >> know when you would prefer the meetings and also any potential agenda >> items. Obviously it is going to be hard to find a time that is good for >> everyone all the time so we might try alternating between morning and >> evening in East Asia to give people in other regions some chance to >> participate also. >> >> I would like to have the first meeting in #fedora-i18n on Freenode >> this week. Maybe we should do it in #fedora-meeting? See: http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel -d -- Dimitris Glezos Jabber ID: glezos at jabber.org, GPG: 0xA5A04C3B http://dimitris.glezos.com/ "He who gives up functionality for ease of use loses both and deserves neither." (Anonymous) -- From sankarshan at randomink.org Tue Jun 26 03:49:35 2007 From: sankarshan at randomink.org (Sankarshan Mukhopadhyay) Date: Tue, 26 Jun 2007 09:19:35 +0530 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <467F7838.9080505@redhat.com> References: <467F7838.9080505@redhat.com> Message-ID: Hi, On 6/25/07, Jens Petersen wrote: > We are thinking that it would be a good to have a meeting of > the Fedora I18n project to discuss various technical issues openly. I would like to join in. > Some of the things to discuss include: > > - installation package defaults I am specifically interested in this assuming that this is aimed at some kind of guideline formation/standardization. [snipped] > I would like to have the first meeting in #fedora-i18n on Freenode > this week. +1 Would be good to use timeanddate.com or something similar so that the confusions about TZs don't arise. :Sankarshan -- >From Untruth, lead me to the Truth, >From Darkness, Lead me towards the Light, >From Death, Lead me to Life Eternal From wtogami at redhat.com Tue Jun 26 16:53:51 2007 From: wtogami at redhat.com (Warren Togami) Date: Tue, 26 Jun 2007 12:53:51 -0400 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> References: <467F7838.9080505@redhat.com> <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> Message-ID: <4681449F.8060900@redhat.com> Nicolas Mailhot wrote: > Le Lun 25 juin 2007 10:09, Jens Petersen a ?crit : >> We are thinking that it would be a good to have a meeting of >> the Fedora I18n project to discuss various technical issues openly. >> >> Some of the things to discuss include: >> >> - installation package defaults >> - input method desktop defaults and configuration (xinput/im-chooser) >> - renaming of fonts-* to reflect upstream projects >> - adding a IM package group? > > I'd like to attend, but probably only could in the evening (western > european time). I'd like the following topics discussed: > > + extented (multimedia) key Fedora target (wait-and-see, active Fedora > push, to evdev or not to evdev?) > > + font policy/comps i18n group organisation -> some fonts bring > support for scripts used by existing desktop locales, others for > scripts associated to langages we don't have localisation for > (tiffinagh, n'ko, inuktikut, tibetan?), others are purely decorative > and no one will use them in real life by default, others are for > historical scripts (dead languages, medieval variants, old greek, > church scripts...). How all this stuff is supposed to be organised in > comps? How will it appear in anaconda/yum guis? These are legitimate issues, but we need to limit the scope of this meeting if we are going to tackle the highest priority problems before F8. Perhaps as a first step, we can map out all the problems and create a big picture overview. Then we can figure out interdependencies, prioritize, or escalate issues to other groups. I suspect the highest priority problems that i18n needs to focus on for F8 are Input Method related: installation/removal, launch defaults and configuration. If others can come up with solutions for the other problems in parallel that would be great of course. > > + what to do when upstream is dormant or end-user unfriendly? Where > and how should user feedback be directed? Do we need a Fedora-level > i18n technical hub? Do we have the resources for it? (hunspell dicts, > xkb maps, console maps, abandonware fonts, etc) > This is an issue that effects more than just i18n, perhaps FESCo should discuss and create general policy instead? Warren Togami wtogami at redhat.com From nicolas.mailhot at laposte.net Tue Jun 26 17:24:40 2007 From: nicolas.mailhot at laposte.net (Nicolas Mailhot) Date: Tue, 26 Jun 2007 19:24:40 +0200 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <4681449F.8060900@redhat.com> References: <467F7838.9080505@redhat.com> <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> <4681449F.8060900@redhat.com> Message-ID: <1182878680.14650.16.camel@rousalka.dyndns.org> Le mardi 26 juin 2007 ? 12:53 -0400, Warren Togami a ?crit : > Nicolas Mailhot wrote: > > Le Lun 25 juin 2007 10:09, Jens Petersen a ?crit : > >> We are thinking that it would be a good to have a meeting of > >> the Fedora I18n project to discuss various technical issues openly. > >> > >> Some of the things to discuss include: > >> > >> - installation package defaults > >> - input method desktop defaults and configuration (xinput/im-chooser) > >> - renaming of fonts-* to reflect upstream projects > >> - adding a IM package group? > > > > I'd like to attend, but probably only could in the evening (western > > european time). I'd like the following topics discussed: > > > > + extented (multimedia) key Fedora target (wait-and-see, active Fedora > > push, to evdev or not to evdev?) > > > > + font policy/comps i18n group organisation -> some fonts bring > > support for scripts used by existing desktop locales, others for > > scripts associated to langages we don't have localisation for > > (tiffinagh, n'ko, inuktikut, tibetan?), others are purely decorative > > and no one will use them in real life by default, others are for > > historical scripts (dead languages, medieval variants, old greek, > > church scripts...). How all this stuff is supposed to be organised in > > comps? How will it appear in anaconda/yum guis? > > These are legitimate issues, but we need to limit the scope of this > meeting if we are going to tackle the highest priority problems before F8. Well, I do i18n fonts, so I sort of need to know where I fit in :) and to evdev or not is linked to IM anyway. > > + what to do when upstream is dormant or end-user unfriendly? Where > > and how should user feedback be directed? Do we need a Fedora-level > > i18n technical hub? Do we have the resources for it? (hunspell dicts, > > xkb maps, console maps, abandonware fonts, etc) > > > > This is an issue that effects more than just i18n, perhaps FESCo should > discuss and create general policy instead? It's a general issue, but it's much worse for i18n. Good i18n absolutely requires locals to report problems, and the people most likely to do the best reports are also the most likely to be put of by the technical english interfaces technical testers use. Also some resources like fonts and dicts have pretty much the worst possible upstreams on the maintenance scale (having OO.o as dict source is a joke, OO.o does not have the resources to support dicts and some of them are not even bundled with OO.o due to licensing clashes) -- Nicolas Mailhot -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Ceci est une partie de message num?riquement sign?e URL: From wtogami at redhat.com Tue Jun 26 17:38:40 2007 From: wtogami at redhat.com (Warren Togami) Date: Tue, 26 Jun 2007 13:38:40 -0400 Subject: Volunteer Needed: fedora-i18n-list Admin Message-ID: <46814F20.3040602@redhat.com> Anyone here want to be a list admin for fedora-i18n-list? I would prefer to give list ownership to someone who is already a developer within the Fedora Project. When accepted you will become co-owner of this list along with Jens Petersen. Warren Togami wtogami at redhat.com From mayank.gnu at gmail.com Wed Jun 27 16:32:44 2007 From: mayank.gnu at gmail.com (=?UTF-8?Q?=E0=A4=AE=E0=A4=AF=E0=A4=82=E0=A4=95_?= =?UTF-8?Q?=E0=A4=9C=E0=A5=88=E0=A4=A8_(?= =?UTF-8?Q?makuchaku)?=) Date: Wed, 27 Jun 2007 22:02:44 +0530 Subject: Volunteer Needed: fedora-i18n-list Admin In-Reply-To: <46814F20.3040602@redhat.com> References: <46814F20.3040602@redhat.com> Message-ID: <22ce560a0706270932k776992e7x2ce9c4fa631d96ad@mail.gmail.com> Hi Warren, I would like to take up this responsibility. Having personally worked with Jens, it would be wonderfull to co-moderate fedora-i18n-list with him. Thanks, Makuchaku http://www.makuchaku.info/blog -- Replied from Nokia E61 -- On 6/26/07, Warren Togami wrote: > Anyone here want to be a list admin for fedora-i18n-list? > > I would prefer to give list ownership to someone who is already a > developer within the Fedora Project. When accepted you will become > co-owner of this list along with Jens Petersen. > > Warren Togami > wtogami at redhat.com > > -- > Fedora-i18n-list mailing list > Fedora-i18n-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-i18n-list > From petersen at redhat.com Thu Jun 28 06:22:02 2007 From: petersen at redhat.com (Jens Petersen) Date: Thu, 28 Jun 2007 16:22:02 +1000 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> References: <467F7838.9080505@redhat.com> <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> Message-ID: <4683538A.9030608@redhat.com> Nicolas Mailhot ????????: > I'd like to attend, Great! > but probably only could in the evening (western > european time). OK, that is a bit hard from Asia/Pacific where the Red Hat i18n team is located. Let's see how we can work out things as we move on. We will post logs anyway so you want also followup with comments by email of course. :) > + extented (multimedia) key Fedora target (wait-and-see, active Fedora > push, to evdev or not to evdev?) Not quite sure how this relates to i18n. Are you proposing to use it for international input or something? > + font policy/comps i18n group organisation -> some fonts bring > support for scripts used by existing desktop locales, others for > scripts associated to langages we don't have localisation for > (tiffinagh, n'ko, inuktikut, tibetan?), others are purely decorative > and no one will use them in real life by default, others are for > historical scripts (dead languages, medieval variants, old greek, > church scripts...). How all this stuff is supposed to be organised in > comps? How will it appear in anaconda/yum guis? Ok we can certainly talk about it at some point. Going on we need to put more effort into maintaining comps for i18n. I try to do what I can. > + what to do when upstream is dormant or end-user unfriendly? Where > and how should user feedback be directed? Do we need a Fedora-level > i18n technical hub? Do we have the resources for it? (hunspell dicts, > xkb maps, console maps, abandonware fonts, etc) Ok. Some of these may be case-by-case. Let's discuss when you can join. Jens -- Jens Petersen Internationalization From petersen at redhat.com Thu Jun 28 07:17:35 2007 From: petersen at redhat.com (Jens Petersen) Date: Thu, 28 Jun 2007 17:17:35 +1000 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <4680359C.9050407@glezos.com> References: <467F7838.9080505@redhat.com> <467FD646.3030300@users.sourceforge.net> <4680359C.9050407@glezos.com> Message-ID: <4683608F.9080005@redhat.com> Hi Dimitris Glezos, >>> I would like to have the first meeting in #fedora-i18n > > Maybe we should do it in #fedora-meeting? I would like to use #fedora-i18n initially to encourage more people to use that channel, but yes later it will probably be a good idea to do our meetings on the meeting channel. Jens From petersen at redhat.com Thu Jun 28 07:25:13 2007 From: petersen at redhat.com (Jens Petersen) Date: Thu, 28 Jun 2007 17:25:13 +1000 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: References: <467F7838.9080505@redhat.com> Message-ID: <46836259.8010805@redhat.com> Sankarshan Mukhopadhyay ????????: >> - installation package defaults This was more an indirect reference to whether for example scim should be installed by default or not in fedora 8 like it is in 7, but this has already been fixed in the development tree recently so it is less of an issue now but maybe still worth discussing. > I am specifically interested in this assuming that this is aimed at > some kind of guideline formation/standardization. We could also come to that - specifically for things like fonts: eg how much font/input method coverage do we want by default in Fedora, etc. Jens From nicolas.mailhot at laposte.net Thu Jun 28 07:37:49 2007 From: nicolas.mailhot at laposte.net (Nicolas Mailhot) Date: Thu, 28 Jun 2007 09:37:49 +0200 (CEST) Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <4683538A.9030608@redhat.com> References: <467F7838.9080505@redhat.com> <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> <4683538A.9030608@redhat.com> Message-ID: <1536.192.54.193.51.1183016269.squirrel@rousalka.dyndns.org> Le Jeu 28 juin 2007 08:22, Jens Petersen a ?crit : > Nicolas Mailhot ????????: >> I'd like to attend, > > Great! > >> but probably only could in the evening (western >> european time). > > OK, that is a bit hard from Asia/Pacific where > the Red Hat i18n team is located. I know, my people are in Australia right now. > We will post logs anyway so you want also followup > with comments by email of course. :) Ok. >> + extented (multimedia) key Fedora target (wait-and-see, active >> Fedora >> push, to evdev or not to evdev?) > > Not quite sure how this relates to i18n. Are you proposing > to use it for international input or something? Fixing Fedora input needs switching to evdev someday. It's very likely this switch will unearth bugs in the handling of international keyboards, as most evdev testers probably only use western keyboards (probably not too difficult to fix stuff, but i18n should be ready for the switch) >> + what to do when upstream is dormant or end-user unfriendly? Where >> and how should user feedback be directed? Do we need a Fedora-level >> i18n technical hub? Do we have the resources for it? (hunspell >> dicts, >> xkb maps, console maps, abandonware fonts, etc) > > Ok. Some of these may be case-by-case. Let's discuss when you can > join. Unfortunately while some cases are extremes you have a general pattern of i18n not getting sufficient feedback because of langage barriers. At best you have translation teams but i18n is far more than translation. People (esp. people new to Linux) just assume things are broken by default and there's nothing to be done (You learn there are problems when you go to local forums and someone rants about Fedora i18n problems, but you never get the problem reports directly) That's why other distros have i18n hubs with a strong presence and activity. It's dishearting to notice time and time again other distros manage to get problem reports for stuff which was pushed in Fedora months before without anyone reacting. -- Nicolas Mailhot From petersen at redhat.com Thu Jun 28 08:30:07 2007 From: petersen at redhat.com (Jens Petersen) Date: Thu, 28 Jun 2007 18:30:07 +1000 Subject: [announcement] Fedora I18n IRC meeting Message-ID: <4683718F.9060204@redhat.com> We would have a first open meeting of the Fedora I18n Project on IRC next week: Place: #fedora-i18n on Freenode Time: 2007-07-02 06:00 UTC [1] Agenda: - desktop input method install defaults and configuration - i18n comps - renaming of fonts-* to reflect upstream projects - plans for next meeting - open discussion Jens [1] $ date -d "2007-07-02 06:00 UTC" or http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=2&year=2007&hour=6&min=0 Probably we will do the next meeting at a different time which will make it easier for people in different timezones to join. From petersen at redhat.com Thu Jun 28 08:42:31 2007 From: petersen at redhat.com (Jens Petersen) Date: Thu, 28 Jun 2007 18:42:31 +1000 Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <1536.192.54.193.51.1183016269.squirrel@rousalka.dyndns.org> References: <467F7838.9080505@redhat.com> <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> <4683538A.9030608@redhat.com> <1536.192.54.193.51.1183016269.squirrel@rousalka.dyndns.org> Message-ID: <46837477.6070906@redhat.com> Nicolas Mailhot ????????: >>> + extented (multimedia) key Fedora target (wait-and-see, active >>> Fedora push, to evdev or not to evdev?) >> Not quite sure how this relates to i18n. Are you proposing >> to use it for international input or something? > > Fixing Fedora input needs switching to evdev someday. It's very likely > this switch will unearth bugs in the handling of international > keyboards, as most evdev testers probably only use western keyboards > (probably not too difficult to fix stuff, but i18n should be ready for > the switch) Ok, I would like to know more - some pointers would be useful. Is it closer to kernel kbd handling? > That's why other distros have i18n hubs with a strong presence and > activity. It's dishearting to notice time and time again other distros > manage to get problem reports for stuff which was pushed in Fedora > months before without anyone reacting. I hear what you are saying and agree completely. I think we have been aware of the problem but have not had the resources to address them yet. We certainly have some things we need to learn from them. I think this may be something that needs to be pushed higher up to FESCO or the Board, but together with L10N project I think we can help to lay the groundwork for that by providing good input, examples and ideas. Jens From nicolas.mailhot at laposte.net Thu Jun 28 08:58:05 2007 From: nicolas.mailhot at laposte.net (Nicolas Mailhot) Date: Thu, 28 Jun 2007 10:58:05 +0200 (CEST) Subject: [Fedora-i18n-list] Call for a Fedora I18n meeting In-Reply-To: <46837477.6070906@redhat.com> References: <467F7838.9080505@redhat.com> <17240.192.54.193.51.1182760595.squirrel@rousalka.dyndns.org> <4683538A.9030608@redhat.com> <1536.192.54.193.51.1183016269.squirrel@rousalka.dyndns.org> <46837477.6070906@redhat.com> Message-ID: <29975.192.54.193.52.1183021085.squirrel@rousalka.dyndns.org> Le Jeu 28 juin 2007 10:42, Jens Petersen a ?crit : > Nicolas Mailhot ????????: >>>> + extented (multimedia) key Fedora target (wait-and-see, active >>>> Fedora push, to evdev or not to evdev?) >>> Not quite sure how this relates to i18n. Are you proposing >>> to use it for international input or something? >> >> Fixing Fedora input needs switching to evdev someday. It's very >> likely >> this switch will unearth bugs in the handling of international >> keyboards, as most evdev testers probably only use western keyboards >> (probably not too difficult to fix stuff, but i18n should be ready >> for >> the switch) > > Ok, I would like to know more - some pointers would be useful. > Is it closer to kernel kbd handling? evdev cuts out some translation layers between X and the kernel. So you're less likely to have different bugsets in the kernel and X, and switching to evdev will just kill lots of legacy limitations/bugs. However evdev has not got the test coverage of the currend X kbd driver, so bugs can still be lurking. -- Nicolas Mailhot