C. Michael Pilato wrote: > On 04/09/2013 11:45 AM, Branko Čibej wrote: >> I frankly cannot recall a single tool that localizes its command line, >> either commands, options or option values. That way lies insanity; you >> might as well localize C. > > Agreed. Madness. > >> On the other hand, I wouldn't mind localizing the interactive prompts, >> except for the actual command codes. So the example French translation >> of the conflict prompt makes perfect sense to me. > > Yup. I see no problem with the likes of: > > "Do you wish to continue? [y/n]" > > being translated: > > "¿Desea continuar? [(y) sí / (n) no]" > > From Wikipedia's "Internationalization_and_localization" page: > > One example of the pitfalls of localization is the attempt made by > Microsoft to keep some keyboard shortcuts significant in local > languages. This has resulted in some (but not all) programs in the > Italian version of Microsoft Office using "CTRL + S" (sottolineato) > as a replacement for "CTRL + U" (underline), rather than the (almost) > universal "Save" function. > > That's the kind of nonsense we want to avoid. Typing 'p' for > "postpone" at a conflict resolver prompt should have exactly the > same effect regardless of the locale.
No objection here. - Julian
