Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Re: Piping stderr?
- Date: Tue, 25 Jun 2002 13:51:07 +0900
- From: Jiro SEKIBA <jir@example.com>
- Subject: Re: [tlug] Re: Piping stderr?
- References: <3D109EC0.4070703@example.com><87n0trz38q.fsf@example.com><s3t3cvj6oad.fsf@example.com><87r8j1w8ol.fsf@example.com><877kktb463.wl@example.com><87u1nxuguj.fsf@example.com><87n0tlmn5r.wl@example.com><87bsa1nsvr.fsf@example.com><87vg895g7k.wl@example.com><871yaxnjei.fsf@example.com>
- User-agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3(Unebigoryōmae) APEL/10.3 Emacs/20.7(i386-debian-linux-gnu) MULE/4.1 (AOI)
At 24 Jun 2002 17:57:41 +0900, Stephen J. Turnbull <stephen@example.com> wrote: >> ??? What do you mean it, you meant localozed hard coded > > As far as I know, that's how Bash does it (at least, libreadline docs > don't say anything about I18N). Aha, I see now. We had a misconception :-). The newest version of bash(2.05a) does not have multibyte capability, yet. And... >> patch? Then you are absolutely right. If not, I don't >> understand what you mean exactly. If you think of I18N, it >> includes multibyte capability. > > But that's not what Mike was talking about AFAIK. Yes, Mike has > worked hard for I18N for years at SuSE, and definitely is on the side > of the angels in this. But my understanding of the "multibyte patch" > he was talking about is the kind of thing that we've seen in software > like nemacs and j{sed,grep,gawk,perl,pine,...} for years, because > that's what's available in Bash and csh (again, AFAIK). Mike knows better than me, but SuSE includes bash applied i18n patch provided by li18nux. So I thought Mike meant it :-). >> I'd like to ask you that if I18N software is acceptable for >> you? Why/Why not? > > Mostly, yes. I need one M17N app, and XEmacs fills the bill. For the > rest, I18N is fine. But it needs to be built around a general > library. Good to here :-). Some people are UTF-8 believer and never accept CSI I18N concept ;-p. CSI I18N includes UTF-8 support, I must say. And yes, we need much better general library. > I'm sick of fighting with *terms and j-apps that don't quite do it > (and often break down quite badly outside of a Japanese/English > environment). Much better to stay inside of Mule and to use the > excellent and well-defined (if cumbersome) tools provided by glibc. O.K, now the time forget about j-apps, but please forget about UTF-8 apps as well, such are like uxterm... apps which accpet only UTF-8 are as same as j-apps, just a multibyte enhancement, I think.. -- Jiro SEKIBA | Web tools & AP Linux Competency Center, YSL, IBM Japan | email: jir@example.com, jir@example.com
- Follow-Ups:
- Re: [tlug] Re: Piping stderr?
- From: Stephen J. Turnbull
- References:
- [tlug] Piping stderr?
- From: Josh Glover
- Re: [tlug] Piping stderr?
- From: Stephen J. Turnbull
- [tlug] Re: Piping stderr?
- From: Mike Fabian
- [tlug] Re: Piping stderr?
- From: Stephen J. Turnbull
- Re: [tlug] Re: Piping stderr?
- From: Jiro SEKIBA
- Re: [tlug] Re: Piping stderr?
- From: Stephen J. Turnbull
- Re: [tlug] Re: Piping stderr?
- From: Jiro SEKIBA
- Re: [tlug] Re: Piping stderr?
- From: Stephen J. Turnbull
- Re: [tlug] Re: Piping stderr?
- From: Jiro SEKIBA
- Re: [tlug] Re: Piping stderr?
- From: Stephen J. Turnbull
Home | Main Index | Thread Index
- Prev by Date: Re: [Re: [tlug] CVS and Japanese files]
- Next by Date: RE: [tlug] Root - NO KDE
- Previous by thread: Re: [tlug] Re: Piping stderr?
- Next by thread: Re: [tlug] Re: Piping stderr?
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links