On Wed, Jun 22, 2011 at 2:30 PM, Caolán McNamara <caolanm@redhat.com> wrote:
On Wed, 2011-06-22 at 13:34 +0300, Lior Kaplan wrote:
Hi,
A year ago when the Hebrew support was taken by the community (was
done by a commercial company before), I've mapped all the Hebrew
related and RTL related bugs in OO.org.
I was wondering how do we ( = LibO) handle the oo.org bugs reported
before the code split. Should I double check them in LibO and open
them in our own bug tracking system?
Its always possible to completely flood a bug-tracking system with a
gadzillion various problems. Personally I'd prefer either finding ways
to fix them yourself :-), or just log the top x most annoying ones where
x is a small number ~= 5 if that's not possible.
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.
I'll try to select the top few so you guys could see what is doable.
Thanks.
Kaplan
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.