Re: Translation messages file

[<lau...@uf...>]

On  4 Jul, Keiichi Takahashi wrote:
> Hi,
> 
> Thank you for your kind information, Laurent.
> 
> Fortunately I've already obtained updated source from CVS repository when I
> received your previous message, and checked it works. But as I mentioned before,
> the issue of 'underline' is serious in order to add the file of Japanese message
> in lib/tk8.4/msgs.
> 
> For message of Japanese version, I think it better to wait until '&' can be used
> to indicate underlined character.
> 
> Or, is this already available?
> 

No it isn't available yet. I've started working on it but I'm segfaulting
all over the place. And it's a bit more involved than I originally expected.

For those who weren't involved in the discussions, the -underline option
causes problems when you change languages; key bindings become a problem
also. A few solutions have been put forward for both of these problems and
I'm looking at the best way to implement it. 

Mr. Takahashi has proposed using the "&" character to mark the location of
the character to underline and to use -underline & as a special case to
locate it. There have been other proposals (which I would need to dig up in
my voluminous email) but this one seems to be the better one IMO. But it
requires modifying the core structure of the Button widget. There's also a
display issue because the "&" needs to disappear from the string, etc.

How this relates to the binding issue is that the underlined character is
the one that should be used in the key binding for the dialog being used.
There have been some discussions on how to best do the binding. Eric
proposed expanding msgcat to handle the keybindings. I'm lukewarm to the
idea. I wanted to "translate" the key bindings from one language to next by
using special names for the key bindings. Something like:

bind [::msgcat::mc "chooseDirOpenDirectoryKey"] {...}

Eric doesn't like the idea.

.
.
.

Maybe something like

set string [$widget cget -text]
set char [indexOfUnderlineInWidget $string]
bind <Alt-$char> {....}

is another viable alternative. IOW, the binding key to use is returned by
the widget which has the underlined character.

If anyone has any other comments, suggestions, let'em rip. Remember that
it's a holiday in the US so we shouldn't expect anything from the TCT before
tomorrow.

L

-- 
Laurent Duperval                   "Montreal winters are an intelligence test,
U|Force - Java Center                     and we who are here have failed it."
Phone: (514) 282-8484 ext. 228                                   -Doug Camilli
mailto:lau...@uf...      Penguin Power!