[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Localization of user replies

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2004-12-05 20:30:29 CET

On Sun, 5 Dec 2004, Norbert Unterberg wrote:

> While doing some polishing work on the German translation, I noticed
> something which currently fails to localize: The user's response when
> subversion asks questions:
>
> Example: in clients/cmdline/prompt.c:297 subversion asks the user:
> (R)eject, accept (t)emporarily or accept (p)ermanently?
> Obviously the possible replies are R, T, P which correspond to the first
> letters of some words in the question. These letters are hard coded in
> the source code and can not be localized. Can you imagine how hard is it
> to find adequate words in different languages that also contain these
> letters?
>
> Here my suggestion:
> Allow to localize the replies as well. This should not be too hard and
> coud be done like this:
> Add an additional string that contains the possiblie user replies in
> upper and lower case:
>
I think something like this is a good idea. You want to qualify it in some
way to not get duplicates. Have a string like SSL Server Trust
Prompt|aRrTtPp (jsut an example). Then the translator would translate the
letters after the |. The code would scan the translated string for the |
and use the letters there after. This is inspired from a section in the
gettext manual about hwo to handle short GUI items, where the same English
term will need different translations depending on context. YOu can look
there and get the idea. We can talk about the details, but I think the
main idea is good. What do others say?

Regards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 5 20:31:55 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.