LotusScript to C API Programming Guide

rtLib Domino Rich Text Management template
Home
Show details for ContentContent
Purchase
Ready-to-use samples
Show details for Online resourcesOnline resources
Forum
Links
Happy readers

Anonymous

login


 

Hosted by Prominic.NET, Inc.
Main topic: Using the DXL exporter APIs from LotusScript

Using the DXL exporter APIs from LotusScript (by Normunds Kalnberzins, 01/30/2006 12:24:58 AM)

Kenneth, it looks like despite of these problems you've managed a nice article for "The View". Full of DXL handling code... congratulations.

For me DXL handling is still a grayish zone, because people always complain about the fidelity of round-trips, so it's always something to be tested before implemented. It looks like the development team is still in process of improving it.

I just tested your assertions in ND7 and for me it gives utf-8 -- both from the menu in Designer and from LS. I must admit I do not have an idea how to manipulate the charsets.

And single/double quotes cannot have anything with charset. Besides in my tests I got attribute values in single quotes in both cases and in case any of them are used inside an attribute value they get escaped.

As for 3. I think specifying charset when opening the file serves to interpret the file content. It will not change the value of the tag in any case, nor the "real" encoding.

Could they have improved DXL handling in ND7? I do not remember having your problems in my earlier work with DXL, but then again I did not try much round-tripping of Notes design -- I have practically used it early Notes 6 for design analyses (sort of a homemade Teamstudio analyser). I did have some problems -- and long time ago I complained and got this answer in notes.net:

http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/2be1ce3dcda9bdfd85256c9200750a81?OpenDocument

Dick also talks about utf-16 and utf-8, so your's could be part of the same problem, except the post is from 2002, so they should clearly have had some time for fixing things in the meantime.

About API -- it seems it provides way of setting an export charset, but I've never tried anything with DXL from C API. In any case upgrade to ND7 seems to fix your problems; it's probably simpler than call the APIs - especially as design handling is not an end user application; there cannot be a case of 10000 users who all are still on Notes 6.0.x and who needs to use these cool DXL things, so that it could justify playing around with C API as a workaround...

Good luck, Normunds