<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 2014-08-26 12:16, Pieren wrote :<br>
    </div>
    <blockquote
cite="mid:CAPT3zJpYsuoMReFZySQWAApB-JOzVJSqBoek=ShY+h=du_zRnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Mon, Aug 25, 2014 at 8:36 PM,
            André Pirard <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:A.Pirard.Papou@gmail.com" target="_blank">A.Pirard.Papou@gmail.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">Yes, this sentence
                is misunderstood, and by many repliers apparently.<br>
                It means that once Mapnik uses a (defined) rendering you
                cannot change it (RENDER is ignored).<br>
                The main idea behind RENDER is not coloring objects, and
                I agree it shouldn't, but showing them.<br>
                And the renderer can do that with any single color they
                like.<span class="HOEnZb"><font color="#888888"><br>
                    <table>
                      <tbody>
                        <tr>
                          <td><br>
                          </td>
                        </tr>
                      </tbody>
                    </table>
                  </font></span></div>
            </blockquote>
            <div><br>
            </div>
            <div>Basically, all renderers already decide what they print
              or not. </div>
          </div>
        </div>
      </div>
    </blockquote>
    If that's "already decided" rendering, I hope that those suggesting
    opening a ticket are not jokers ! ;-)<br>
    <blockquote
cite="mid:CAPT3zJpYsuoMReFZySQWAApB-JOzVJSqBoek=ShY+h=du_zRnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>Adding a flag saying "hey don't forget my feature" will
              not change this principle. </div>
          </div>
        </div>
      </div>
    </blockquote>
    Unless the renderers consider that they can't cope with every map
    feature, esp. with a specific rendering, that a plain surface and a
    name is sufficient and if the mappers are wise enough to follow
    guidelines without abusing.<br>
    Mapping a recreation site with only one of the three attractions
    they have and two big holes is the particular OSM meaning of the
    word attraction.<br>
    <blockquote
cite="mid:CAPT3zJpYsuoMReFZySQWAApB-JOzVJSqBoek=ShY+h=du_zRnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>Also with your tag, the same feature may or may not be
              displayed on the map, depending if you added your RENDER
              tag or not.</div>
          </div>
        </div>
      </div>
    </blockquote>
    If that's a problem, it has already been said that the simple
    solution is defining a rendering.<br>
    <blockquote
cite="mid:CAPT3zJpYsuoMReFZySQWAApB-JOzVJSqBoek=ShY+h=du_zRnA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>Your proposal have no chance to be adopted for these
              reasons.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    Not a single suggestion either.  Happy tagging for the renderer,
    everybody.<br>
    <br>
    <table>
      <tbody>
        <tr>
          <td>André.</td>
        </tr>
      </tbody>
    </table>
    <br>
    <br>
  </body>
</html>