<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:FreeSerif;
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=DE link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-US>Thanks for giving me the background on this, Karl! I appreciate it!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Is Xiphos the only frontend that has been patching Sword for this purpose? Then I suppose all other frontends suffer from this issue, huh?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Thanks for putting in the work to make Sword behave well with non-ascii path names!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Best regards,<br>Tobias<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:karl@kleinpaste.org">Karl Kleinpaste</a><br><b>Sent: </b>Sonntag, 19. Juli 2020 15:23<br><b>To: </b><a href="mailto:sword-devel@crosswire.org">SWORD Developers' Collaboration Forum</a><br><b>Subject: </b>Re: [sword-devel] Win32 FileMgr Subclass</p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 7/18/20 1:53 PM, Tobias Klein wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US>No, I have not tested my code properly with non-ascii characters in paths / file names.</span></p></blockquote><p class=MsoNormal><br><span style='font-family:"FreeSerif",serif'>The original cause for the Xiphos patch to Sword was because, 11 years ago when we introduced the Win32 port, as GnomeSword was renamed Xiphos, one of our first new Windows users was a fellow in Spain who wanted to review it. His name was Reuvén, and that was his login name on his Windows machine.</span> So of course the path C:\Users\Reuvén was involved, and that 'é' is what killed us.<br><br>What dies here is Sword itself. Xiphos was fine, being already based on glib, but Sword's collapse came as soon as Xiphos made its first filesystem call. The patch glib-ifies Sword, where glib works rather hard at hiding the UTF16 boundary from the application.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>