[ros-kernel] l18n in react os
iastrubn at actcom.co.il
Thu Oct 9 15:55:27 CEST 2003
áéåí øáéòé, 8 áàå÷èåáø 2003, 22:45, ðëúá òì éãé KJK::Hyperion:
> At 01.33 09/10/2003, you wrote:
> >I was wondering what will be the approach in this project for i18n. The
> >approach in MS world is to recompile with new strings.
> no. Microsoft used to maintain separate builds for each language, but most
> other vendors didn't. Currently, even Microsoft has abandoned the old model
> >Is it possible to use gettext()?
> I want to be clear: I'm not too fond of excessive "GNU-phily". gettext
> isn't standard on UNIX ("GNU isn't UNIX"...), neither on Windows, both of
> which define simple, efficient (and very similar) ways to localize strings.
> And I don't think the complexity of gettext is justified by anything
> simpler than an office suite. We don't *need* gettext, we shouldn't paint
> ourselves in a corner so happily about it. On top of that, add the fact
> that ReactOS, being Windows, will have to support the MUI API, sooner or
> later, and we'll likely end up using that
I would like to disagree with you if you don't mind.
Using gettetxt means only adding I18N() before each string. for example:
The string extraction is done automagically by the auto* magic, and trust me
the translation is easy, since you have a few programs which can edit them
graphically (google for poedit, they have a windows version).
I am sorry, but editing strings inside DLL's does seem intimidating to me now.
About you other mail.
>>I will not even start talking about rtl and bidi yet.
>Windows supports RTL layouts perfectly: just set the appropriate style bit
>for a window, and everything in the window's DC gets automatically
>mirrored. In most cases you don't even need to touch your code. BIDI?
>recent versions of Windows have added support for complex scripts - you
>could even write in alternate ltr-rtl mode, or in vertical. We don't have
>to invent anything: like usual, those kind folks at Redmond have already
>done all the boring research for us
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. (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).
Don't worry, wine does already implement BIDi with the use of ICS (a library
developed by IBM). I will get into that when time arrives. Don't worry.
Details will come in time (if someone request) since it's really not needed
You talked about a style bit which mirrors a window. Please send me a source
code which demonstrate this. If I am correct it will only mirror the window
frame, not the client side (that's what I remember from my experience). IMHO
it looks really ugly and should not be used, since it confuses people a lot
(again from experience).
Rick Parrish <rfmobile at swbell.net> wrote:
>If they are win32 dialogs, then each locale gets it's own dialog
>resource - with appropriate size and dimensions.
Does that means that for each language the translator needs to resize the
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...
diego, 13 Tishrey 5764
Please avoid sending me Word or PowerPoint attachments.
More information about the Ros-kernel