Best way to use solution build in the local language

andrejsm · 2006-06-02

Hi,
Our partners developed great solution, but it is writen in local language (all table field names, captions, variables, comments - all is in foreign language ](*,) )
There is more then 150 tables and it is quite big solution.
We got no time to completely rewrite solution. How do you think, is it possible to translate just field captions and try to use solution as it is? Or is it better to try something else? :?:

Marije_Brummel · 2006-06-02

We've encounterd the same problems with some german add-ons. Luckily we have some knowledge of the german language.

There are tools to translate all captions, but not the fieldnames. Maybe you can contact MS about this.

If you are going to support this solution my advise would be to translate to english otherwise bugfixing will be a huge problem in the future.

Alex_Chow · 2006-06-02

You won't have to rewrite the whole solution. Just add on to the caption property of the fields.

Of course, for 150 tables, that's a lot of fields to modify the caption for.

Marije_Brummel · 2006-06-02

deadlizard wrote:

You won't have to rewrite the whole solution. Just add on to the caption property of the fields.

Of course, for 150 tables, that's a lot of fields to modify the caption for.

What about debugging or bugfixing in the future? What language is it? Do you understand the language? Otherwise debugging will be hell

Alex_Chow · 2006-06-03

I'm not talking about changing the field name, just the caption property.

Regarding debugging, a developer should easily find the field in question now that the fields can be searched in teh C/AL code.

andrejsm · 2006-06-06

Hi,
Solution is in foreig language, which is not very popular in our country and more over, there is no one who know this languange in our company

It will be necessery to support and modify this solution in the future.
We decide to translate solution using Navision Localization Workbench. At the end of this process we will have field names, variables e.c. translated to english. Then we will test whole system and decide which parts to rewrite or disable.
And one more thing, now I see why it is necessary to use best practices and write code in the right way. It is huge pain to work with excelent solution with crappy code :evil:
More advices?

kriki · 2006-06-20

Some "Dirty" trick:
Create a form on the field table (a system table).
In it you can rename the fields to your own language. You don't need to recompile anything because in the compiled objects, only a reference to the field-ID is kept.
And when you later open an object that uses fields translated in this way, you will see them with the name.
Of course before renaming the fields, you must be sure that all objects are compiled in the DB.

Marije_Brummel · 2006-06-20

Nice trick; I'll try it sometime =D>

kriki · 2006-06-20

And with this dirty trick, you can also add fields and delete fields!

Balello · 2006-06-20

You can also add object in object table. And you can create runtime a table with fields and, if I remember good,without "commit" you can use the new variable configuration on a local variable (it's declared runtime....). But I never find a way to use this tricks.

Talking about the first post.... I think that a good solution center should never use local language when writing,commenting and giving name to variables.....

Moreover: I recently studied for Dev II and the manual marks on the fact that VIRTUAL table cannot be changed....... But Field and Object are considered as Virtual table..... What's wrong with that???? What kind of tables are those???

:-k

kriki · 2006-06-20

Balello wrote:

Moreover: I recently studied for Dev II and the manual marks on the fact that VIRTUAL table cannot be changed....... But Field and Object are considered as Virtual table..... What's wrong with that???? What kind of tables are those???

But they are also real tables. They have a dual character...

Kowa · 2006-06-21

BlackTiger wrote:

Beleive me,this is NOT "great solution". And they are not good developers. Because in developer's guide wrote: use for development ONLY english language and local language for captions only.
-

If you adopt code written for 2.X Versions, it will usually be in local language.
All of the standard code was written in local langage too up to Version 3.

Marije_Brummel · 2006-06-21

Yes, we also have some older solutions still developped in Dutch. They were developed years ago before the ML options and we did not have time yet to translate to english

But this does not mean the solution is bad! It is just in Dutch, thats all.

andrejsm · 2006-06-21

We decided to use NLW and translate all necesary objects.
I think we already translated about 50% of tables. It is not so hard as it looks like, but it is very time consuming.
Some terms like Vendor Ledger Entry or Finanche Charge Memo could be translated only by finding this meanings in standart Navision Functionality, where they have multilanguage captions. Some terms still secret for us :oops:
This week we met "Error 9 in module 24" problem ](*,) . Some objects already have fields with multilanguage captions. And when we are trying to import translation file this error occur. Our solution for this problem is to delete ENU language module in objects which have translated fields.
I think every programmer should try to localize some code from foreign language :twisted: . After that he will write briliant code with all these requirements from developer's guide!

kriki · 2006-06-21

Kowa wrote:

If you adopt code written for 2.X Versions, it will usually be in local language.
All of the standard code was written in local langage too up to Version 3.

Not always true. The Belgian version was completely multilanguage since 2.01!
And the DB had 3 companies in it (a Belgian Dutch, Belgian French and English)!
Imagine my surprise when I saw a 2.60 Italian DB STILL IN ITALIAN!

Marije_Brummel · 2006-06-21

Yes, this is all true, we started using the belgian database for international implementations!

BUT, believe it or not, there are people here that also have worked with version 1.x 2.0 or even DOS.

There were some great solution already back then. Yes there was NAV life before 3.x

[sorry O:) ]

kriki · 2006-06-21

BlackTiger wrote:

Yes. I'm disagree too. Even 2.01 had multilanguage capabilities (quite hidden from the public).

But not from the Belgian public.

Marije_Brummel · 2006-06-21

Yes, back than there were 3 countries with ML capbilities

Belgium Canada South Afrika (correct me if I'm wrong)
Ok that was history class for today

Kowa · 2006-06-21

I know that that there were some 2.X multilanguage Versions, Luc mentioned this 3 years ago, that's why I added "usually". Sadly not in the german versions, at the moment I'm translating 2.6 add-ons to implement them into 4.0 Upgrades. This may take some weeks...

kriki · 2006-06-22

Kowa wrote:

I know that that there were some 2.X multilanguage Versions, Luc mentioned this 3 years ago, that's why I added "usually". Sadly not in the german versions, at the moment I'm translating 2.6 add-ons to implement them into 4.0 Upgrades. This may take some weeks...

Maybe this can help you speed up the work: http://www.mibuso.com/forum/viewtopic.php?t=12223

Best way to use solution build in the local language

Comments

Categories