[Foxgui-users]Is anyone actually using FOX's Unicode support?

[l***@knology.net]

I'm trying to do some planning about how to support the new Unicode stuff in
FXRuby; not so much how to implement the internals, which I think will be
straightforward, but how to advise people to use it (i.e. in terms of
examples and tutorial information). In the past, I've had more than one
person tell me that they'd be using FOX (or FXRuby) if only it had support
for Unicode. But when pressed for more information about how they would take
advantage of it in their application(s) they didn't have much to say. In
other words, I am suspicious that for a lot of people this is just another
ambiguous box to check off on a feature list.

So my challenge (or request) is this: If you are actually *using* the new
Unicode stuff in your application, could you post your experiences here (or
to me by private e-mail if appropriate)? I'm curious to hear about how
people are using it in practice, and what problems (if any) you've run into
-- that sort of thing.

Thanks.

[Lothar Scholz]

Hello lyle,

lkn> I'm trying to do some planning about how to support the new Unicode stuff in
lkn> FXRuby; not so much how to implement the internals, which I think will be
lkn> straightforward, but how to advise people to use it (i.e. in terms of
lkn> examples and tutorial information). In the past, I've had more than one
lkn> person tell me that they'd be using FOX (or FXRuby) if only it had support
lkn> for Unicode. But when pressed for more information about how they would take

There is a huge problem as Ruby is not very good in Unicode. I don't
even know if we have any codecs in 1.8.2 to translate between this and
other codes. I also think that even UTF-8 ruby source code might be a
problem with the current interpreter (BOM sequence at beginning - i
remember a message about this on the core dev mailing list).

lkn> advantage of it in their application(s) they didn't have much to say. In
lkn> other words, I am suspicious that for a lot of people this is just another
lkn> ambiguous box to check off on a feature list.

No. If you ever need to display XML file contents or input at least
some text then this is not a feature list item, but a real pressure for users.
And the reason why many people still use the TK bindings instead of FOX.

lkn> So my challenge (or request) is this: If you are actually *using* the new
lkn> Unicode stuff in your application, could you post your experiences here (or
lkn> to me by private e-mail if appropriate)? I'm curious to hear about how
lkn> people are using it in practice, and what problems (if any) you've run into
lkn> -- that sort of thing.

Don't think that anybody is really using it know.

On windows i would be almost sure as there it's a huge step back at
the moment as long as keycodes are not translated correctly.
We will see, but i think i'm quite right with the expectation that
using unicode with FOX will still have to wait until spring next year.
At least for mission critical applications.