On Tue, 2003-09-30 at 11:08, Danilo Segan wrote:
> уторак, 30. септембар 2003. 15:42:25 CEST — Vasilis Vasaitis
> написа:
> >
> > It's Not A Bug, It's A Feature. (TM)
> >
> > GTK+ 2.x uses by default its own input methods for character
> > composition. Nevertheless, you can force GTK+ applic
On Fri, 2003-07-18 at 20:32, Hans Deragon wrote:
> Hi again.
>
>
> I found something very interesting that explains why I could not generate the
> with cedilla previously.
>
> In my XF86Config file (XFree86 4.3.0 used), I have the following option:
>
> Option "XkbLayout" "us_int"
>
Some comments here:
* Although there are claims that this applies to French, etc,
it's really a pt_BR specific bug. Not because c-cedilla is
at all specific to Portuguese, but because the us-intl keymap,
which requires this combination to produce c-cedilla, is
used pretty much exclusively
On Mon, 2003-07-07 at 23:42, Yu Shao wrote:
> Hi,
>
> Right now, the four Asian locales' definition in X are:
>
> zh_CN.UTF-8 locale is using en_US.UTF-8's definition,
> zh_TW.UTF-8 is using zh_TW.UTF-8
> ko_KR.UTF-8 is using ko_KR.UTF-8
> ja_JP.UTF-8 is using ja_JP.UTF-8
>
> Actually the detail
On Thu, 2003-06-12 at 23:28, lily wrote:
> > On Tue, 2003-06-10 at 22:25, miaocheng wrote:
> > >I use red hat linux 8.0, the version of XFree86 is 4.2.0 and the
> > > desktop manager is Gnome
> > > I encounter a problem . When I input character of Uighur , which is
> > > one kind of Arb
On Tue, 2003-06-10 at 22:25, miaocheng wrote:
>I use red hat linux 8.0, the version of XFree86 is 4.2.0 and the
> desktop manager is Gnome
> I encounter a problem . When I input character of Uighur , which is
> one kind of Arbic and be generally used in west zone of china, in X
> windo
After passing through several countries and several
hands a copy of a draft standard for Sami keyboard
layouts from the Sami parliamentary council
ended up on my desk.
A quick examination seems to indicate that it has
various differences from the layout in
symbols/sapmi.
I figure that there migh
[EMAIL PROTECTED] (Hideki Hiura) writes:
> > From: Theppitak Karoonboonyanan <[EMAIL PROTECTED]>
> > * Should the client return the string in reversed order?
>
> No.
>
> > The cause of my doubt is that the X11R6.4 "Xlib C Language X Interface"
> > section 13.5.7.3 "Input Method Semantics - S
Markus Kuhn <[EMAIL PROTECTED]> writes:
> I think I have run into a serious bug with XFree86's Xutf8LookupString
> implementation. It occurs when the client runs under XFree86 4.[12], but
> the X server is for example Solaris 5.8
>
> vendor string:Sun Microsystems, Inc.
> vendor release
Keith Packard <[EMAIL PROTECTED]> writes:
> Agreed; this choice was somewhat rhetorical in nature...
>
> > > b) use $LANG or $LC_CTYPE?
> >
> > If this road is taken, it has to be determined which env.
> > variables have to be refered to in what order. AFAIK, SUS and POSIX say
> > that
Keith Packard <[EMAIL PROTECTED]> writes:
> Around 14 o'clock on Jul 8, Owen Taylor wrote:
>
> > +locale = (FcChar8 *)setlocale (LC_CTYPE, NULL);
>
> Don't you mean LC_MESSAGES? If so, I think we should be able to use this
> return value almos
Keith Packard <[EMAIL PROTECTED]> writes:
> Much as I hate the C locale model, I'm wondering if I shouldn't use the
> current locale as a language hint where applications don't provide
> explicit language information when selecting fonts. This would make
> the generic aliases (like "sans-seri
Brian Stell <[EMAIL PROTECTED]> writes:
> Viveka Nathan K wrote:
> > ...
> > If I type the vowel character 'D' next to the consonant 'K', the already
> > printed consonant, should be removed and the character corresponding to the
> > combination of the Consonant+Vowel should be displayed.
>
> T
Markus Kuhn <[EMAIL PROTECTED]> writes:
> Dr Andrew C Aitchison wrote on 2002-04-30 21:08 UTC:
> > Given that en_US.UTF-8 is the only instance of a locale file with UTF-8
> > in its name,
>
> In Xlib, yes. This should be extended, I think.
At least for European locales this isn't a problem...
Ivan Pascal <[EMAIL PROTECTED]> writes:
> Owen Taylor wrote:
> > I'm certainly not certain that we shouldn't set up the font sets that
> > way, but some reasons I didn't suggest it were:
> >
> > - There are some strange effects that occ
[EMAIL PROTECTED] (Hideki Hiura) writes:
> > From: Owen Taylor <[EMAIL PROTECTED]>
> > My recommendation, then, for the UTF-8 locale files, is that for locales
> > where iso10646-1 is a reasonable font encoding, we should point to
> > a en_US.UTF-8 locale that h
I've been looking some recently at using UTF-8 locales with Xlib's
i18n code, and the conclusion I seem to be coming to is that the
contents of nls/XLC_LOCALE/en_US.utf8 are entirely and completely bogus.
What is in there is something like
XCOMM fs0 class
fs0 {
charset {
Isam Bayazidi <[EMAIL PROTECTED]> writes:
> > If my understanding is correct, we're not far from a solution now. Adding
> > new keysyms is relatively easy once the decision is made that the new
> > symbol is necessary.
>
> OK .. now what application does take the keysym input and puts the corr
Keith Packard <[EMAIL PROTECTED]> writes:
> Around 12 o'clock on Feb 20, Tomohiro KUBOTA wrote:
>
> > What font name you use? I imagine Devanagari will need more glyph
> > codepoints than character codepoints. Since these X11 functions
> > assume the character encoding to be *glyph* index, I
Roozbeh Pournader <[EMAIL PROTECTED]> writes:
> On Wed, 20 Feb 2002, Pablo Saratxaga wrote:
>
> > A long term choice is to add the possibility to send lam+alef.
>
> Do you know where?
What you'd have to do is extend the set of XKB actions to have
an action "send multiple key presses" - somet
Rui-Xiang Guo <[EMAIL PROTECTED]> writes:
> > I believe the cause and effect was:
> >
> > - xcin didn't work
> > - This cause untested code to be run which crashed.
>
> Hmm, let's go back my original question. :)
> Why xcin work under XFree 4.1 but not under XFree 4.2 ?
> I only wrote "seten
Rui-Xiang Guo <[EMAIL PROTECTED]> writes:
> On Sun, Jan 27, 2002 at 01:29:48PM -0500, Owen Taylor wrote:
> >
> > Owen Taylor <[EMAIL PROTECTED]> writes:
> >
> > > Rui-Xiang Guo <[EMAIL PROTECTED]> writes:
> > >
> > > OK, I wa
It seems that imConv.c is currently linked into libX11.so.
Is it also necessary to link it into ximcp.so? I wouldn't
have thought so.
In any case, this doesn't look related to this particular
problem.
Regards,
Owen
ISHIKAWA Mutsumi <[EMAIL PROTECTED]> wr
Owen Taylor <[EMAIL PROTECTED]> writes:
> Rui-Xiang Guo <[EMAIL PROTECTED]> writes:
>
> OK, I was able to reproduce it and figured out the immediate
> problem here:
>
> _XDynamicRegisterIMInstantiateCallback() dlopens 'ximcp.so'
>
Rui-Xiang Guo <[EMAIL PROTECTED]> writes:
> > What input method are you using? I've seen another report of this for
> > Chinese (http://bugzilla.gnome.org/show_bug.cgi?id=69523); but
> > it seems to work fine for Japanese (or at least, no reports of
> > problems.)
>
> Hello,
> I use xcin as chi
Rui-Xiang Guo <[EMAIL PROTECTED]> writes:
> Hi, all
> recently I update my XFree 4.1 to 4.2 and find some programs
> no more work. :(
> Like gqview, mozilla,...etc, which compiled with gtk/glib just
> get the core dump.
> It seems to the problem of X11 lib.
> Here are some gdb message from gqvie
Keld Jørn Simonsen <[EMAIL PROTECTED]> writes:
> On Mon, Oct 22, 2001 at 01:09:24PM +0100, Markus Kuhn wrote:
> > On Mon, 22 Oct 2001, Vasif Ismailoglu MD wrote:
> > > How xmodmap works with unicode? For example
> > > Azerbaidjani works under unicode. How I can make
> > > xmodmap file for unicod
Francisco Lobo <[EMAIL PROTECTED]> writes:
> The problems really started when I tried to use my new keymap file. The
> setxkbmap utility wouldn't work and setting XF86Config as above gave the
> error I mention in the beginning.
>
> I wasted time in breaking down my keymap file into the differ
"Lau Tung-Leng" <[EMAIL PROTECTED]> writes:
> Dear All,
>
> I am currently writing an Input Method for the TinyX environment on an
> in house StrongARM board (very much like the Compaq iPAQ). I'm using
> IMdKit (yes, I know it's kind of outdated...) to develop the IM.
>
> The IM has been set
Markus Kuhn <[EMAIL PROTECTED]> writes:
> On Wed, 3 Oct 2001, Tomohiro KUBOTA wrote:
> > I need variable-width fonts which includes reasonable-proportion
> > glyphs of latin/greek/cyrillic/katakana/hiragana/katakana/ideograph/hangul.
> > In such fonts, hiragana/katakana/ideograph/hangul will hav
Juliusz Chroboczek <[EMAIL PROTECTED]> writes:
> >> However, XIM support imposes that we use font sets, thus pulling in
> >> a whole new range of bugs.
>
> TK> Are you saying that nothing should be added to XTerm?
>
> No. I am not objecting to the use of fontsets. I am objecting to the
> fac
Tomohiro KUBOTA <[EMAIL PROTECTED]> writes:
> Hi,
>
> At Sun, 2 Sep 2001 12:32:17 +0200,
> Pablo Saratxaga <[EMAIL PROTECTED]> wrote:
>
> > Xft in unicode only is simple and thiny; is conversion mechanism should be
> > added it will be fat very quickly, it will add extra requirements on iconv
32 matches
Mail list logo
