[ros-kernel] l18n in react os

[KJK::Hyperion]

At 16.55 09/10/2003, you wrote:
>I would like to disagree with you if you don't mind.
>Using gettetxt means only adding I18N() before each string. for example: 
>"I18N("hello world!").

I know gettext isn't that trivial, and you know it too. If that's all 
gettext does, one doesn't see why it's that necessary, right?

>I am sorry, but editing strings inside DLL's does seem intimidating to me now.

what's the difference? you'll still need an editor of some sort. And once 
you have an editor, it doesn't matter much if the format is DLL or whatever 
else

>I am sorry to inform you that BIDI is much more complex that that. I can 
>try and explain what is it, but it will be long. Maybe another thread.

the RichEdit 3.0 control from Microsoft supports all of that, and more. I 
wouldn't be surprised if you never heard about it: Microsoft always does 
the good stuff quietly (what are they, ashamed of not sucking? is sucking 
their corporate standard? their mission statement? figures)

>(what if you mix languages in one line for example? try moving the cursor 
>in the first line of this mail, opefully you use some mail client which 
>supports unicode).

nobody has found a good solution for this - _in plaintext_. Rich text isn't 
affected, and this is the strongest argument in favor of HTML mail

>You talked about a style bit which mirrors a window. Please send me a 
>source code which demonstrate this.

I'll pass. Too much of a hassle. The style is WS_EX_LAYOUTRTL: note it down 
and try it by yourself, whenever you feel like. You'll see how it Just 
Works (TM). I've personally tried on a couple of programs of mine, and it 
worked seamlessly (but I actually understand the coordinate model of the 
Windows GDI, I'm minority)

>If I am correct it will only mirror the window frame, not the client side

It mirrors the device context of the client area, therefore it mirrors all 
painting operations and the coordinate system itself - all children windows 
get automatically mirrored, in position and content

>Does that means that for each language the translator needs to resize the 
>widgets manually?

you are looking at it from the wrong angle: it means that the *resource 
editor* has to do it. Dialogs have a static layout by design. Just get over 
it, it's not going to change anytime soon (but, like I said, you don't 
write applications with Win32 dialogs. You write, well, dialogs. Property 
sheets, mostly)

>As you can see, I do come from Linux world so I may think differently then 
>you sometimes. That is not always bad, I may have good ideas once in a time...

we have no time for good ideas, sorry. We are rewriting Windows, here