[EMAIL PROTECTED] wrote:
>
> Hello, Angus,
>
> Attached is another xforms-i18n patch in which
>
> 1. I made XFontSet to be loaded only on the machine with locales set
> Chinese, Japanese or Korean ( or their aliases, of course).
Ugly!!! Still I guess that you have to release sometime. Fair en
Apparantly, I forgot to attach the patch. Hre si the one.
cghan
diff -urdN xforms-1.0-release/Imakefile xforms-1.0-i18n/Imakefile
--- xforms-1.0-release/ImakefileWed Dec 4 02:25:43 2002
+++ xforms-1.0-i18n/Imakefile Tue Feb 25 19:19:40 2003
@@ -100,7 +100,7 @@
image \
Hello, Angus,
Attached is another xforms-i18n patch in which
1. I made XFontSet to be loaded only on the machine with locales set
Chinese, Japanese or Korean ( or their aliases, of course).
2. The messy part in handle_key in input.c is removed so that the order is
back to the original.
Plea
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> On Tuesday 25 February 2003 09:07, Jean-Marc Lasgouttes wrote:
>> José> Probably Jean-Marc, as always, knows the answer. ;-)
>>
>> What are you trying to obtain from me?
José> A smile?! ;-)
OK, this I can give you :)
JMarc
On Tuesday 25 February 2003 09:07, Jean-Marc Lasgouttes wrote:
>
> José> Probably Jean-Marc, as always, knows the answer. ;-)
>
> What are you trying to obtain from me?
A smile?! ;-)
> JMarc
--
José Abílio
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> On Monday 24 February 2003 14:38, Angus Leeming wrote:
>> You should set the xforms.Fontset option in your .Xdefaults file.
>> (I think that the syntax is correct but am not too sure. Try. If
>> successful, you'll get fontset == 1
>>
>
[EMAIL PROTECTED] wrote:
>
> Angus, there seems something seriously wrong in your new code of
> '-fontset'. I have had two kinds of problems.
>
> 1. After loading your 'trial' widget without '-fontset' option, my
> X-Window behaves abnormally. One of my xterms crashes without any reason,
> and
Angus, there seems something seriously wrong in your new code of
'-fontset'. I have had two kinds of problems.
1. After loading your 'trial' widget without '-fontset' option, my
X-Window behaves abnormally. One of my xterms crashes without any reason,
and even after stopping the 'trial' this
> Angus, you should know that there are some linux users who even do not
> read README. To them, this shell script cannot be the answer.
Then they should stick to an OS that treats them as stupid ;-)
> Well, I think I can go with 'lyx -fontset'. In fact, with the kde
> or gnome desktop setting,
On Mon, 24 Feb 2003, Angus Leeming wrote:
> Wow!
>
> You could supply them with a shell-script wrapper:
>
> $ cat cjklyx
> #! /bin/sh
> if [ $# = 0 ]; then
> lyx -fontset
> elif (echo $* | grep '[-]fontset' > /dev/null); then
> lyx $@
> else
> lyx -fontset $@
> fi
>
[EMAIL PROTECTED] wrote:
>
>> You should set the xforms.Fontset option in your .Xdefaults file. (I
> think
>> that the syntax is correct but am not too sure. Try. If successful,
> you'll
>> get
>> fontset == 1
>>
>> I think that you need to restart X after changing .Xdefaults.
>
>
> Is
> You should set the xforms.Fontset option in your .Xdefaults file. (I
think
> that the syntax is correct but am not too sure. Try. If successful,
you'll
> get
> fontset == 1
>
> I think that you need to restart X after changing .Xdefaults.
Isn't it possible to make the end-users to "
On Monday 24 February 2003 14:38, Angus Leeming wrote:
>
> You should set the xforms.Fontset option in your .Xdefaults file. (I think
> that the syntax is correct but am not too sure. Try. If successful, you'll
> get
> fontset == 1
>
> I think that you need to restart X after changing .Xdef
[EMAIL PROTECTED] wrote:
>
>> What does the print statement, above, print to console when you run?
>> $ lyx -fontset
>> It should be:
>> fontset == 1
>
>
> All is well, here. By the way, is there any 'noble' way of putting the
> option '-fontset' inside the CJK-LyX so that we do
[EMAIL PROTECTED] wrote:
>
> Just ignore my previous messages. It was a false alarm. So with this,
> '-fontset' option turns on "fl_cntl.fontset=1", right?
Yes. Pass -fontset to any xforms app (including lyx) and it will set
fl_cntl.fontset to 1.
--
Angus
> What does the print statement, above, print to console when you run?
> $ lyx -fontset
> It should be:
> fontset == 1
All is well, here. By the way, is there any 'noble' way of putting the
option '-fontset' inside the CJK-LyX so that we don't have to turn this
option on each
[EMAIL PROTECTED] wrote:
>
> Please bear with me, Angus. I cannot understand a thing in your new code.
> But let me try.
>
> @@ -863,6 +866,7 @@
> fl_cntl.vclass = fl_vclass_val(fl_cntl.vname);
> fl_cntl.coordUnit = fl_get_vn_value(vn_coordunit, OpCoordU
Just ignore my previous messages. It was a false alarm. So with this,
'-fontset' option turns on "fl_cntl.fontset=1", right?
cghan
Please bear with me, Angus. I cannot understand a thing in your new code.
But let me try.
@@ -863,6 +866,7 @@
fl_cntl.vclass = fl_vclass_val(fl_cntl.vname);
fl_cntl.coordUnit = fl_get_vn_value(vn_coordunit, OpCoordUnit);
+printf("fontset == %d\n",
[EMAIL PROTECTED] wrote:
>
> On Mon, 24 Feb 2003, Angus Leeming wrote:
>
>
>> Ok I tested it with LANG == en_US.UTF-8 (Standard RH8 setup).
>> All is fine.
Sorry. All is fone with LANG == C. All is BAD with LANG == en_US.UTF-8. No
surprise there.
>> This should be set by a flag passed to fl_
On Mon, 24 Feb 2003, Angus Leeming wrote:
> Ok I tested it with LANG == en_US.UTF-8 (Standard RH8 setup).
> All is fine.
>
> Note, however, that I don't think that xforms should be clever about
this.
I know. The patch should fail where some non-standard locale setting is
set.
> This shoul
[EMAIL PROTECTED] wrote:
> Attached another of my 'beavering'. It works with 'LANG=C' environment
> here. Would you mind testing the patch in your environment ?
> If it fails, I'm sure that the 'if condition' of the new 'use_fontset()'
> defined at flresource.c, as
Ok I tested it with LANG == en_
Hello, Angus,
On Sun, 23 Feb 2003, Angus Leeming wrote:
> > Attached another of my 'beavering'. It works with 'LANG=C'
> environment > here. Would you mind testing the patch in your
> environment ?
>
> Ok.
>
If it works for your environment, I better leave it as it is. O.K. ?
Have you got the
[EMAIL PROTECTED] wrote:
>
> Hello, Angus,
>
> Attached another of my 'beavering'. It works with 'LANG=C' environment
> here. Would you mind testing the patch in your environment ?
Ok.
> If it fails, I'm sure that the 'if condition' of the new 'use_fontset()'
> defined at flresource.c, as
>
>
[EMAIL PROTECTED] wrote:
>
> On Fri, 21 Feb 2003, Angus Leeming wrote:
>
>> Ok, CG. I tried it. xfs uses all my cpu. This is very wrong :-( Can you
> try
>> things out with LANG=C or something 'normal'. This thing has to work for
>> the rest of the world too, doesn't it?
>
>
> Well, I should h
Hello, Angus,
Attached another of my 'beavering'. It works with 'LANG=C' environment
here. Would you mind testing the patch in your environment ?
If it fails, I'm sure that the 'if condition' of the new 'use_fontset()'
defined at flresource.c, as
***
extern int
On Fri, 21 Feb 2003, Angus Leeming wrote:
> Ok, CG. I tried it. xfs uses all my cpu. This is very wrong :-( Can you
try
> things out with LANG=C or something 'normal'. This thing has to work for
> the rest of the world too, doesn't it?
Well, I should have expected this kind of disaster soon
Angus Leeming <[EMAIL PROTECTED]> wrote:
(B
(B> Ok, CG. I tried it. xfs uses all my cpu. This is very wrong :-( Can you try
(B> things out with LANG=C or something 'normal'. This thing has to work for
(B> the rest of the world too, doesn't it?
(B
(BI guess you are trying to scale a bitmap fon
[EMAIL PROTECTED] wrote:
> So I cleaned up a little bit and made the patch against clean xforms-1.0,
> which I attached on this mail. I hope you lok at the patch and polish it
> as much as possible, and then send it back to me as soon as possible.
> Because the CJK-LyX-1.3.0 critically depends on
> In "Edit->Find..." widget, the first signal(whether it is ascii letter
> 'a', or CJK-char) has
> "beginrange = 0, endrange = 0". This being the case, the English letter
is
> not swallowed.
> Even on this widget, all the subsequent signals have
> "beginrange = 0, endramge = -1".
Based on these
On Fri, 21 Feb 2003, Angus Leeming wrote:
>
> It looks to me that this piece of code is meant to remove highlighted
text.
> Somethink like, mark a block of text with the cursor key and press any
key.
> The highlighted block is replaced by your key.
>
Yes, I just confirmed your guess.
> What
[EMAIL PROTECTED] wrote:
>
> Hello, Angus:
>
> I have made some interesting observations regarding to the "swallowing"
> of the first CJK-chars on the "Edit->Find&Search" box.
>
> The 'draw_char' in input.c starts with the block,
> "if (sp->endrange >= 0)
> {
> delete_piece(ob, sp->beginra
Hello, Angus:
I have made some interesting observations regarding to the "swallowing"
of the first CJK-chars on the "Edit->Find&Search" box.
The 'draw_char' in input.c starts with the block,
"if (sp->endrange >= 0)
{
delete_piece(ob, sp->beginrange, sp->endrange - 1);
slen = strlen(sp
On 20 Feb 2003, Jean-Marc Lasgouttes wrote:
>
> I cannot comment on the content of the patch itself, but I have two
> observation on its form.
>
> 1/ the header forms.h is AFAIK automatically generated from the
> various header files in lib/include. So you should not modify this
> files directly
> "cghan" == <[EMAIL PROTECTED]> writes:
cghan> So I cleaned up a little bit and made the patch against clean
cghan> xforms-1.0, which I attached on this mail. I hope you lok at
cghan> the patch and polish it as much as possible, and then send it
cghan> back to me as soon as possible.
I ca
Hello, Angus;
my mail failed to reach you yesterday. The internet mail delivery system
seems unstable recently.
On Tue, 18 Feb 2003, Angus Leeming wrote:
> > > (a) the first widget in both windows overwrite the 'X' or
> > > (b) only the first widget of the first dialog?
> > >
> > > I ask bec
On Mon, 17 Feb 2003, Angus Leeming wrote:
> If you _can_ draw the space like this and want the space then I
> suspect that we don't need the complicated code in input.c at all.
> Ie, we can treat the two XEvents separately after all and get rid of
> the stored_keybuf nastiness.
>
> i
Angus Leeming wrote:
> If you _can_ draw the space like this and want the space then I
> suspect that we don't need the complicated code in input.c at all.
> Ie, we can treat the two XEvents separately after all and get rid of
> the stored_keybuf nastiness.
Sorry, that should be:
if (kbuf
[EMAIL PROTECTED] wrote:
>
> On Mon, 17 Feb 2003, Angus Leeming wrote:
>
>> Would this be what you _really_ wanted in the xforms input widget
>> perhaps?
>>
>> // Or whatever test you now use to indicate that
>> // precomposition is finished
>> if (key == XKSpace and stor
On Mon, 17 Feb 2003, Angus Leeming wrote:
> Would this be what you _really_ wanted in the xforms input widget
> perhaps?
>
> // Or whatever test you now use to indicate that
> // precomposition is finished
> if (key == XKSpace and stored_kbuflen > 1) {
> in
[EMAIL PROTECTED] wrote:
> In the xforms input widget, because of the space signal, the
> CJK-characters were sallowed. On the WorkArea, this never happens.
> So keeping 'space' is allowed.
Sigh...
Would this be what you _really_ wanted in the xforms input widget
perhaps?
// Or whatever
On Mon, 17 Feb 2003, Angus Leeming wrote:
>
> Ah, I understand. You want to 'turn on' the red square AND input your
> CJK char. I'm sure that Juergen could solve this in two minutes.
> Unfortuanately, he seems to have dissappeared.
>
> JJUUEERRGGEENN !
>
Means I have to wait indefinitely?si
[EMAIL PROTECTED] wrote:
> Thank you for your re-interpretation of the CJK-input process. Here
> the problem is because of this process, inputting the first
> precomposed CJK-chars on the default cell of table fails. Let me
> explain the problem in step by step. First, I open the table and at
> thi
On Mon, 17 Feb 2003, Angus Leeming wrote:
>
> Guys, a brief préãis of how this CJK composition works:
>
> In 'normal' text input, X passes each XEvent through to LyX:
> one XEvent -> One char to place on the screen.
>
> When using these oriental precomposition methods:
>
> * Shift-space t
[EMAIL PROTECTED] wrote:
> My second problem is with regard to the tabular inset. When the
> table menu is clicked, table appears on the lyx main window. And at
> this moment, no "red square" appears on any of the tabular cells.
> However when I press, for example, "a" key, the signal from the
> ke
Hello,
In my search of the position parameters of the cursor owned by the local
Input Method in tabular, footnote and note insets, I've got now some results
and a couple of questions.
First, the results: I can now put local Input method cursor at the right
position on those three insets. Fur
On Fri, 14 Feb 2003, Angus Leeming wrote:
>
> Well, you must call this code FROM somewhere. If this somewhere is a class
> method, does the class have access to a BufferView* returned by
>
> buffer.h: BufferView * getUser() const;
> BufferView_pimpl.h: BufferView * bv_;
> funcrequest.
On Sat, Feb 15, 2003 at 12:23:34AM +0900, [EMAIL PROTECTED] wrote:
> Please, it is important for people living in Far-Eastern country!
Oh, I know, it's just trying to get the stuff through my thick skull is
a very slow and tedious process...
john
On Fri, 14 Feb 2003, John Levon wrote:
> > PS: a stupid idea: wouldn't you have more luck with your CJK patch by
> > trying to make the qt version work? Isn't qt supposed to do all that
> > correctly?
>
> Nooo, not all this language stuff all over again ! :))
>
Please, it is important for peo
On Friday 14 February 2003 3:08 pm, [EMAIL PROTECTED] wrote:
> On Fri, 14 Feb 2003, Angus Leeming wrote:
> > Congratulations duly sent. Incidentally, why are you using
> > 'current_view'. It's a nasty, ugly hack. Could you not pass a (BufferView
> > *) to the function that requires this? That's gua
On Fri, Feb 14, 2003 at 03:03:52PM +, Angus Leeming wrote:
> I think that John has demonstrated that the Qt language interface is
> "difficult".
I think that's a bit unfair to Qt actually. Most of the problems were
our not-really-multilingual-but-we-pretend-to-be code, and my lack of
know
On 14 Feb 2003, Jean-Marc Lasgouttes wrote:
>
> Note that this will only give you the outer inset (think for example
> an ERT inset in a footnote). If what you mean is really the inset
> which is being edited, you have to do some extra voodoo magic I never
> understood.
>
I see what you mean.
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Fri, Feb 14, 2003 at 03:53:18PM +0100, Jean-Marc Lasgouttes
John> wrote:
cghan> the current_view! : "current_view->theLockingInset()" . It's
>> Note that this will only give you the outer inset (think for
>> example an ERT inset in a
On Friday 14 February 2003 2:56 pm, John Levon wrote:
> On Fri, Feb 14, 2003 at 03:53:18PM +0100, Jean-Marc Lasgouttes wrote:
> > cghan> the current_view! : "current_view->theLockingInset()" . It's
> >
> > Note that this will only give you the outer inset (think for example
> > an ERT inset in a fo
On Fri, 14 Feb 2003, Angus Leeming wrote:
>
> Congratulations duly sent. Incidentally, why are you using 'current_view'.
> It's a nasty, ugly hack. Could you not pass a (BufferView *) to the function
> that requires this? That's guaranteed to work in the future also when we have
> more than on
On Fri, Feb 14, 2003 at 03:53:18PM +0100, Jean-Marc Lasgouttes wrote:
> cghan> the current_view! : "current_view->theLockingInset()" . It's
>
> Note that this will only give you the outer inset (think for example
> an ERT inset in a footnote). If what you mean is really the inset
Really ?? I've
> "cghan" == <[EMAIL PROTECTED]> writes:
cghan> Congratulate me, folks! I've just got how to call insets from
cghan> the current_view! : "current_view->theLockingInset()" . It's
cghan> that simple! Now I'm in business again!!!
Note that this will only give you the outer inset (think for exa
On Friday 14 February 2003 2:55 pm, [EMAIL PROTECTED] wrote:
> On Fri, 14 Feb 2003 [EMAIL PROTECTED] wrote:
> > Anyhow I need to know how to call insets such as footnote and tables
>
> from
>
> > the current bufferview, i.e., I like to have
> >
> > "(current bufferview)->(inset)->x()" or "...->getL
On Fri, 14 Feb 2003 [EMAIL PROTECTED] wrote:
> Anyhow I need to know how to call insets such as footnote and tables
from
> the current bufferview, i.e., I like to have
>
> "(current bufferview)->(inset)->x()" or "...->getLyXText(..)->x()", or
> something like that.
Congratulate me, folks! I'v
On Fri, 14 Feb 2003, Angus Leeming wrote:
> Guys?
> (FYI, CG has been beavering away and can has moved all the nasty Composition
> stuff into the GUI library. As a result he can now also enter Korean
> characters in the xforms input widgets as well as on the main LyX screen. His
> one real rema
On Friday 14 February 2003 11:27 am, [EMAIL PROTECTED] wrote:
> On Fri, 14 Feb 2003, Angus Leeming wrote:
> > Put it this way: how do you expect to get your patch into the official
> > xforms library when it contains such nastiness ;-)
> >
> > Anyway, you have isolated the problem and have things w
On Tue, 4 Feb 2003, Angus Leeming wrote:
> do_keyboard(XEvent * xev, int formevent)
> {
> Window win;
> - int kbuflen;
>
> ...
> if ( keyform ) {
> KeySym keysym = 0;
> - unsigned char keybuf[227];
>
> kbuflen = fl_XLookupString((XK
On Tue, 4 Feb 2003, Angus Leeming wrote:
>
> Does this pseudo patch (below) fix your problem. It means that the global vars
> will be filled by fl_XLookupString rather than the local ones.
I don't get here. The patch below is exactly the same as I have.
>
> 1. When you precompose another C
On Tuesday 04 February 2003 1:25 pm, [EMAIL PROTECTED] wrote:
> With this "work_area->form", I now have a working XIC for the WorkArea
> events. Precomposition of CJK-characters on the lyx main window is
> perfect. However putting these precomposed characters on the screen with
> your function, "fl
On Mon, 3 Feb 2003, Angus Leeming wrote:
>
> Add lots of statements like
> printf("xoffset = %d\n", sp->xoffset);
> whereever you want to find out what these parameters store.
>
Oh, these printf's are my primary tool, for a code-illiterate like me
Sometimes they help, sometimes the
On Monday 03 February 2003 5:17 pm, [EMAIL PROTECTED] wrote:
> On Mon, 3 Feb 2003, Angus Leeming wrote:
> > Print statements, CG, print statements!
>
> Sorry, I cannot catch you. What do you mean by "Print statements"?
Add lots of statements like
printf("xoffset = %d\n", sp->xoffset);
wher
On Mon, 3 Feb 2003, Angus Leeming wrote:
>
> Print statements, CG, print statements!
>
Sorry, I cannot catch you. What do you mean by "Print statements"?
> Looking at struct SPEC:
> int xoffset;
> int yoffset;
> int position; /* cursor position (in chars) */
>
On Monday 03 February 2003 1:22 pm, [EMAIL PROTECTED] wrote:
> Hello, Angus,
>
> I have been trying to find the parameters for the x,y- coordinates of the
> current cursor position. I have tried sp->xpos, sp->position, etc and some
> combination of these, with no avail. Now I'm wondering where the
Hello, Angus,
I have been trying to find the parameters for the x,y- coordinates of the
current cursor position. I have tried sp->xpos, sp->position, etc and some
combination of these, with no avail. Now I'm wondering where the piece
of codes is, that dictate the current cursor position. Any hint
On Sun, 2 Feb 2003, Angus Leeming wrote:
> > > }
> >
> > 'Shift-Space' does not produce any print-out! In fact, I see that no
> > signal from the keyboard is entering into this part in input.c.
Hm...
>
> Does input.c get called at all for any keypress events. Must do. (Add a
print$
> at t
On Sunday 02 February 2003 5:11 pm, [EMAIL PROTECTED] wrote:
> On Sun, 2 Feb 2003, Angus Leeming wrote:
> > No, you are not missing anything. I was refering to this code.
> >
> > > By the way, a quick test shows that this code does not affect the
> > > precomposition point. That is, the keyboard si
On Sun, 2 Feb 2003, Angus Leeming wrote:
>
> No, you are not missing anything. I was refering to this code.
>
> > By the way, a quick test shows that this code does not affect the
> > precomposition point. That is, the keyboard signal does not go through
> > this part ("turn_on_local_input(ob);"
On Sunday 02 February 2003 4:22 pm, [EMAIL PROTECTED] wrote:
> On Sun, 2 Feb 2003, Angus Leeming wrote:
> > Sure. Presumably related to that missing psuedo-code in input.c
> >
> > > if (sp->CJK_composition_on && keysym)
> > > Turn_off_composition_Insert_composed_char_and
> >
> >
On Sun, 2 Feb 2003, Angus Leeming wrote:
>
> Sure. Presumably related to that missing psuedo-code in input.c
>
> > if (sp->CJK_composition_on && keysym)
> > Turn_off_composition_Insert_composed_char_and
> Increment_position_by_one();
>
I thought you refer this to
"turn_o
On Sun, 2 Feb 2003, Angus Leeming wrote:
> > > the st_xev.xfocus.window.
> >
> > This was what I was about to ask you. So I can safely ignore this part ?
>
> _I_ don't know. I'm English and words containing anything other than [a-zA-Z]
> gets me confused ;-)
>
Sounds REASONABLE..
> The t
On Sunday 02 February 2003 3:15 pm, [EMAIL PROTECTED] wrote:
> > > Yes, with that modification I can input Korean characters on the
> > > XWorkArea.
> >
> > Excellent!
>
> But inputting CJK-characters on xfom-box is still not possible.
Sure. Presumably related to that missing psuedo-code in input.
On Sunday 02 February 2003 3:20 pm, [EMAIL PROTECTED] wrote:
> > In forms.c you have this:
> > case FocusIn:
> > -if (fl_context->xic)
> > +if (evform->xic)
> > {
> > M_info("Focus", "Setting focus window for IC");
> > -XSetICValues(fl_context-
On Sun, 2 Feb 2003, Angus Leeming wrote:
> In forms.h you have this as well as one for 'fl_get_composed_string'.
> +FL_EXPORT void ol_get_composed_string(
> +int * ptr_kbuflen,
> +char const * ptr_keybuf
> +);
>
> I take it that this is
> 'o
On Sun, 2 Feb 2003, Angus Leeming wrote:
>
> Oh, I see.
>
> You can't.
>
> But you shouldn't be either. I thought that you were going to create the IC in
> forms.c and then MODIFY it in input.c when the user pressed 'Shift Space'.
>
> That way, your precomposition area will:
> 1. move alon
Looking at your patch:
In forms.h you have this as well as one for 'fl_get_composed_string'.
+FL_EXPORT void ol_get_composed_string(
+int * ptr_kbuflen,
+char const * ptr_keybuf
+);
I take it that this is
'old fl_get_composed_string that d
On Sunday 02 February 2003 2:12 pm, [EMAIL PROTECTED] wrote:
> On Sun, 2 Feb 2003, Angus Leeming wrote:
> > Oh, well done ChangGil! A Happy start to the Old New Year!
>
> So far so good. Happy about that!
>
> > Looking at the code in input.c, I see code in handle_key:
> >
> > SPEC *sp = ob->s
On Sun, 2 Feb 2003, Angus Leeming wrote:
> Oh, well done ChangGil! A Happy start to the Old New Year!
So far so good. Happy about that!
> Looking at the code in input.c, I see code in handle_key:
>
> SPEC *sp = ob->spec;
> ...
> /* merge the new character */
> for (i
On Sunday 02 February 2003 11:20 am, [EMAIL PROTECTED] wrote:
> Hello, Angus;
>
> I'm back now and this is how far I've got:
>
> 1. Migration of XIC from flresource.c to forms.c is now complete (more or
> less). If I remove stuffs in lyxim.C from CJK-LyX, I find
> that precomposition of CJK-charact
Hello, Angus;
I'm back now and this is how far I've got:
1. Migration of XIC from flresource.c to forms.c is now complete (more or
less). If I remove stuffs in lyxim.C from CJK-LyX, I find
that precomposition of CJK-characters on both XWorkArea(main lyx window)
and the xform box become possib
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > the 'ø' is pronouned similar to the first sound in 'earn'
|
| But it is a short vowel, isn't it?
yes.
--
Lgb
On Fri, Jan 31, 2003 at 10:39:28AM +0100, Lars Gullik Bjønnes wrote:
> | I'd use a short ö for the ø.
> | Reading it as 'Bjemptysetness' seems inappropriate.
>
> I thought you would say "fitting".
> (which incidentely is a pretty obcene word in norwegian... but enough
> of that)
Sorry. I forgot
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Thu, Jan 30, 2003 at 01:37:41PM +, Angus Leeming wrote:
| > Lars Gullik Bjønnes wrote:
| > > [...]
| > [...]
| > Incidentally, how do you pronouce your surname?
|
| I'd use a short ö for the ø.
|
| Reading it as 'Bjemptysetness' seems inapprop
On Thu, Jan 30, 2003 at 01:37:41PM +, Angus Leeming wrote:
> Lars Gullik Bjønnes wrote:
> > [...]
> [...]
> Incidentally, how do you pronouce your surname?
I'd use a short ö for the ø.
Reading it as 'Bjemptysetness' seems inappropriate.
Andre'
--
Those who desire to give up Freedom in o
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > <[EMAIL PROTECTED]> writes:
| >
| > | How about you? Mr. Angus, Angus, leeming, ...?
| >
| > Angie Boy!
|
| No! ;-)
| Incidentally, how do you pronouce your surname?
|
| bj-ugh-ness ?
:-)
I have never met a person
Lars Gullik Bjønnes wrote:
> <[EMAIL PROTECTED]> writes:
>
> | How about you? Mr. Angus, Angus, leeming, ...?
>
> Angie Boy!
No! ;-)
Incidentally, how do you pronouce your surname?
bj-ugh-ness ?
--
Angus
[EMAIL PROTECTED] wrote:
> Anyway you want suits me. But CG owuld be simplest?
> How about you? Mr. Angus, Angus, leeming, ...?
Angus will do ;-) Have a good break CG.
--
Angus
<[EMAIL PROTECTED]> writes:
| How about you? Mr. Angus, Angus, leeming, ...?
Angie Boy!
--
Lgb
On Thu, 30 Jan 2003, Angus Leeming wrote:
> Thus, you should move the XCreateIC call from fl_initialize to a
> point in fl_prepare_form_window after the GC has been created.
> Moreover, you should store the generated xic in struct FL_FORM if it
> is a per-window variable, rather than in FL_CONTEX
[EMAIL PROTECTED] wrote:
>> XIC is designed to be created for each GC (graphic
>> context). Especially, each window (widget) must
>> have its own input context if it expects user input.
>> The current design of xforms is flawed that it
>> creates only process global XIC and tries to use it
>> for
Hello, Miyata:
Glad to hear from you.
On Thu, 30 Jan 2003, Shigeru Miyata wrote:
> Sorry, I don't have time to look at the source
> right now.
> So here are only vague general remarks.
>
> XIM is designed to be created only once for an X
> connection. Don't create more than one XIM
> nor
Sorry, I don't have time to look at the source
(Bright now.
(BSo here are only vague general remarks.
(B
(BXIM is designed to be created only once for an X
(Bconnection. Don't create more than one XIM
(Bnor destroy and recreate again and again.
(BXlib can be quite fragile, (especially you t
Hello, Angus;
On Wed, 29 Jan 2003, Angus Leeming wrote:
> Dear CG, thanks for the explanation. I now understand that we need only
one
> IC (per dialog?) and that we can change it's position using
XSetICValues.
> Great, I've learnt something new.
I am glad that I can still hold your interest
[EMAIL PROTECTED] wrote:
> Now if I maintain code [I] in flresource.c and put
>
>
> *
> location.x = 20;
> location.y = 0;
> preedit_list = XVaCreateNestedList( 0,
> XNSpotLocation, &location,
>
On Wed, 29 Jan 2003, Angus Leeming wrote:
> It seems to me that you should post a question to some eastern mailing
list
> where you're more likely to find experts at this sort of thing.
>
> Sorry I can't be of more help.
> Best wishes,
> Angus
I can feel your frustration, but here's a quest
On Wednesday 29 January 2003 4:42 pm, [EMAIL PROTECTED] wrote:
> On Tue, 28 Jan 2003, Angus Leeming wrote:
> > Of course, I don't know what I'm doing when it comes to the nitty gritty
> > of creating an input context,
> I don't know about the input context any more than you don't, but somebody
> h
1 - 100 of 143 matches
Mail list logo
