#include<FL/Fl.H>
#include<FL/Fl_Window.H>
#include<FL/Fl_Button.H>
#include<FL/Fl_Input.H>
#include<iostream>
#include<string.h>
using namespace std;
// fltk-config --compile multilingual.cxx
int main(int argc, char **argv)
{
int i;
Fl_Button *btn[5];
Fl_Window *wnd;
Fl::visual(FL_DOUBLE|FL_INDEX);
wnd = new Fl_Window(440, 470, "emuster");
Fl::set_font(FL_HELVETICA, " Lohit Hindi");
btn[0] =new Fl_Button(40, 40, 170, 30),
btn[0]->label("डाà¤à¤¨à¤²à¥à¤¡");
btn[0]->labelfont(FL_HELVETICA);
btn[1] =new Fl_Button(40, 90, 170, 30),
btn[1]->label("à¤à¤ªà¤¸à¥à¤¥à¤¿à¤¤à¤¿"); //it not show like my kdevelop
editor show
//http://www.packetizer.com/labs/cs/characters.html plz use this link put
this"à¤à¤ªà¤¸à¥à¤¥à¤¿à¤¤à¤¿" and view it Unicode
btn[1]->labelfont(FL_HELVETICA);
btn[2] =new Fl_Button(40, 140, 170, 30),
btn[2]->label("à¤à¤¾à¤°à¥à¤¯ पà¥à¤°à¤à¤¤à¤¿ "); //it not show like my
kdevelop editor show
btn[2]->labelfont(FL_HELVETICA);
btn[3] =new Fl_Button(40, 190, 170, 30);
btn[3]->label("à¤
पलà¥à¤¡");
btn[3]->labelfont(FL_HELVETICA);
wnd->show();
// Fl::set_font(FL_SYMBOL, "Kochi Gothic");
// Fl::set_font(FL_SYMBOL, " Lohit Hindi");
// Fl::set_font(FL_SYMBOL, "lohit marathi");
// Fl::set_font(FL_SYMBOL, "lohit Devanagari");
return Fl::run();
}
/* end of file */
i am using fltk-1.3.x-r8365
some indian char nt show it well like kdevelop editor show is well
plz help me
> > Hi
> > "à¤à¤ªà¤¸à¥à¤¥à¤¿à¤¤à¤¿" if this my label & i use
> > Fl::set_font(FL_SYMBOL, " Lohit Hindi"); but it now show well to me on
> > screen. bcoz it,s cutting char it nt in English style char
> > so plz help me
> >
>
> I'm not understanding your question, I am afraid to say.
>
> Can you post a small, complete, compileable example that shows the problem,
> please?
>
> Maybe modify the "hello" example from the test folder to show your label,
> then perhaps describe what you do get, and what you expected to get.
>
> Some notes:
> - fltk-1.1 will not render utf8 strings, so I assume you are using fltk-1.3.
>
> - flkt does not do any compositing or language specific formatting of the
> passed utf8 strings, rather it assumes that they are already composed in
> display order with the appropriate glyphs. If you need to composite strings
> from some canonical ordering into display order, for languages that require
> complex compositing, then you will need to use ICU or perhaps PanGo to
> prepare the strings before passing them to fltk to be displayed. This is
> particularly true for the Indic languages, though is also true of the semitic
> languages (Hebrew, Arabic), to a lesser extent.
>
> Note: for LGC languages (which I think covers most of the fltk devs) it is
> *usually* the case that the display ordering of the glyphs matches the
> canonical ordering in the string, but this is often not the case for complex
> languages.
>
> There is some (probably apocryphal) suggestion that this simplification of
> rendering in the LGC languages came about with the widespread adoption of
> movable type, which could not easily cope with the variations... Where the
> written text remains predominantly hand-crafted, the text formatting tends to
> be rather more elaborate...
>
>
>
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
