<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Ruby formatting should be configurable using paragraph styles"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=109030">109030</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Ruby formatting should be configurable using paragraph styles
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>5.3.3.2 release
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Writer
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>khanson679@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>Description:
Currently the position and alignment of ruby text must be set manually upon
every application. Likewise for changes to existing ruby text.
It should be possible to set these properties in the paragraph style, modified
from those values using the Asian Phonetic Guide dialog, and reset to style
defaults as with other text formatting properties.
This appears to be supported in the ODF 1.2 spec under section 17.10
<style:ruby-properties>.
Related: <a class="bz_bug_link
bz_status_NEW "
title="NEW - Default behaviour of Asian Phonetic Guide window"
href="show_bug.cgi?id=104503">bug 104503</a>. Adding this feature will provide a workaround, or perhaps
an altogether better solution to the problem in this bug.
Steps to Reproduce:
n/a
Actual Results:
n/a
Expected Results:
n/a
Reproducible: Always
User Profile Reset:
Additional Info:
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101
Firefox/54.0</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>