<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Pedro,<br>
<br>
2012.01.23 13:07, Pedro Lino rašė:<br>
<blockquote
cite="mid:CAPrkgod5Swga_m9RMagE8uJciGo1R5puHetojVpHF6V1xYkyXw@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
<br>
</div>
All we should need is localised versions of key names like
Ctrl, Del,<br>
Ins (that are on almost every keyboard [1], but whose names
can<br>
change) and global versions of key names for<br>
alphanumeric/script-specific keys (which might not be on every<br>
keyboard, but whose names are the same internationally).<br>
So, looking at the code, we'd need to just move the keyboard
language<br>
specific data to the specific locales. This also seems a lot
more<br>
scalable than for every localiser having to ask a developer to
add<br>
their native keys into this code.<br>
</blockquote>
</div>
<br>
That would be too simple. See my example in the previous email.<br>
You would need to match the keys for EACH keyboard model,
regardless of Locale.<br>
<br>
This is particularly true for laptops (at least in Portugal...).
All laptops sold in Portugal have a Portuguese layout but the
Special keys (like Ctrl, Alt, Insert) have the English text.
Obviously manufacturers do this to save on producing specific
keys. So Locale doesn't solve the problem.<br>
</blockquote>
<br>
I think you'd just have to choose which label to use. Correctly
matching key names with the keyboard model is hardly impossible. I
would say you'd just have to choose whether to use Inserir or
Insert, and stick to that choice. Which strings you would choose
would be completely up to you, but you could of course take
popularity and other factors into account.<br>
<br>
Rimas<br>
<br>
</body>
</html>