[PATCH] Re: Introducing separate strings for quick bar items

2005-07-18 Thread Roland Illig
Egmont Koblinger wrote: On Wed, Jul 13, 2005 at 04:17:19AM +0200, Roland Illig wrote: This would result in a function like this: const char *translate_ui (const char *s) With a simpler name, of course :-))) I'm just wondering whether __() is fair, or should be treated as it belonged to

Re: Introducing separate strings for quick bar items

2005-07-13 Thread Egmont Koblinger
On Wed, Jul 13, 2005 at 04:17:19AM +0200, Roland Illig wrote: This would result in a function like this: const char *translate_ui (const char *s) With a simpler name, of course :-))) I'm just wondering whether __() is fair, or should be treated as it belonged to glibc private namespace. Or

Re: Introducing separate strings for quick bar items

2005-07-12 Thread Egmont Koblinger
On Mon, Jul 11, 2005 at 11:02:31PM +0200, Leonard den Ottolander wrote: F.e. I've translated N_(Quit) to Afsltn in Dutch. This is short for Afsluiten. Now this string fits nicely in the quick bar, but it's quite ugly as a header in the quit dialog. By defining the quit string for the quick

Re: Introducing separate strings for quick bar items

2005-07-12 Thread Leonard den Ottolander
Hi Egmont, On Tue, 2005-07-12 at 13:13, Egmont Koblinger wrote: Quite ugly approach since it relies on Quit actually being shorter than 6 chars. The quick bar strings all have a maximum length of 6 chars. And what do you do at RenMov, Delete, PullDn? I think the former and the latter are

Re: Introducing separate strings for quick bar items

2005-07-12 Thread Pavel Tsekov
Hello, On Tue, 12 Jul 2005, Egmont Koblinger wrote: By the way: the bottom right corner of mc has Quit while the File menu contains eXit associated to F10. Shouldn't they be called the same? Good catch! Just checked Volkov Commander and it has Quit in both places. But what should MC do in

Re: Introducing separate strings for quick bar items

2005-07-12 Thread Roland Illig
Egmont Koblinger wrote: A more generic approach is to add the same prefix to all these strings (e.g. 1Quit), make a comment for translators to leave that prefix as it is (e.g. 1Afsltn) and strip that prefix at runtime. I suggest another naming scheme for it, as the 1 has no intuitive