[vdr] Re: [PATCH] fix segfaults because of channels with umlauts

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

"Dr. Werner Fink" wrote:
> 
> On Mon, Jun 14, 2004 at 02:05:19PM +0200, Klaus Schmidinger wrote:
> > "Dr. Werner Fink" wrote:
> > > Please explain _why_ do you think so?  What is wrong
> > >
> > > on text like this one:
> > >
> > > Arabic اÙ?سÙ?اÙ? عÙ?ÙSÙfÙ?
> > > Greek (Î*λληνικά) Î?ειά ÏfαÏ,
> > > Hebrew ש×?Ö¸×?×*Ö¹×?
> > > Japanese (æ-¥æ?¬èª?) ã??ã,?ã?«ã?¡ã?¯, ｺï¾?ï¾?ï¾?ï¾S
> > > Chinese (中æ-?,æ?®é?sè¯?,æ±?语) ä½ å¥½
> > > Cantonese (ç²µèª?,廣æ?±è©±) æ-©æ?¨, ä½ å¥½
> > >
> > > ... no problem to read this within an UTF-8 locale ;^)
> > >
> > >         Werner
> >
> > Wow, I didn't know you speak that many languages.
> >
> > I for one need only German and English.
> > And I would say that for the majority of German Linux users
> > this applies as well. Those who need different languages
> > can easily enable UTF support - but why should those who
> > really don't need it suffer from that?
> 
> If I speak or not speak several languages is not the point.
> The point is that we've many customers around which can do
> this and _want_ todo so without knowledge of the internals
> of the needed settings. I for my person prefer German and
> English, nevertheless I know that there is no way around UTF-8 ;)
> 
> And one major problem is that it is impossible to distinguish
> between e.g. iso-8859-1, iso-8859-15, iso-8859-4, and iso-8859-5.
> The customer has to switch the encoding, fontset and locale
> by hand if the encoding isn't known by the system.  This problem
> is simply gone with full UTF-8 support.  And with the help of UTF-8
> also other languages not supported by the ISO 8859 but e.g.
> GB2312 or ISO 646 or ISO 2022 or ... without system knowledge for
> the maybe native or not native languages. And with UTF-8 it is
> very simple to support several languages in _one_ text ... e.g.
> sub titles within VDR with two languages let's say German and
> Czech ... even if you don't speak Czech ;^)

Well, to end this discussion (at least from my side): I will NOT use
UTF-8 - neither in VDR nor on my other systems. With VDR we had no
problem until SuSE 9.1 came up with UTF-8 as default - maybe this
rings a bell... ;-)

EOT

Klaus