Problem with Import of Translate File

FDickschat

Dear all,

we are currently translating our DB to French (FRA) and encountered the follwing strange problem:

When importing a translation file which only contained Texts in the language FRA NAV destroyed our changes to the property OptionString.

Example: In T81, F6 (Document Type) the properties looked like this before the import:

OptionString:         ,Payment,Invoice,Credit Memo,Finance Charge Memo,Reminder,Refund,,,,,,,,,,,,,,Bill
OptionCaptionML: ENU: ,Payment,Invoice,Credit Memo,Finance Charge Memo,Reminder,Refund,,,,,,,,,,,,,,Bill
                 DEU: ,Zahlung,Rechnung,Gutschrift,Zinsrechnung,Mahnung,Erstattung,,,,,,,,,,,,,,Teilrechnung
                 ESP:  ,Pago,Factura,Abono,Docs. interés,Recordatorio,Reembolso,,,,,,,,,,,,,,Efecto
                 Other languages...

After the import of the file which only contained OptionCaptionML in FRA it looked like this:

OptionString:         ,Payment,Invoice,Credit Memo,Finance Charge Memo,Reminder,Refund
OptionCaptionML: ENU: ,Payment,Invoice,Credit Memo,Finance Charge Memo,Reminder,Refund,,,,,,,,,,,,,,Bill
                 DEU: ,Zahlung,Rechnung,Gutschrift,Zinsrechnung,Mahnung,Erstattung,,,,,,,,,,,,,,Teilrechnung
                 ESP:  ,Pago,Factura,Abono,Docs. interés,Recordatorio,Reembolso,,,,,,,,,,,,,,Efecto
                 FRA:  ,Paiement,Facture,Avoir,Intérêts,Relance,Remboursement
                 Other languages...

Obviously the FRA translation does not contain our add-on string. But NAV should never change the property OptionString. But that is exactly what happened. And this is just one example of thousands!


- Has anyone ever encountered this?
- Does someone know why this happens?
- Does someone know how to work around this bug?

Thanks for your help.

kine

Did you somehow modify the translate file? From where you took the file? It seems that the file is from objects without your addon, thus not having the options for your addon... ;-)

FDickschat

Hi Kamil,

Of course you are right that the FRA translations did not contain our addon. We already did this several times with other languages but it never went wrong. The property OptionString is always in ENU and has no ML captions because these are in the property OptionCaptionML

We already have ENU, DEU, ESP (more or less complete), NLD and SVE (partially) in our database and were adding FRA. We did the following:

• From a 4.03FR DB we deleted the ENU translations and then exported the translations into a file. Thereby you get a translation file with FRA only.
• This file was imported into our Development DB.
• Then all languages were exported from the DevDB to a new translation file and were imported into the Merge Tool DB 3 times for languages ENU, ESP and FRA
• The Merge Tool was used to autotranslate ESP and FRA. 2 language files were created from the Merge Tool for the newly translated tokens and were imported into the DevDB

After this procedure the Option String had lost all addons

Ahhh, we just found the problem. This is an explanation what happened:
Until now we thought the problem would be the file from Pers Merge Tool but it is already in the 4.03FR Export file.

This is the original file from the 4.03FR Export:

T81-F6-P2818-L30:Document Type
T81-F6-P8629-A1036-L999:Type document
T81-F6-P8632-A1036-L999: ,Paiement,Facture,Avoir,Intérêts,Relance,Remboursement
T81-F6-P10340-L999: ,Payment,Invoice,Credit Memo,Finance Charge Memo,Reminder,Refund

This is the export from the Merge Tool from Per. Here are the 2 lines for Field 6:

T81-F6-P8629-A1036-L999:Type document
T81-F6-P8632-A1036-L999: ,Paiement,Facture,Avoir,Intérêts,Relance,Remboursement

As you can see the original file did contain the property P2818 (Field Name) and P10340 (OptionString) although I would say it should not be here. Obviously the import did overwrite the property on the field with the information from the file. ](*,)
Why this did not create the same problem earlier when we added ESP and the other languages I don't know.

So for the future we will change your procedure: We will first import the fresh translation file into the Merge tool and then export it from there with only the languages we need.