<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Font feature descriptions for "Linux Biolinum G" et al. can't be localized" href="https://bugs.documentfoundation.org/show_bug.cgi?id=136634#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Font feature descriptions for "Linux Biolinum G" et al. can't be localized" href="https://bugs.documentfoundation.org/show_bug.cgi?id=136634">bug 136634</a> from <a class="email" href="mailto:mihhkel@gmail.com" title="Mihkel Tõnnov <mihhkel@gmail.com>"> Mihkel Tõnnov</a> <pre>Wasn't aware that this is caused by those being Graphite fonts - thanks. I don't think string manipulation on LibO side would be a good approach to this, because that kind of "software smarts" sooner or later break something for one language or another :) E.g. some languages utilize different punctuation / spacing around punctuation, or differ in capital vs. small first letter, or demand a specific case form or suchlike. So if it's deemed unreasonable to enable translation of these exact strings for all the bundled (!) fonts on LibO side, then we the translators would have to try and get the translations into the fonts themselves. (I would prefer the 1st option, though.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>