<div dir="ltr"><font size="4"></font>On 31 March <a href="tel:2012" value="+9722012" target="_blank">2012</a> 09:24, Rainer Bielefeld <span dir="ltr"><<a href="mailto:LibreOffice@bielefeldundbuss.de" target="_blank">LibreOffice@bielefeldundbuss.de</a>></span> wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Shahar Or schrieb:<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It would be beneficial to us, who report and follow RTL bugs, like the<br>
Ubuntu RTL team[1] to have an easy tracking of RTL bugs in<br>
LibreOffice.<br>
</blockquote>
<br></div>
Hi,<br>
<br>
Thank you for your help to improve LibreOffice.<br></blockquote><div><br>My pleasure :)<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Currently we use a pseudo-keyword "RTL" in the Summary line as you see here [1].<br>
The Bug Report Assistant [2] and the Components description page [3] allow/recommend use for Components Database, Documentation, Drawing, Linguistic component, Presentation, Spreadsheet, UI, Writer. Of course it is possible to add that string manually if it's required, and I cann add the Sub Component to other Components if that would be useful.<br>
<br>
A statistic chart how it has been used in the past you find here [4]<br>
<br>
I would prefer to keep proceeding for LibO FDO Bugzilla as it is, because here users and developers are used to proceed this way.<br>
<br>
Of course it would be possible to add a key word, but that should be discussed with Lior Kaplan <<a href="mailto:lior@gmail.com" target="_blank">lior@gmail.com</a>> [5] and others active in this area.<br>
<br>
Please also mention discussion on this mailing list [6] concerning a "Most Annoying RTL Bugs" [7].<br>
<br>
I hope this information is useful for you<br>
<br>
Best regards<br>
<br>
Rainer Bielefeld<br>
<br>
<br>
Hyperlinks<br>
[1] <<a href="https://bugs.freedesktop.org/show_bug.cgi?id=36707" target="_blank">https://bugs.freedesktop.org/<u></u>show_bug.cgi?id=36707</a>><br>
[2] <<a href="http://www.libreoffice.org/get-help/bug/" target="_blank">http://www.libreoffice.org/<u></u>get-help/bug/</a>><br>
[3] <<a href="https://wiki.documentfoundation.org/BugReport_Details" target="_blank">https://wiki.<u></u>documentfoundation.org/<u></u>BugReport_Details</a>><br>
[4] <<a href="https://bugs.freedesktop.org/report.cgi?y_axis_field=op_sys&cumulate=1&z_axis_field=&format=bar&x_axis_field=component&x_labels_vertical=1&query_format=report-graph&short_desc_type=allwordssubstr&short_desc=RTL&product=LibreOffice&action=wrap" target="_blank">https://bugs.freedesktop.org/<u></u>report.cgi?y_axis_field=op_<u></u>sys&cumulate=1&z_axis_field=&<u></u>format=bar&x_axis_field=<u></u>component&x_labels_vertical=1&<u></u>query_format=report-graph&<u></u>short_desc_type=<u></u>allwordssubstr&short_desc=RTL&<u></u>product=LibreOffice&action=<u></u>wrap</a>><br>
[5] <<a href="http://liorkaplan.wordpress.com/2012/01/24/rtl-status-for-libre-office-3-5-0/" target="_blank">http://liorkaplan.wordpress.<u></u>com/2012/01/24/rtl-status-for-<u></u>libre-office-3-5-0/</a>><br>
[6] <<a href="http://lists.freedesktop.org/archives/libreoffice-qa/2011-December/000677.html" target="_blank">http://lists.freedesktop.org/<u></u>archives/libreoffice-qa/2011-<u></u>December/000677.html</a>><br>
[7] <<a href="https://bugs.freedesktop.org/show_bug.cgi?id=43808" target="_blank">https://bugs.freedesktop.org/<u></u>show_bug.cgi?id=43808</a>><br>
</blockquote></div><br>This is too much information :) I would prefer a simple instruction on how to:<br><br>1. Have a URL to a list of all RTL bugs. Not just the most annoying ones.<br>2. Be able to mark or "tag" or "keyword" all RTL bugs as such.<br>
3. Have a formal and documented instruction on that so that bug reporters / handlers would "tag" those bugs.<br><br>A keyword seems the most natural way to me. Please see KDE[1] as well.<br><br>I apologize. I do not understand what you suggest about adding a sub component and if I do understand than that would be a bit confusing/overkill.<br>
<br>Why would you use pseudo keywords and not actual keywords? Too many keywords, you have?<br><br>Lior, can you chime in, please?<br><br> 1. <a href="https://bugs.kde.org/buglist.cgi?keywords=rtl" target="_blank">https://bugs.kde.org/buglist.cgi?keywords=rtl</a><br>
</div>