LAPI UTF-8 Support from the VB6 Application

David_Zhu

We are modifying an VB6 application to support UTF-8. Here is the configuration:Livelink 9.7 UTF-8 VB6 Application using LAPI SDK 9.5.0.1The LAPI document indicates that the LL_SetCodePage() should be called to set up the codepage. I added the following call to the VB6 application: lError = LL_SetCodePage(lSession, LL_TRUE, LL_TRUE, 65001)Here are my questions:1. By debugging the VB6 app, the return value of LL_SetCodePage() is zero. However, it apepars that the call doesn't make much difference since without calling it after allocating the session, I'm still able to retrieve the UTF-8 chracters from the Livelink 9.7 UTF-8 server such as the document/folder names in UTF-8. Is this being taken care of by Livelink 9.7 UTF-8? 2. I'm calling LL_ValueGetString() to retrieve some values for the folder names or document names in Livelink that can be in UTF-8 (Japanese or Chinese). Here is the call: lError = LL_ValueGetString(lValueObject, strBuf, Len(strBuf), lBufSize)The returned string appears to be in UTF-8. For example, one Chinese chracter will take 3 bytes. However, if they are in Japanese or Chinese, I had to do a conversion myself inside the VB6 application from the UTF-8 so they can be displayed properly. Does LAPI SDK take care of this conversion? Since it appears that the LL_SetCodePage() call doesn't work for me well, could the call to LL_SetCodePage() be the reason? 3. Will LAPI SDK 9.5.0.1 work with Livelink 9.7 UTF-8 or we will need to use LAPI SD K9.7? Basically we are modifying the VB6 application so it can retrieve the UTF-8 chracters (They can be in Japanese or Chinese) from Livelink 9.7 UTF-8 and display them properly, and upload the metadata that can be in Japanese or Chinese (UTF-8) into Livelink 9.7 UTF-8. I really apprecaite any information you can share on this UTF-8 support. Thanks in advance,David

eLink User

Message from Carsten Kulms via eLinkI think the observed behaviour has to be regared as a bug.Please contact OT customer support for confirmation that your problemhas the same cause as the already filed issue "LPO-150". Sorry for the bad news and the inconvenience.