[openbeos] Re: Coding Guidelines, translations

From: "Marcus Overhagen" <dos4gw@xxxxxx>
To: openbeos@xxxxxxxxxxxxx
Date: Mon, 12 Nov 2001 03:15:02 +0000

"Erik Jakowatz" <erik@xxxxxxxxxxxxxx> wrote:
>
>First, what mail client are you using, Marcus?  I think virtually every 
I'm using Scooby for BeOS, seems to work fine so far,
and looking into the list archive, my emails don't look strange.
If somebody else has a problem reading my email,
please email me off list.

>single one of your mails to the list end up looking like a vast sea of 
>boxes with the occasional cross thrown in. =P  "Thankfully, I use BeOS; 
>all I have to do is query by attribute and open the garbled mail in 
>Eddie, and I'm off to the races!" ;)
UhOh, Postmaster appended a couple of empy lines on your email :)

>Second, though there is a *lot* more to localization than translating 
>strings, using the translator API to provide a way to do this is bloody 
>*brilliant* -- I mean, that's what the API is there for, no?  Doing 

Well, I'm not sure if it is really wise to extend the BTranslatorRoster
class to do it, but I believe it is a much better idea to create a service
class similar to BTranslatorRoster or BMediaRoster for this purpose,
instead changing all other classes.
For example, you would need for example functions to inquire how
date, time or currency information needs to be displayed,
in which class would this belong? BView? No. BApplication? No.
and so on. Better use a Roster for all this.
The remaining problem is font display, for example when

        tfel ot thgir deyalpsid eb ot sdeen gnirts a

this additional functionality must be integrated in the interface
kit classes somehow. But later.

>translations? =)  I've been scratching my head the last couple of weeks 
>(in a low priority background thread) about how to integrate string 
>translation functionality into the interface kit and didn't *once* think 
>of this route.  Nice going, Marcus -- you going to implement this for 
>us? ;)
No, seriously not. It was just an idea I had,
I have enough other work, including media kit :)

regards
Marcus

[openbeos] Re: Coding Guidelines, translations

Other related posts: