<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FIELDS: Allow date field with lower case letters" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128316#c26">Comment # 26</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FIELDS: Allow date field with lower case letters" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128316">bug 128316</a> from <a class="email" href="mailto:itt788@yandex.com" title="itt788@yandex.com">itt788@yandex.com</a> <pre>(In reply to Mike Kaganski from <a href="show_bug.cgi?id=128316#c25">comment #25</a>) [ ... ] >From spell checked point of view, a field is some > kind of external object, like image. Its content is not something that user > types freely, and is calculated automatically from some source data. Thus an > expectation that spell checker would do something instead of the field > itself is wrong. you're pointing a purely technical point, and this is not how it should be. In French for example, day and month names follow the same rule as common names, i.e. capitalisation is only done if they occur as first word in a sentence. So if autocapitalisation were user settable for date fields and ON, then capitalisation will happen even in the middle of a sentence if that's where the date field is. That forces users to check manually each date entry in their document. For a text processor that claims to check grammar, that should be called a bug. [ ... ] > Thus some method of capitalization *must* be embedded into > the field, or else user will have no way to control that (just the same way > as it it now, only the opposite direction: when one wants capitalization, > that would be impossible). There seems to be such a long way to go. LO is a fork from a project that was first released in 1985!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>