Hi,

I'm trying to make a self-maded french translation of the Invision Community strings.

For the moment I've translated ~5900 strings (that makes only near 30% of the total number of strings to translate... 😅). I work in a sandbox -TESTINSTALL community instance in order to avoid being polluted by plugins and any other third party application. So when I want to test it in my main community, I try an export from the development sandbox and an import into the main community...

The generated XML translation file seems to contain the right number of strings... But once imported, I got only near the half of the strings translations (~3000 strings) working and seen as "translated" in the translation interface of the main community...

I've not any "debug" tool to get any clue on what's going on there... So, please, somebody can help me with it ?

Thankyou for your attention and best regards,

D

Edited February 16, 20223 yr by Dexter_X

Please be advised there is limited support we can provide with custom translations but can investigate if this is an issue with the product export/import process.

• Are the other strings showing as outdated?
• Are both installations on the same version?
• Are any language strings being modified or have duplicates in any custom add-ons which may be creating conflicts?

Thankyou for your answer.

I'm not asking help on the translation, but help on the import/export. I've tried from a Macbook and from a PC-W10, in both the behavior is the same.

I've noticed while exporting the export window remains open (with the turning "wait" animation) forever...

 

To answer your questions :

- in the sandbox there are no outdated stings, but I've just taken a look and yes, in the imported side, the ~3000 imported strings are all marked as outdated (?!) ;

- yes, both installations are on the same version ;

- I don't understand the last question...

18 minutes ago, Dexter_X said:

in the sandbox there are no outdated stings, but I've just taken a look and yes, in the imported side, the ~3000 imported strings are all marked as outdated (?!) ;

This would indicate that these strings have changed since you have made your translation so you would need to review them. With the translated and outdated do you have your full set of strings?

4 minutes ago, Jim M said:

This would indicate that these strings have changed since you have made your translation so you would need to review them. With the translated and outdated do you have your full set of strings?

In the sandbox, which is on the same version as the main/production community, those strings are not indicated as outdated : there are no outdated strings at all in the sandbox. But once uploaded in the main/production community, the imported strings are all displayed as outdated and only half of the translated strings are imported...

In other words : the translated and the outdated are exactly the same set of strings.

Edited February 16, 20223 yr by Dexter_X

All the same applications, etc... are installed on the test as production? Are you able to give us access to the export?

Nope : the sandbox/test/development installation does not have any third party application installed. The destination/production/main community does have a certain amount of third party applications installed.
The export file seems to contain all the translated strings (~5900 lines in it). It seems the import procedure is the one having troubles (?). How can I send you the export file in a secured way ?

When you are trying to import a language pack, are you doing this without developer mode enabled?

Hi,

None of the communities are set in developper mode : both are set in standard user mode.

Could I also confirm you are exporting and imported on the same version. If so, please feel free to PM me the file so I can take a look

Thankyou. Yes they're both on exactly the same version. I'll PM you the file. Thankyou again.

Please could you provide me with some example items that are not showing as translated?

Yes, there are a lot on the pages application, for example :

. content_add_page

. content_add_folder

 

Please provide access to the site you are creating the translation on. I am also not seeing it on our end

ok, I've set the information into the Client Area, instead of the information for the main site.

Please, consider that sandbox/dev/test site is not backed up so be careful : I don't want to loose all the translation work already done.

Edited February 18, 20223 yr by Dexter_X

10 minutes ago, Dexter_X said:

ok, I've set the information into the Client Area, instead of the information for the main site.

Please, consider that sandbox/dev/test site is not backed up so be careful : I don't want to loose all the translation work already done.

Please ensure you back up. While there isnt really anything that should go wrong on there, we cannot really be responsible for you having no backup if it does

ok, I'm on it, I'll post a new message when it is done.

ok, backup done, you can "play" with the sandbox... 😶

Please could you check the htaccess? It appears to be incorrect

sorry, my fault, it should be ok now

On 2/18/2022 at 5:41 PM, Dexter_X said:

sorry, my fault, it should be ok now

No problem. Im in there now. Which language pack is it?

In the sandbox it is the first one, called "Français_DEV"

I have created a ticket for you on this, so one of our developers can see whats going on for you