<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On 06/08/2012 12:24 AM, Joel Madero wrote:
    <blockquote
cite="mid:CAPcxoX63pwq6Yc_NAwO6q_9pXyqOdiWnLE3CZ-fxKiicpm+s2Q@mail.gmail.com"
      type="cite">
      <div>Thanks for pointing that out, correction:<br>
      </div>
      <div><br>
      </div>
      <div><a moz-do-not-send="true"
          href="https://bugs.freedesktop.org/show_bug.cgi?id=43192">https://bugs.freedesktop.org/show_bug.cgi?id=43192</a></div>
      <br>
      <div class="gmail_quote">
        On Thu, Jun 7, 2012 at 10:20 PM, Daniel Bankston <span
          dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:daniel.dev.libreoffice@gmail.com"
            target="_blank">daniel.dev.libreoffice@gmail.com</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div class="HOEnZb">
            <div class="h5">On 06/07/2012 10:58 PM, Joel Madero wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                Hi All,<br>
                Before I push this (which I will do tomorrow). I want to
                get preference opinions if possible. Here is the bug
                report:<br>
                <br>
                <a moz-do-not-send="true"
                  href="https://bugs.freedesktop.org/show_bug.cgi?id=43518"
                  target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=43518</a><br>
                <br>
                I tend to agree with the complaint (although it's
                incredibly minor). Technically "between" should not
                include the minimum and maximum numbers put in. Since
                they are (and I think that this is preferred) the text
                should be changed. I opted for "valid range" and
                "invalid range". There are other options including:<br>
                <br>
                between (inclusive) &amp; not between (inclusive) or
                simply include range &amp; exclude range<br>
                <br>
                This is really minor but I'm trying to knock off some of
                these little bugs that just take a small amount of time
                to fix. If you're opposed to any change in language
                &amp;/or prefer different wording please respond,
                otherwise I'm pushing my updates as soon as possible.<br>
                <br>
                Lastly, on a technical note. What's the easiest way for
                me to replace all occurrence of a variable with another
                name. In order to be consistent I'll have to update the
                variable name along with the actual text name.<br>
                <br>
                Thanks all,<br>
                Joel<br>
                <br>
              </blockquote>
              <br>
            </div>
          </div>
          Hi, Joel,<br>
          <br>
          Maybe I misunderstand, but I think you accidentally linked the
          wrong bug report.<br>
          <br>
          <br>
          Respectfully,<br>
          Daniel Bankston<br>
        </blockquote>
      </div>
      <br>
    </blockquote>
    Hi, Joel, <br>
    <br>
    Ironically, I have been working today on ODS's import of Data
    Validity in the feature/gsoc-calc-perf branch which will eventually
    be merged to master.&nbsp; If you are only changing the UI, I don't think
    there will be any conflicts, but can you please show us your patch
    before you push?&nbsp; I haven't committed my own changes to my feature
    branch yet, but I will soon.<br>
    <br>
    <br>
    Respectfully,<br>
    Daniel Bankston<br>
  </body>
</html>