From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Does plain pc console support UNICODE?
Date: Sun, 20 Jan 2013 23:40:15 +0100 [thread overview]
Message-ID: <50FC724F.1060602@gmail.com> (raw)
In-Reply-To: <1349370553.2182.9.camel@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On 04.10.2012 19:09, Andrey Borzenkov wrote:
> I have default language Russian. When testing patch I switched from
> gfxterm to plain console and got '????' instead of grub messages. Is it
> supposed to work at all? If not, does it make sense to temporary reset
> language when we switch to terminal that is known to not support
> UNICODE?
>
Normal BIOS console supports only CP437. The fix for this would go through:
1) Possible use of vga_text instead of BIOS services and enhance it with
font-loading code to dynamically load characters we need. But this is
already more than just a simple console and requires to load e.g.
unifont. Currently BIOS services and vga_text are used for their
simplicity and compactness. Perhaps vga_text would need to be split to
vga_text and vga_text_font the latter being a separate module and
vga_text calling vga_text_font only if it's loaded.
2) Another possibility is to translate the unrepresentable characters to
their nearest ASCII equivalent. The problem is that this is somewhat
language-dependent. E.g. a German-speaking person would replace ö with
oe but a Finnish would probably just drop the diaresis.
> -andrey
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2013-01-20 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 17:09 Does plain pc console support UNICODE? Andrey Borzenkov
2013-01-20 22:40 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=50FC724F.1060602@gmail.com \
--to=phcoder@gmail.com \
--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.