You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you cannot use trademapper in any other langauges. It will not translate via a machine translation tool like Google translate partly because the language strings are uploaded after the website is loaded from the CSV. Trademapper looks for the terms it needs to populate the map with data in the CSV file, but these terms must first be written in English.
So one problem is that if a CSV file is not in English then Trademapper does not recognise the descriptors in the data (for example 'family' so if it was in French 'famille' it would not upload the CSV)
Another problem is that the country codes will be replaced with country names which will also need to be translated.
Translation could take place at 3 different points:
The HTML of the website at the point when it is loaded
The CSV file before it is loaded
The end product of the data preloaded into Trademapper
Another possible other solution would be to have customisable colum mapping so that Trademapper could accept any terms from the CSV, but these would have to be defined when the CSV is uploaded.
The text was updated successfully, but these errors were encountered:
Currently you cannot use trademapper in any other langauges. It will not translate via a machine translation tool like Google translate partly because the language strings are uploaded after the website is loaded from the CSV. Trademapper looks for the terms it needs to populate the map with data in the CSV file, but these terms must first be written in English.
So one problem is that if a CSV file is not in English then Trademapper does not recognise the descriptors in the data (for example 'family' so if it was in French 'famille' it would not upload the CSV)
Another problem is that the country codes will be replaced with country names which will also need to be translated.
Translation could take place at 3 different points:
One solution to this could be to make a bundle with alternate translations of terms. Using this:
http://requirejs.org/docs/api.html#i18n
Another possible other solution would be to have customisable colum mapping so that Trademapper could accept any terms from the CSV, but these would have to be defined when the CSV is uploaded.
The text was updated successfully, but these errors were encountered: