kicad-developers team mailing list archive

[Manveru <manveru@...>]

--000325557a76f573a1047b5fcb9c Content-Type: text/plain; charset=UTF-8

2009/12/22 Lorenzo <lomarcan@...>

> [...]
>
> This is only speculation and it needs testing but I suspect that kicad
> files using extended characters (codepoints > 127) today ARE NOT portable
> between unix and windows.
> [...]
>

LyX (using Qt and UTF-8 for file encoding do not have problems with
portability between Unix and Windows, as far as I know Python interpreters,
too). So in case where wx methodology is used to handle all file operations
all files should be portable.

-- 
Manveru
jabber: manveru@...
gg: 1624001
http://www.manveru.pl
 --000325557a76f573a1047b5fcb9c Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2009/12/22 Lorenzo <span dir=3D"ltr">&lt=
;<a href=3D"mailto:lomarcan@...";>lomarcan@...</a>&gt;</span><br><bloc=
kquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, =
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">













<div style=3D"background-color: rgb(255, 255, 255);"><span> [...]</span><br=
><div><div><div>
<br>
This is only speculation and it needs testing but I suspect that kicad file=
s using extended characters (codepoints &gt; 127) today ARE NOT portable be=
tween unix and windows.<br>[...]</div></div></div></div></blockquote><div>
<br>LyX (using Qt and UTF-8 for file encoding do not have problems with por=
tability between Unix and Windows, as far as I know Python interpreters, to=
o). So in case where wx methodology is used to handle all file operations a=
ll files should be portable. <br>
</div></div><br>-- <br>Manveru<br>jabber: <a href=3D"mailto:manveru@manveru=
.pl">manveru@...</a><br> =C2=A0 =C2=A0 gg: 1624001<br> =C2=A0 <a hre=
f=3D"http://www.manveru.pl";>http://www.manveru.pl</a><br>
 --000325557a76f573a1047b5fcb9c--