ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Find too long sentences
Date: Fri, 15 Feb 2013 13:54:32 +0100	[thread overview]
Message-ID: <20130215125432.GA29053@phlegethon.router_intern> (raw)
In-Reply-To: <511E2C53.6030309@mmnetz.de>


[-- Attachment #1.1: Type: text/plain, Size: 1631 bytes --]

···<date: 2013-02-15, Friday>···<from: "H. Özoguz">···

> Good Friday there,
> 
> working on a book with many too long sentences, I got the following
> idea/question:
> Is it possible to recognize the length of a sentence, and to let
> context show in the pdf, if there is a too long sentence.

Places to start:
  http://en.wikipedia.org/wiki/Sentence_breaking
  http://en.wikipedia.org/wiki/Natural_language_processing#Major_tasks_in_NLP

Good luck :P
Philipp



> 
> For example I am thinking of an command like
> \version[longsentence,15]
> 
> which sets an symbol like "*" in the margin, if a sentence has more
> than 15 words.
> 
> First, correct sentence-regonition could be a task: It is not enough
> to count the words between two dots, because of abbreviations. But
> there is probably a known algorithm for handling those problems. I
> think a feature like this could be interesting for context (and for
> my work :D)
> 
> Thanks for you comments
> Huseyin
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2013-02-15 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 12:38 "H. Özoguz"
2013-02-15 12:52 ` Marco Patzer
2013-02-15 12:54 ` Philipp Gesang [this message]
     [not found] <mailman.815.1360932936.2489.ntg-context@ntg.nl>
2013-02-15 14:11 ` "H. Özoguz"
2013-02-15 14:52   ` Marco Patzer
2013-02-15 16:16     ` Marco Patzer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130215125432.GA29053@phlegethon.router_intern \
    --to=philipp.gesang@alumni.uni-heidelberg.de \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).