<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:eyalroz@technion.ac.il" title="Eyal Rozenberg <eyalroz@technion.ac.il>"> <span class="fn">Eyal Rozenberg</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Difficult to set/override footnote separator line direction"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=133820">bug 133820</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Component</td>
<td>Documentation
</td>
<td>Writer
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Difficult to set/override footnote separator line direction"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=133820#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Difficult to set/override footnote separator line direction"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=133820">bug 133820</a>
from <span class="vcard"><a class="email" href="mailto:eyalroz@technion.ac.il" title="Eyal Rozenberg <eyalroz@technion.ac.il>"> <span class="fn">Eyal Rozenberg</span></a>
</span></b>
<pre>1. No, I'm sorry, this is not a documentation bug. That should be opened
separately. This bug is about the UI itself.
2. We are again in the situation where it is agreed there's a problem with the
UI, but no solution is offered. Better documentation doesn't count as a
solution to UI issues - IMO.
3. A decision that the current UI is sufficient should be discussed and decided
together with the RTL QA group, not merely on your own.
4. I don't understand this sentence?
<span class="quote">> Basically all options are available and after figuring the page style relation it shouldn't be too difficult. </span >
How are they available when you've rejected them? "after figuring out" -
figuring by whom? Also, what is "it" in that sentence?
5.
<span class="quote">> Mixing up the clear separation of page styles with other attributes of the footnotes is not recommended</span >
Well, footnote attributed and page style overlap, semantically; so it's either
a "mixup" or an artificial separation. Also, this principle is invalid: Think
of, say, fonts or font sizes. Nobody has any problem with font controls being
available in lots of places around the UI - complete independently, as part of
the character style, as part of the paragraph style... the font is the font.
Same thing for the footnote separator direction.
Finally, at least some of my suggestions do not involve such mixup:
* Allowing direct access, e.g. with a toolbar button, to the
Page-Footnote-Style settings, as a separate dialog.
* Text, text-link or other mechanism in the Footer tab of the Page Style dialog
directing the user to the Footnote tab.
* Having some appropriate entry in the right-click menu of the separator line.
To be more specific: A menu entry which opens the page style dialog to the
Footnote tab.
I don't know that these are the only possibilities, I'm sure UI wizards can
come up with more ideas.
About the other bugs - will comment there separately.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>