<HTML><FONT FACE=arial,helvetica><FONT SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">In a message dated 9/15/2002 4:56:03 AM Eastern Daylight Time, sanke@hrz.uni-kassel.de writes:<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">I cannot see why you should not try to remove the problem of<BR>
cross-platform transfer of un-American characters inside custom<BR>
properties (and its names) - however unimportant that may be for the<BR>
majority of Metacard users - and thus improve the transferability between<BR>
different platforms, which is one of the outstanding features of<BR>
Metacard.</BLOCKQUOTE><BR>
<BR>
The fix for custom property *names* seems reasonable and helpful, but as others have mentioned, messing with the contents of the custom properties would be unacceptable. We can't have MetaCard altering our binary data behind our back! If you want to store textual data and have its content converted, you should really use fields. OR... use MetaCard's built-in functions: macToISO() and ISOToMac().<BR>
<BR>
HTH,<BR>
Brian</FONT></HTML>