<div dir="ltr"><div class="gmail_quote">On Wed, Jun 22, 2011 at 2:30 PM, Caolán McNamara <span dir="ltr"><<a href="mailto:caolanm@redhat.com">caolanm@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On Wed, 2011-06-22 at 13:34 +0300, Lior Kaplan wrote:<br> > Hi,<br> ><br> > A year ago when the Hebrew support was taken by the community (was<br> > done by a commercial company before), I've mapped all the Hebrew<br> > related and RTL related bugs in OO.org.<br> ><br> > I was wondering how do we ( = LibO) handle the <a href="http://oo.org" target="_blank">oo.org</a> bugs reported<br> > before the code split. Should I double check them in LibO and open<br> > them in our own bug tracking system?<br> <br> </div>Its always possible to completely flood a bug-tracking system with a<br> gadzillion various problems. Personally I'd prefer either finding ways<br> to fix them yourself :-), or just log the top x most annoying ones where<br> x is a small number ~= 5 if that's not possible.<br> <font color="#888888"><br></font></blockquote><div>I'm not a programmer... so I can't do the fixes myself, but I try to give detailed bug reports, hints to where the problem might be and help with QA of the solutions. <br> <br>I'll try to select the top few so you guys could see what is doable.<br><br>Thanks.<br><br>Kaplan<br></div></div><br></div>