Tristan,
Thank you for this quick answer:
About 16bpp:
Great!!! I didn't see the "-pixelformat" option. I tested it and it works
perfectly! So forget "my" patch.
About keyboard management:
I am agree with you, the xmodmap command allows to set (or reset) the
keyboard mapping.
The weak point of xmodmap is an additional configuration file is needed to
correctly set the Xvnc internal keyboard mapping. For installation and
maintenance reasons, it is better to have a correct default behavior (FR,
UK, US...).
The main benefit of xmodmap method is with a signle Xvnc binary, we can
"customize" the internal language.
To summarize, I think the xmodmap method is suitable for changing the
language but I think it's a pity that Xvnc doesn't provide a full PC
keyboard support.
Thank you again for these answers
Vincent DEDIEU
----- Original Message -----
From: "Tristan Richardson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 20, 2001 4:34 PM
Subject: Re: 2 Xvnc bugs (and patches): 16bpp and internal keyboard mapping
> "Vincent DEDIEU" <[EMAIL PROTECTED]> writes:
> > I am using Xvnc 3.3r2 on differents OS (Linux, UW7...) and I found 2
bugs:
> >
> > BUG #1 - 16bpp
> > In 16bpp there is a problem about the number of bits associated with
Red,
> > Green and Blue level. Xvnc uses RGB655 and the "standard" value is
RGB565.
>
>
> This isn't a bug, this is just what the X server "cfb" code does by
default.
> As it happens, I've already made RGB565 the default on our internal
sources,
> but didn't think it significant enough to make a new release (putting
> "-pixelformat rgb565" on the command line isn't that hard is it :-)
>
>
> >
> > BUG #2 - keyboard management
> > An US keyboard map is currently encoded in the Xvnc binary. This raises
2
> > problems:
> > - Some software can't be used with non-US keyboards (for example
rdesktop
> > and a French keyboard)
> > - the US keyboard mapping is incomplete. For example the num pad is
not
> > encoded. So a spreadsheet can be used.
>
>
> Again this isn't a bug. Xvnc will automatically add new "keycodes" for
any
> "keysyms" which it doesn't have in its keyboard mapping already. If
> there'an X application which is broken in this regard you can always
preload
> the keyboard mapping by using xmodmap before running that application.
> There's no need to compile in keyboards for different languages.
>
>
> Cheers
>
> Tristan
>
> --------------------------------------------------------------------------
-
> Tristan Richardson [EMAIL PROTECTED]
www.uk.research.att.com/~tjr
> --------------------------------------------------------------------------
-
> AT&T Laboratories Cambridge, 24a Trumpington Street, Cambridge, CB2 1QA,
UK
> Tel: +44 1223 343000 Fax: +44 1223 313542
www.uk.research.att.com
> --------------------------------------------------------------------------
-
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
