> I am using nano-X which is simulating the X11server.
Ah, OK.
My glib answer here would be that you should dump nano-X and get a proper X11
server, it will save you a whole world of pain in the longer term.
Unless your hardware is really feeble, the KDrive/TinyX stuff will Just Work
and be much more standard, so worth the effort to get it going. Really, do
yourself a favour...
> I am using gcc-arm-
> linux and g++-arm-linux to build the toolchain. The problem with the
> linking error is now sorted out. Since I was using nxlib it should be the
> one that define the XIMOfIC and other functions. Strangely the nxlib 0.45
> and 0.46 both do not do that. So I got the latetst source code (released
> on 29th July 2011) and built the nxlib which solved the problem. What
> those guys have done is added the functions XIMOfIC,XLocaleOfIM and
> Xutf8LookupString in stubs file. Basically these function are implemented
> as stubs and returns zero.
>
> Now that I was able to build the application I went ahead and tested it on
> the target. All seems to work fine but I was hit with a new problem. Now I
> cannot see any text on my application.
How do you have fltk configured?
You probably have to configure it to disable XFT and use the older Xlib font
interfaces, I suspect, to get it working on nano-X. (As you may infer, I no
longer use nano-X for anything so do not know where they have got to
recently...)
The fltk-1.3 stock builds have XFT enabled by default (fltk-1.1 had Xlib by
default) so you may have to "configure --disable-xft " to get your fltk tree
the way that you'd want. Maybe...
Though fonts and so forth under nano-X may be tricky anyway, so you need to
ensure you have the fonts loaded and so forth on your target, or built into
your server...
> So I think because XIMOfIC,XLocaleOfIM and Xutf8LookupString fucntions are
> implemented as stubs, the fltk is unable to render the text. Am I correct
> here?
Possibly, though see above.
Also, note that fltk provides its own implementation of Xutf8LookupString (it
is in the src/xutf8 folder) and you SHOULD be using that in preference to the
nano-X stub, since it does do more or less the Right Thing.
You need to ensure that the fltk versions of the various Xutf8 methods are
linked in before the nano-X stubs, so that the functionality is provided as
needed. (At least for the ones we have hooks for, we don't have the means to
fake up the IM stuff for example..!)
> Next things is how important are XIMOfIC,XLocaleOfIM and Xutf8LookupString
> function to the new fltk 1.3.0 for UTF8 support and what exactly are their
> functions?
There's a simple implementation of XUtf8LookupString in src/xutf8/utf8input.c
so you can see what it actually does there. Or check the man pages for what the
"official" version does:
http://linux.die.net/man/3/xutf8lookupstring for example...
Basically, the IM (Input Methods) display some UI mechanism that allows the
user to input text that can not be directly typed on the installed keyboard
(e.g. entering Chinese or Japanese texts on a ASCII keyboard) and then pass the
composed text back to the calling application.
The IM UI is usually provided by the host OS or windowing system, so the fltk
app would not know the details of it, it simply gets text through the IM
methods and reads them into the app, thereafter they are treated as if they
were "typed" normally at the keyboard...
So, depends on what you want to do. If you are mainly displaying LGC group
languages, you probably do not care if the IM works at all or not.
For Indic or Semitic languages, you might want the IM to work. Not sure, may
depend on what setup your users have.
For CJK languages, you probably need the IM to work...
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
