[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [babel-translators] "Non-translatable" strings with keyboard accelerators
|
- From: Hendrik Maryns <hamaryns@xxxxxxxxxxxxxx>
- Date: Wed, 10 Jun 2009 13:42:59 +0200
- Delivered-to: babel-translators@eclipse.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=YsJMYapFxaSWVMqOj+3joJpJ6JzKR8FwStN9oS2MvBY=; b=SGTzru07tDYTtHRSeXX3pYK3a82u3WxENYm3CGbzAG/NWVS/r7C/S9e7DBlRsTkRzN HKjI2wdL4M70abiTcysupeByKsN/ObCcUDmTGoiheuxISwilsqtmnHapd3DTGNtTN6hD b6hfi0jBfoIOb2feKWQAncV+xZfMYser58nR4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=vMc7m3iGi5Fa2wkjzuXJ45Hafh624oNz5r4nQeiqnpO72+kM1TFwUbY4VrXgSoQn0m TG2qW0AHVJ8BRfhwbxwRfpBN4hBvCz1NPXaxPRZ46xD7JPbQtRBClOhWUS4OxjqdCzaT AHRFPwMtlC77krrWPDh5Czsf1GPQal9zcWJSY=
- User-agent: Thunderbird 2.0.0.21 (X11/20090324)
Sean Flanigan wrote:
Hi,
Marcus Nitzschke found [1] some text which translated "public static
void main(String[] args)" as "öffentlich statisch ungültig
Haupt(String[] Argumente)".
This string is used by the New Java Class wizard to ask the user
whether it should include a method with the signature "public static
void main(String[] args)", so I agree with Marcus that the signature
shouldn't be translated. Accordingly, I have marked this string as
non-translatable in Babel [2].
However, I can think of one reason why marking this string as
non-translatable might be a bad idea - it prevents translators from
providing an alternative keyboard accelerator. In fact, Eclipse Genie
was providing just that in the languages I checked, changing the
accelerator from V to G.
By marking it as non-translatable, I have changed all languages to use
the same accelerator as English does. Whether that's a good or bad
thing, I'm not entirely sure.
Do you think strings which contain keyboard accelerators should always
be translatable?
Can't we instead split up accelerators and strings, as it is done in
Mozilla? That is, have a separate entity for each accelerator (hm, I
think the proper name is access key here).
Or is leaving these strings translatable just creating more work for
everyone? Should I revert my change?
No. Rather, a better solution should be found.
H.