ExcelDna.IntelliSense(64).XLL and XML multi-languages version 1.2

[AL7Seven]

Hi everyone
Just to announce that I did version 1.2 ExcelDna.IntelliSense-and-XML-multi-languages
I changed and correct few stuff.

The main one is the internal DnaIntelliSense function Refresh that is working now. So, in the module SetCountry_md, I replace my ReLoadDNA function (but let it in place just in case) with RefreshDNA
Know you may install your UDF in a specific directory named like your function name. Like that the program will find it itself.
The ExcelDna.IntelliSense(64).xll files should to be in the default Add-ins directory

ToDo … DONE!!

Correct the encoding problem. The messages are not correctly displayed depending the country
Thinking about making XML-multi-languages as class and, may be, itself as a UDF
Let me know what you think about.
Have a look 😁

[govert]

If you have the external xml files, might it be simpler just renaming the language-specific file to the expected name, and then calling the Refresh, instead of using the CustomParts embedding?

[AL7Seven]

Do you mean we don’t need to load xml content in the CustomPart?
So why I found it in?
Something I missed about the mecanism of XLM used?
Do you think there is anything todo with encoding?

About what I am doing in the program....

It’s nearly what you suggest.
If you look to my repositery, you will see that we have one XLM per country.
So, I copy the existing country xml file with the default xml file name.
Then I upload the xml content into CustomPart and call dna refresh function.
That’s all.

But I forgot to test if Refresh function does that job for me (Oups!). I will test tomorrow.
If I remember, I noticed that CustomPart could have several xml contents of the samedi "namespece". That means Refresh doesn’t semestre to erase the last loaded one.
The rest of the program is to check if exceldna and all files exist and unload /reload CustomPart.

I let you know.
Have à good night.

[govert]

You can have the IntelliSense information in any of three places:

• In a sheet called _IntelliSense_
• In a loose file called <MyBook>.IntelliSense.xml
• In a CustomXMLPart in the book (it uses the first CustomXMLPart with the IntelliSense namespace).

For your case, it seems simpler to ship the book with the loose xml language-specific xml files, then copy the right one to the expected <MyBook>.IntelliSense.xml name, then call Refresh.
This way you don't have to fiddle with the CustomXMLPart or read the file.

I think the code you use to read the file (which is from an Excel-DNA sample) is not compatible with UTF-8 contents.
I suggested a better approach in your other discussion here: https://groups.google.com/g/exceldna/c/fBG-kPsn5Y0
But you don't need that if you just use the files (by copying / renaming the right one) directly.

[AL7Seven]

Thanks.
Î’ll do all the tests you suggest and will tell you what’s goong on with them.