<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#c27">Comment # 27</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#c26">comment #26</a>) > (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. Absolutely not. You miss the point entirely. Field is, by its nature, not a random text. Its text is *meant* to be *generated by program* following the field's rules from some data (e.g., a number representing a date). There's no concept of "field data modified by user". Hence there's no "field text + spell check edits". This is *how it should be*: any changes of the field content may only be applied by modifying the field properties, not editing text from outside. Which means that field properties must provide user a means to define wanted capitalization, not some "spell check" or any outside tool.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>