<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>entergio Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>entergio Tracker</description>
    <pubDate>Sat, 18 Nov 2023 03:43:13 GMT</pubDate>
    <dc:date>2023-11-18T03:43:13Z</dc:date>
    <item>
      <title>VixDiskLib_Open : Internationalization (multibyte character)</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/VixDiskLib-Open-Internationalization-multibyte-character/m-p/2928801#M2367</link>
      <description>&lt;P&gt;&lt;BR /&gt;If I try to call&amp;nbsp;VixDiskLib_Open to a disk that has a path with Chinese characters it cannot find the path.&lt;BR /&gt;The VDDK only accepts UTF-8 characters, how do I make it open a path that contains Chinese characters?&lt;/P&gt;&lt;P&gt;On the documentation I read:&lt;/P&gt;&lt;P&gt;"VDDK libraries are not localized, but backup partners can support any locale that uses UTF-8 encoding. Other than Unicode, VDDK does not support multibyte character encodings such as Extended Unix Code (EUC) for Chinese, Japanese, and Korean (ISO- 2022).&lt;/P&gt;&lt;P&gt;The path name to a virtual machine and its VMDK can be expressed with any character set supported by the host file system. As of vSphere 4 and Workstation 7, VMware supports Unicode UTF-8 path names, although for portability to various locales, ASCII-only path names are recommended.&lt;/P&gt;&lt;P&gt;Windows 2000 systems (and later) use UTF-16 for localized path names. For example, in locale FR (Français) the VDDK sample code might mount disk at C: \ Windows \ Temp \ vmware-Système, where è is encoded as UTF-16 so the VixMntapi library cannot recognize it. In this case, a workaround is to set the tmpDirectory configuration key with an ASCII-only path before program start-up; see Initialize the Library.&lt;/P&gt;&lt;P&gt;For programs opening arbitrary path names, Unicode offers a GNU library with C functions iconv_open () to initialize codeset conversion, and iconv () to convert UTF-8 to UTF-16, or UTF-16 to UTF-8. "&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So the only solution is to make my customers change their virtual machine paths ?&lt;BR /&gt;iconv cannot convert EUC to UTF8!&lt;BR /&gt;In another post i read that:&lt;BR /&gt;&lt;BR /&gt;"Internationalization support is planned for a future release of VDDK." (&lt;A href="https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/call-VixDiskLib-Open-to-open-multi-byte-characters-file-name/m-p/669565" target="_blank" rel="noopener"&gt;05-19-2008&lt;/A&gt;&amp;nbsp;)&lt;/P&gt;&lt;P&gt;but it's been years.&lt;/P&gt;&lt;P&gt;Is there a workaround?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 09:13:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/VixDiskLib-Open-Internationalization-multibyte-character/m-p/2928801#M2367</guid>
      <dc:creator>entergio</dc:creator>
      <dc:date>2022-09-14T09:13:28Z</dc:date>
    </item>
  </channel>
</rss>

