[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
AW: [babel-translators] "Non-translatable" strings with keyboard accelerators
|
- From: Thomas Walijew <Thomas.Walijew@xxxxxxxxxxx>
- Date: Wed, 10 Jun 2009 06:56:47 -0500
- Accept-language: de-DE, en-US
- Acceptlanguage: de-DE, en-US
- Delivered-to: babel-translators@eclipse.org
- Thread-index: AcnpwKL0OpgwPX08SdOfTL/Y6iUN9wAALBjg
- Thread-topic: [babel-translators] "Non-translatable" strings with keyboard accelerators
Hello all,
I agree with Hendrik. Reserved words must remain untranslatable, especially when they are used 1:1 to create a method stub, in this case "public static void main".
In the case of accelerators we should take the risk of having dupes in favor of an exact translation.
Best
Thomas
> -----Ursprüngliche Nachricht-----
> Von: babel-translators-bounces@xxxxxxxxxxx [mailto:babel-translators-
> bounces@xxxxxxxxxxx] Im Auftrag von Hendrik Maryns
> Gesendet: Mittwoch, 10. Juni 2009 13:43
> An: Mailing list for Babel translators
> Betreff: Re: [babel-translators] "Non-translatable" strings with
> keyboard accelerators
>
> 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.
> _______________________________________________
> babel-translators mailing list
> babel-translators@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/babel-translators