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
___
fltk-dev mailing list
fltk-dev@easysw.com
ht
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
___
fltk-dev mailing list
fltk-dev@easysw.com
ht
On 15.07.2011, at 14:11, nitin wrote:
> 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
I assume you are using FLTK 1.3 ? Earlier versions do not support Unicode. A
>> Fl::set_font(FL_SYMBOL, " Lohit Hindi"); but it now show well
> The Symbol font does normally not contain text characters,
> but only graphics characters.
Nah, he's just pulling a trick I often use myself in my code - he's
effectively "over writing" the FL_SYMBOL font entry (which I never u
> 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,
#include
#include
#include
#include
#include
#include
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:
On 15.07.2011, at 14:39, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>
>>> Fl::set_font(FL_SYMBOL, " Lohit Hindi"); but it now show well
>
>> The Symbol font does normally not contain text characters,
>> but only graphics characters.
>
> Nah, he's just pulling a trick I often use myself in my
It works perfectly well on OS X. I am sorry that I can't say anything for Linux.
On 15.07.2011, at 15:49, nitin wrote:
>
>
> i am using fltk-1.3.x-r8365
> some indian char nt show it well like kdevelop editor show is well
> plz help me
>
___
fltk-
On 15 Jul 2011, at 16:34, Matthias Melcher wrote:
>
> It works perfectly well on OS X. I am sorry that I can't say anything for
> Linux.
I just tested this on my Mac, and in a VM running ubuntu 11.04.
I'm not entirely sure what the correct rendering of the labels is, but:
- Under OSX, the t
On 15.07.2011, at 22:39, Ian MacArthur wrote:
> Why the fltk app appears correct on OSX I am not sure - it may be that the
> Apple text renderer under Quartz is "fixing" things for us, which I find
> unexpected.
Ah, this is a right-to-left script?! FLTK leaves it to the operating system to
re
> > Why the fltk app appears correct on OSX I am not sure - it
> may be that the Apple text renderer under Quartz is "fixing"
> things for us, which I find unexpected.
>
> Ah, this is a right-to-left script?!
Um, no, I do not think it is, though I do not know for sure. I think the
Indic scr
Little addendum:
I just tested nitin's example code on a WinXP box (albeit one with complex text
handling enabled, which is *not* the default for LGC Windows systems, though it
is enabled by default for Asian systems I think) and it seems to be displaying
the text correctly. IIRC the CTL was e
On Jul 18, 2011, at 4:49 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>
> Unfortunately it seems that nitin, the OP, is on a Linux system...
>
> I guess the best bet is for him to pre-format the strings into display order
> before rendering - this is what ICU or PanGo can help with, of cour
Mike said:
> FWIW, I would actually prefer that FLTK handles the conversion to
display
> order (as needed) since otherwise you end up with every Unicode app
> re-implementing the same damn code, and all of the other
> (mainstream/popular) GUI toolkits handle this for the developer as
well.
This
On Jul 18, 2011, at 10:55 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
> ...
> This is true, of course, but could be a fair bit of work for us to make
> it fly - we would certainly be into the 1.4/3.x range for this!
We could certainly introduce Pango or ICU support as an experimental addition
i
On 18 Jul 2011, at 17:02, Michael Sweet wrote:
> We could certainly introduce Pango or ICU support as an experimental addition
> in 1.3 and default in 3.0 for X11. The current situation definitely limits
> how much Unicode can be supported without platform-specific code.
True - though we can d
On Jul 18, 2011, at 4:43 PM, Ian MacArthur wrote:
>> ...
>> Ooops, must have deleted the rest by accident - "This could be used to
>> reposition widgets and change the appearance of widgets."
>
> Oh, I see; so if we determine the text is predominantly r2l for example, we
> could redraw the widge
On 07/18/2011 01:58 PM, Michael Sweet wrote:
> On Jul 18, 2011, at 4:43 PM, Ian MacArthur wrote:
>>> ...
>>> Ooops, must have deleted the rest by accident - "This could be used
>>> to reposition widgets and change the appearance of widgets."
>>
>> Oh, I see; so if we determine the text is predomina
> Pango's api pretty much takes entire blocks of text and a box to put
> them into. It would replace a very high level drawing api in fltk.
>
> The OS/X and Windows systems should be rewritten to call their api at
> this same high level.
On the subject, I think we eventually need the same thing fo
On 21 Aug 2011, at 03:00, Bill Spitzak wrote:
>
> Cairo/Pango are unfortunately not as fast as they should be.
You can say that again!
I had some code where we deliberately contrived to have either "fltk-native" or
Cairo as the back end renderer - sure the Cairo looked nicer (well, except on
On 21 Aug 2011, at 03:26, Evan Laforge wrote:
>> Pango's api pretty much takes entire blocks of text and a box to put
>> them into. It would replace a very high level drawing api in fltk.
>>
>> The OS/X and Windows systems should be rewritten to call their api at
>> this same high level.
>
> On
Hello !
> I recommend using Cairo and Pango on X11 platforms. We need to scrap all
> the legacy X11 api.
I have no problem, when Cairo/Pango is helping FLTK to support Unicode and I18n
better, but please do not drop the standard X11 stuff. I am not an embedded
systems developer, but FLTK is real
On 24.08.2011, at 04:42, Torsten Giebl wrote:
> Hello !
>
>
>> I recommend using Cairo and Pango on X11 platforms. We need to scrap all
>> the legacy X11 api.
>
> I have no problem, when Cairo/Pango is helping FLTK to support Unicode and
> I18n
> better, but please do not drop the standard X1
23 matches
Mail list logo
