<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#c25">Comment # 25</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:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to itt788 from <a href="show_bug.cgi?id=128316#c24">comment #24</a>) > (In reply to Mike Kaganski from <a href="show_bug.cgi?id=128316#c23">comment #23</a>) > > (In reply to itt788 from <a href="show_bug.cgi?id=128316#c22">comment #22</a>) > > > Auto-capitalisation must be removed from the code making the date > > > field. Spell checker with its grammar and language options should take care > > > of capitalisation for the whole document on the basis of user settings. > > > > This has no sense. Fields value is not subject to grammar checker (and must > > not be.) > > I hope having not been misunderstood. > > In my previous comment i meant that in whatever language capitalisation is a > matter of grammar. Thus the date field should never force either > capitalisation or non-capitalisation unless the user wishes so, in which > case he must turn on spell-checker with grammar option. Here it the thing I objected to. The phrase "the date field should never force either capitalisation or non-capitalisation unless the user wishes so, in which case he must turn on spell-checker with grammar option" implies that the spell-checker would somehow suggest and/or change capitalization of the date field text. But *that* will not happen, because field data is not spell-checked in any way. 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. 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).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>