<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<style>body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;" bidimailui-charset-is-forced="true"
bidimailui-detected-decoding-type="latin-charset" bgcolor="#ffffff"
text="#000000">
On 23/02/11 19:29, Tomer Cohen wrote:
<blockquote
cite="mid:AANLkTin7T4WFKCUdQtpXr15TD+wzrVB+hWnCo_kSiX=c@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<br>
<div class="gmail_quote">On Wed, Feb 23, 2011 at 17:25, Alon Barzilai
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:alon@skylinesoft.com">alon@skylinesoft.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I
found in forums a way to replace half (or all) OS files and fix the
problem in gmail and some other apps, but this does not fix all the
apps.<br>
</blockquote>
<div> </div>
<div>Someone in these forums is responsible enough to report these
issues to the upstream? <br>
</div>
</div>
</div>
</blockquote>
I'm not sure what you mean by "upstream". Most of the limitations of
the forum solutions stem from the fact that no sources are available
for the phones, so you are, essentially, hacking in BiDi support by
modifying the binaries. Which upstream would you say is responsible, in
such a case?<br>
<br>
Also, bear in mind that while I think a better job can be done, not
everything is fixable when you are doing binary only hacking.<br>
<br>
Shachar<br>
<pre class="moz-signature" cols="72">--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
<a class="moz-txt-link-freetext" href="http://www.lingnu.com">http://www.lingnu.com</a>
</pre>
</body>
</html>