RE: Translations strings in CVS

[Jeffrey H. <jef...@aj...>]

> In Dai, 13 Eiye 2000, Jeffrey Hobbs wrote:
> > There is a limitation on exactly how some characters can be sent to
> > the event mechanism, because it requires the X-style translated
> > name, but this seems to have been accepted OK for me (via C&P because
> > I can't directly type in that character):
> >
> > (tkcon) 53 % bind .t \373 { puts "K %K A %A"}
> > (tkcon) 54 % bind .t ? { puts "K %K A %A"}
> > (tkcon) 55 %
> 
> Well for me, under tkcon 1.6, 31 March 1999 does not work.
	...
> bad event type or keysym "?"

Actually, I fooled myself.  My original thoughts were correct in that
it requires the X-style name.  Eric added the new 'keysyms' page to
show all these.  This doesn't work in 8.3.1 WinHelp, but you can see
it in the Unix docs of 8.4a1 at:
	http://dev.scriptics.com/man/tcl8.4/TkCmd/keysyms.htm

>Main< (tkcon) 60 % puts \374
u
>Main< (tkcon) 61 % bind .t \374 { puts " u umlaut " }
>Main< (tkcon) 62 % bind .t <Alt-\374> { puts " u umlaut " }
bad event type or keysym "u"
>Main< (tkcon) 63 % format %o 252
374
>Main< (tkcon) 64 % bind .t <Alt-udiaeresis> { puts " u umlaut " }

You'll have to find out what the correct mapping for that greek
character is.  If I do:

>Main< (tkcon) 71 % scan ? %c
240

Then I can see that 240 in the table in the URL above gives 'eth',
and then we have:

>Main< (tkcon) 73 % bind .t <Alt-eth> { puts " eth " }
>Main< (tkcon) 74 % 

Of course, I can't type in the eth here...

This will be something that everybody has to deal with.  One heuristic
is that if [scan $char %c] >= 127, then you'll need to have a mapping
for that character.

Jeffrey Hobbs                     Tcl Ambassador
ho...@Aj...          Ajuba Solutions (nee Scriptics)