From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Fte-devel] unicode support
Date: Tue, 21 Feb 2006 00:26:22 +0200 [thread overview]
Message-ID: <43FA420E.4000400@nic.fi> (raw)
In-Reply-To: <878xs6z1hd.fsf@xs4all.nl>
Marco Gerards wrote:
> Vesa Jääskeläinen <chaac@nic.fi> writes:
>
>> Timo Sirainen wrote:
>
> [...]
>
>>> I don't think it's such a good idea to start moving to C++ strings or
>>> wxWindows or any of that yet. Those would be pretty huge changes and I
>>> fear they would just never get finished.
>
> [...]
>
>> The problem here is that you can't change only one component, you have
>> to change them all if you want to test it out. So braking it to smaller
>> components was my idea on previous mails. But if you are also willing to
>> work on this it would be nice. I can manage the Win32 specific console
>> code, but we need people for other areas. And that UTF-8 is not the only
>> target formatting we need to think about.
>
> Ehm, I assume you posted this on the wrong list? Or is there anything
> relevant for us in this email?
umh. no :) Sorry.
prev parent reply other threads:[~2006-02-20 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1140362299.14276.188.camel@hurina>
2006-02-19 21:05 ` [Fte-devel] unicode support Vesa Jääskeläinen
2006-02-20 11:57 ` Marco Gerards
2006-02-20 22:26 ` Vesa Jääskeläinen [this message]
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=43FA420E.4000400@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.