Well, if you read back your post you'll see that it wasn't clear at all, which is why I asked if it works out of the box in

Well, it seems clear enough to me in Re: Using the unicode61 tokenizer in DBD::SQLite where I said you need -DEFINES

When you asked if it works out of the box in Re^4: Using the unicode61 tokenizer in DBD::SQLite, I didn't answer the question at all ( Re^5: Using the unicode61 tokenizer in DBD::SQLite ), I basically said figure it out by reading what I said and trying stuff

but I did answer to walto ( Re^4: Using the unicode61 tokenizer in DBD::SQLite), basically no it doesn't work out of the box because it requires -DEFINES

Both answer also seem clear enough to me, maybe a bit short and non-repetitive ... what can I say I'm not chatty

In reply to Re^9: Using the unicode61 tokenizer in DBD::SQLite by Anonymous Monk
in thread Using the unicode61 tokenizer in DBD::SQLite by elef

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.