public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] bmp_logo: Check return value of fread()
Date: Tue, 28 Apr 2009 13:15:52 -0400	[thread overview]
Message-ID: <200904281315.55471.vapier@gentoo.org> (raw)
In-Reply-To: <m2ocugg13b.fsf@ohwell.denx.de>

On Tuesday 28 April 2009 13:06:00 Detlev Zundel wrote:
> > On Tuesday 28 April 2009 05:11:01 Detlev Zundel wrote:
> >> >> The copies cc-ed to myself come through just fine as utf-8 fwiw. 
> >> >> Does that imply the denx.de servers convert unicode messages to
> >> >> base64?
> >> >
> >> > This is in the headers of your message:
> >> >
> >> > 	Content-Type: text/plain; charset="utf-8"
> >> > 	Content-Transfer-Encoding: base64
> >> >
> >> > I don't think anything converted anything. It arrived as you sent it.
> >> >
> >> > You just don't see it.
> >> >
> >> > The problem for me is that I cannot use standard tools (like grep) on
> >> > such messages.
> >>
> >> Isn't it possible that you un-base64 such mails locally in your mail
> >> system?  In the long run I'd really like to be able to handle Unicode in
> >> U-Boot (sources) and thus also on the mailing list.
> >>
> >> It is the 2000s after all with people from all over the world
> >> contributing to U-Boot and we're limiting ourselves to the english
> >> typographic letters :(
> >
> > i dont think we want localized comments/output without an english
> > equivalent. i.e. if someone proposed an optional gettext() kind of thing
> > so the output of u-boot were localized, that may make sense.
>
> Note that I explicitely hinted at the source code.
>
> > mixing language comments makes it kind of hard for people to
> > coordinate/review things as then they'd be required to know multiple
> > languages.  atm, english is the only thing required (well, and coding
> > ability of course).
>
> I wasn't even thinking about language comments but simply names
> especially in git-commit messages.

i have no problem with localized names.  i do have a problem with localized 
comments and source code.

> Obviously I'm lucky that I don't have an umlaut in my name, but if I
> had, what would I do?

currently, like every other person with an umlaut, you use an "e".  ? -> oe.

> Resort to latin-1?

presumably you mean ISO 8859-1, and in that case, that character set is the 
same as in unicode (it was designed that way).

> What about French, Russian, etc. developers who want to see their "real"
> name in the logs?

get a new name !
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090428/214c5af3/attachment-0001.pgp 

  reply	other threads:[~2009-04-28 17:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 20:59 [U-Boot] [PATCH] bmp_logo: Check return value of fread() Peter Tyser
2009-04-27 23:18 ` Wolfgang Denk
2009-04-27 23:41   ` Mike Frysinger
2009-04-27 23:53     ` Peter Tyser
2009-04-28  0:01       ` Mike Frysinger
2009-04-28  5:21       ` Wolfgang Denk
2009-04-28  9:11         ` Detlev Zundel
2009-04-28 12:58           ` Mike Frysinger
2009-04-28 17:06             ` Detlev Zundel
2009-04-28 17:15               ` Mike Frysinger [this message]
2009-04-30 14:00                 ` Detlev Zundel
2009-04-30 15:43                   ` Mike Frysinger
2009-04-28 15:06         ` Peter Tyser
2009-04-28 15:49           ` Mike Frysinger
2009-04-28 15:57             ` Peter Tyser
2009-04-28 17:03               ` Mike Frysinger
2009-04-28 17:22           ` Mike Frysinger
2009-04-28 18:01             ` Peter Tyser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200904281315.55471.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox