<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - language-agnostic styles"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=127115#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - language-agnostic styles"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=127115">bug 127115</a>
from <span class="vcard"><a class="email" href="mailto:lvm@royal.net" title="lvm@royal.net">lvm@royal.net</a>
</span></b>
<pre>I kept on thinking about this issue and while I don't really care how it is
done as long as it gets done, it is in fact an indication of a fundamental
design flaw. Document can be split into two domains: content and presentation.
Style - fonts, colours, spacing etс - belongs to the presentation domain, text
- to the content. Text is always written in specific language, applying German
language to text written in French is meaningless as it won't translate it into
German - not yet anyway; language is an invariable attribute of text and
belongs to the content domain which means that linking language with fonts and
styles is incorrect, and the proper way of resolving this issue requires
complete separation of language from the presentation domain. Language should
be assigned to text not as one of the attributes of the font and shouldn't be
linked to styles in any way, but should be a completely independent text
attribute (which to some extent is already done via Tools-Language menu, but
unless you pick a language from a 3-item frequently used list you still end up
in the same font selection dialogue). Incidentally, ODF standard is similarly
flawed: fo:language is the attribute of style:text-properties.</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>