Inteqam
asked on
Localization of an existing ASP Application
Hi All
I have this English Web application written using ASP and VB,
We use JS, VBS, HTML, VB and SQL database to display everything in the GUI, even Error messages.
I don't want to blame anybody, but when i was requested to move the application into French, I expected the structure to be more comfortable to do that, but Nope,
it was never brought to mind that this application may some day be localized.
I am not the one who is going to translate the application, but i am the one who will extract every single litter written in English to the one who is going to translate, and then return them back.
Now, I need advices.
1- Should I rebuild the system (6-8 Months)
2- Should I do the translation the manuall way (1-2 Months "with bugs properly").
3- Should I use a translating link that translates on the spot, or write one that does so.
4- Any new advices?
Thanks
I have this English Web application written using ASP and VB,
We use JS, VBS, HTML, VB and SQL database to display everything in the GUI, even Error messages.
I don't want to blame anybody, but when i was requested to move the application into French, I expected the structure to be more comfortable to do that, but Nope,
it was never brought to mind that this application may some day be localized.
I am not the one who is going to translate the application, but i am the one who will extract every single litter written in English to the one who is going to translate, and then return them back.
Now, I need advices.
1- Should I rebuild the system (6-8 Months)
2- Should I do the translation the manuall way (1-2 Months "with bugs properly").
3- Should I use a translating link that translates on the spot, or write one that does so.
4- Any new advices?
Thanks
ASKER
thank you evrcool for you reply,
the problem with this is that the application changes nearly everyday, which means that pages are to be changed also and re-translated, is that what you did ?
i mean, when a change happens to a page, what did you do?
the problem with this is that the application changes nearly everyday, which means that pages are to be changed also and re-translated, is that what you did ?
i mean, when a change happens to a page, what did you do?
ASKER
?
Sorry, for some reason I didn't get your reply on 11/19. Anyways, yes, that is what we did when we first started translation. Our app is continually being updated. We have about 20 developers on staff, so we have lots of changes and yes, the French guy did all the updates on the UI as he got to them. Like I said, for the ease of migration, the time lag was a good compromise for us. Now, with everything in one application, they may just see the English version of it for a few days, before it gets translated. But at least with the .NET, everything is in one application, so for the funcationality, there is no lag.
ASKER
mmmmmm...
but we will have a problem when we may need to translate it to another new language, we'll have to re-invent the wheel
but we will have a problem when we may need to translate it to another new language, we'll have to re-invent the wheel
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
you helped, thank you
We thought about using a translation link, however, those don't translate too well. At best it comes out in "broken" French, at worse, it comes out offending someone. To test, do a search in google for something in French, then translate it at any translation site on the web.
Anyways, there is what I have been through and am happy the way we went.