How to translate Captions?

mfabian · 2000-08-07

I'm using Version 2.60 Swiss-German.

If I create a Form using my Swiss Navision License, Multilanguage Captions are stored as

DES="My Title"

If a non-Swiss User tries to import the FOB in Text-Format he receives an error telling him that he has not the right to use Language "DES" (Deutsch, Schweiz) which makes sense in a way as Germans use language "DEU" or americans language "ENU"

You can try if you want. See my posting "Get/Set Filename using COMDLG32.OCX " from July 28th and try to import the object in your database.

My question is: How can I create an object which can be imported by ANY user, no matter what language(s) he has licensed? Do I have to translate the MLCaptions to EVERY language respectively language version?

Or Do I really have to "Translate" the MLCaptions like

DES="Mein Titel";DEU="Mein Titel";ENG="My Title";ENU="My Title";FRA="Ma titre"

in order to cover Swiss-German, German, English UK, English US and French Standard?

Marcus Fabian
m.fabian@thenet.ch
+41 79 439 78 72

Dave_Cox · 2000-08-07

Marcus

Does your fob include codeunit 1?
I had a problem with a project converting a US Database to GB!
I could not open the main menu
It was because of the Language Code Integer in Codeunit 1

ApplicationLanguage() : Integer
// GB Language
EXIT(2057);

MindSource (UK) Limited
Navision Service Partner

david@mindsource.co.uk
info@mindsource.co.uk

mfabian · 2000-08-08

Hi David,

>>Does your fob include codeunit 1?<<

No, should it? I can't imagine that changing the GLOBALLANGUAGE for the whole database is required only to import ONE foreign object, is it?

Marcus Fabian
m.fabian@thenet.ch
+41 79 439 78 72

Dave_Cox · 2000-08-08

Fabian

I have opened databases from other counties with my GB licence.
The language Integer in code unit 1 gives the error message you decribed.

I change that and have no problems with Importing or Exporting fobs.

Maybe it's because the fob is in text that is causing the problem!

I downloaded you control the Navision fob Imported to 2.50GB with no error

The txt fob gave the following error message

DES=Control Filename: make sure to have the -lookup' property set to yes you find an example in how to use the codeunit at filename on lookup)' is not an option

Helpful error message!

The Import stopped at line 35

I then exported your fob as text but could not then re-import it
I got the same error message
CaptionML=2055=Control Filename:
I tried changing the caption no luck

It looks like the text fob will not Import if a different Language, one for the Navision A/S people

[This message has been edited by Dave Cox (edited 08-08-2000).]

[This message has been edited by Dave Cox (edited 08-08-2000).]

[This message has been edited by Dave Cox (edited 08-08-2000).]

mfabian · 2000-08-09

Dave,

That's exactly what I mean! a US programmer e-mailed me as he had problems importing my comdlg object as text with the error message you describe. I could easily solve this problem by giving him the advise to change the CaptionML from "DES" (German, Swiss) to "ENU" (English US) and it works.
Same would apply for you: If you Change CaptionML=DES to CaptionML=ENG you would be able to import the object and compile it.

And this is exactly the point: How to create an object which can be imported and compiled by EVERY user no matter what language he has licensed according tu codeunit 1

Marcus

Marcus Fabian
m.fabian@thenet.ch
+41 79 439 78 72

Dave_Cox · 2000-08-09

Fabian

It seems the only way until Navision sort out the text Importing would be to Create a fob Object for each Version to be Included in your zipped file.
2.00.fob, 2.01.fob, 2.50.fob and include the text version for reference.

It is hard when offering Objects to decide which version is best to use, If you offer an Object at the lowest compatable version you can load it into Cronus and convert the Database saving the Object at each Version until you reach 2.50 of Course then you need the text file, It takes abouts 20 minutes and could be saving hours or days of Development.

A simple Instruction in the readme file advising a find and replace for the ML problem would be enough, the object are offered free!

mfabian · 2000-08-10

Dave,

Sadly enough I'm afraid that you are right. I really would wish for a solution which would allow me to translate all Captions easily to - let's say - German, English and French allowing me to produce an add-on which could be imported by everybody and be understood by 90% of the users.

I wonder what all these NSC's are doing, which live on selling their add-on's. Do they really only sell their products within their country? Does that really mean that every add-on has to be newly created for EVERY country? What about the target (and it MUST be a target for a product like Navision which claims to be international) to spread the pearls of wisdom to the whole community of users? <img border="0" title="" alt="" src="images/smiles/icon_rolleyes.gif" />

Marcus

Marcus Fabian
m.fabian@thenet.ch
+41 79 439 78 72

Dave_Cox · 2000-08-10

Quote:
I wonder what all these NSC's are doing, which live on selling their add-on's. Do they really only sell their products within their country?

Native Fobs are not a problem across the different localisation, only in the text file format!

Howdy, Stranger!

Quick Links

Categories

How to translate Captions?

Comments