Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Thanks for the links. Especially coy. delightful.

I agree completely with your quixotic implication: my efforts in this direction so far have proceeded on two fronts: recursive sentence-building routines based on Chomskyan deep structure rules, all of which have failed terribly, and really simple special case routines like the one above, which makes a perfectly readable sentence in a very dull way.

My background is philosophy of language rather than straight linguistics, but i've got enough of a grasp to see the scale of the problem. I don't think it's completely hopeless, as long as it's properly constrained. The content-management systems that i'm trying to make more articulate are a good place to start: they have a very limited world, their utterances fall into a few well-defined categories, they're almost always declarative, and the goal is transparency, not lyricism.

to start with, i'd like to identify a small set of phrases that people use all the time. that's why i used the results example above, which everyone must need at some point. Other examples might include pagination links, error messages and confirmation questions, but i'm hoping people will make suggestions. Then i'd like to implement that limited set in as general a way as possible, and take it from there.

So it's a fairly limited ambition, really. The fact that i'm using it as a spur both to learn OOP properly and finally read the algorithm book should give you some idea of how long it's likely to take :(

updated: silly typo

In reply to Re: Re: natural language sentence construction by thpfft
in thread natural language sentence construction by thpfft

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others lurking in the Monastery: (5)
    As of 2018-06-22 21:32 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (124 votes). Check out past polls.