LAPI AND UNICODE

Sandra_Lindquist

I need to do a project that is going to be both english and Japaneese... Im stating with the English version of the API and it does not look unicode compliant at all...(C++) Does anyone have any experience with using the LAPI with a unicode environment? Is the .NET verion of the API unicode complaint? Should I make my component in .NET managed code? OR should I just bite the bullet and use the japaneese version of the API...

Marcia_Gillespie-Norder_(tokeleadmin_-_(deleted))

Hi Peter,I am having these same issues. We have a UTF-8 Livelink configuration. So, we can possibly have content in many languages. Using LAPI, I can get to a folder and list its contents when the folders all have English names. But other folders with names in other languages just come up as garbage.I have tried this with VB using LAPI, Formark's LLCOM2 and now Java LAPI. I want to stick with Java because that is more our future direction.It is my understanding that this SHOULD work. I have tried doing setEncoding in my code and that does not seem to help.If you get this working before I do, can you please forward me the solution or post it here?We have had this discussion already on the multilingual discussion. I have spent so much of my not so spare time trying to make this work:https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=3087584&objAction=view&show=0We also have a separate instance that is Japanese and English. So, they would also benefit from this solution.Thanks,Kevin HutsonTokyo Electron Americakhutson@aus.telusa.com