Re: Now it's more than a month since update 2, still no update 3.
- From: OBones <obones_gfe_@xxxxxxxxxxxxxx>
- Date: Mon, 11 Apr 2005 17:39:52 +0200
Will DeWitt Jr. wrote:
OBones wrote in <425a8858@xxxxxxxxxxxxxxxxxxxxxx>:
That is handled by another group inside Borland, so that should not
interfer with a update 3 for the english version.
You obviously have no idea how localization is done in large companies...
Perhaps you could enlighten us.
When you write code, you must always keep in mind that it will be used with different charsets, numbering systems and so on.
If you don't, then you require a team to do what's called "globalization", that is make the code ready to be used in different locale settings.
Problem is that doing this after the initial development requires a lot more time and resources. However, doing it while you develop makes the the development time a bit longer and the initial English release is delayed by that time.
After the code is ready for localization, you then give it to the localization team that should not have to change any code (if work was done correctly, in practice they have to)
Hence you have to decide between two options:
1. Do I delay the initial English release by a few weeks and have the localized versions just after it (a couple of days); or
2. Do I release the English version ASAP (to keep most customers happy) and have the localized versions ready much later (up to six weeks).
Note that it is not always as clear of a cut as this, it's more like a fuzzy logic thing.
I have no direct idea as to how this is managed at Borland (how could I?) but I suspect they chose an approch closer to option 2 than to option 1. Microsoft also chose such an approach for the critical updates releases.
I'm a great fan of option 1, and I push as much as I can for it, but it's sometime impossible to make a developer realize and understand that not everyone in the world uses a QWERTY keyboard and a dot as decimal separator.
And last but not least, you also have to take into account the worthiness of an update when the next release is not too far away. I have no idea if it is or not, but who know, that might be the reason why we see this delay. Something like:
- We'll skip Update 2 for German and French and directly make U3 for all languages; or
- Next Delphi is about 2 months away, let's wait for it.
With the very few information we get here on that matter, the first solution looks like the most probable to me. But once again, I'm not a Borland employee, I'm not even close to any of them, hence I'm just speculating here.
Cheers
Olivier
PS: I don't know if I made this any clearer, please do not hesitate to ask more questions.
.
- Follow-Ups:
- Re: Now it's more than a month since update 2, still no update 3.
- From: Stephane Wierzbicki
- Re: Now it's more than a month since update 2, still no update 3.
- References:
- Now it's more than a month since update 2, still no update 3.
- From: Atle Smelvær
- Re: Now it's more than a month since update 2, still no update 3.
- From: Michael Stum
- Re: Now it's more than a month since update 2, still no update 3.
- From: Atle Smelvær
- Re: Now it's more than a month since update 2, still no update 3.
- From: OBones
- Re: Now it's more than a month since update 2, still no update 3.
- From: Will DeWitt Jr.
- Now it's more than a month since update 2, still no update 3.
- Prev by Date: Re: Hungarian Notation
- Next by Date: Re: Migrating to Delphi 2005 .NET
- Previous by thread: Re: Now it's more than a month since update 2, still no update 3.
- Next by thread: Re: Now it's more than a month since update 2, still no update 3.
- Index(es):
Relevant Pages
|
