<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Windows filenames should be in UTF-8 encoding"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103536#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Windows filenames should be in UTF-8 encoding"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103536">bug 103536</a>
from <span class="vcard"><a class="email" href="mailto:ajohnson@redneon.com" title="Adrian Johnson <ajohnson@redneon.com>"> <span class="fn">Adrian Johnson</span></a>
</span></b>
<pre>(In reply to Bill Spitzak from <a href="show_bug.cgi?id=103536#c10">comment #10</a>)
<span class="quote">> I personally am not thrilled that the function has two different methods of
> returning errors. I would instead just return null if the utf8->utf16
> conversion fails and force errno to whatever it gets if you send invalid
> utf16 as a filename to Windows. Then it is easier to drop-in replacement of
> fopen.</span >
It is an internal function. All internal functions that can generate a cairo
status return the status number so that it will be propagated through to the
cairo object that provides a get status.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>