Revision: 6958
http://languagetool.svn.sourceforge.net/languagetool/?rev=6958&view=rev
Author: dnaber
Date: 2012-05-17 13:14:20 +0000 (Thu, 17 May 2012)
Log Message:
-----------
document new new "<marker>" element that replaces mark_from/mark_to
Modified Paths:
--------------
trunk/website/www/development/index.php
Modified: trunk/website/www/development/index.php
===================================================================
--- trunk/website/www/development/index.php 2012-05-17 13:09:01 UTC (rev
6957)
+++ trunk/website/www/development/index.php 2012-05-17 13:14:20 UTC (rev
6958)
@@ -115,7 +115,9 @@
<?php hl('<rule id="BED_ENGLISH" name="Possible typo 'bed/bat(bad)
English/...'">
<pattern mark_from="0" mark_to="-1">
- <token regexp="yes">bed|bat</token>
+ <marker>
+ <token regexp="yes">bed|bat</token>
+ </marker>
<token regexp="yes">English|attitude</token>
</pattern>
<message>Did you mean<suggestion>bad</suggestion>?</message>
@@ -129,12 +131,14 @@
<ul class="largelist">
<li>element <tt>rule</tt>, attribute <tt>id</tt>: An internal
identifier used to address this rule. This must be unique.</li>
<li>element <tt>rule</tt>, attribute <tt>name</tt>: The text displayed
in the configuration.</li>
- <li>element <tt>pattern</tt>, attributes <tt>mark_from</tt> and
<tt>mark_to</tt>: What part of the original
- text should be marked. The default, <tt>mark_from="0"</tt> and
<tt>mark_to="0"</tt>, means to mark
+ <li>element <tt>pattern</tt>, attributes <tt>mark_from</tt> and
<tt>mark_to</tt> (LanguageTool <= 1.7): What part of the original
+ text should be marked as an error. The default,
<tt>mark_from="0"</tt> and <tt>mark_to="0"</tt>, means to mark
the complete matching token. For example, if the pattern
contains three token
elements that match the input text, those three matching words
will be marked in the text.
<tt>mark_to="-1"</tt> in the example above means that the last
token of the match will not
be marked.</li>
+ <li>element <tt>pattern</tt>, sub element <tt>marker</tt> (LanguageTool
>= 1.8): What part of the original
+ text should be marked as an error. If all tokens are part of
the error you can omit this element.</li>
<li>element <tt>token</tt>, attribute <tt>regexp</tt>: interpret the
given token
as a regular expression</li>
<li>element <tt>message</tt>: The text displayed to the user if this
rule matches.
@@ -211,7 +215,7 @@
<p>In XML rules, you can refer to previously matched tokens in the
pattern. For example:</p>
- <?php hl('<pattern mark_from="2">
+ <?php hl('<pattern>
<token regexp="yes" skip="-1">ani|ni|i|lub|albo|czy|oraz<exception
scope="next">,</exception></token>
<token><match no="0"/></token>
</pattern>'); ?>
@@ -247,13 +251,20 @@
<p>For some languages (currently Polish, English, Catalan, Spanish,
Galician, Dutch, Romanian, Slovak and Russian), element <match/> can be
used to
insert an inflected matched token (or another word with a specified
part of speech
tag). For example:</p>
-
- <?php hl('<pattern mark_from="1" mark_to="-1">
+
+ <?php hl('<pattern>
<token regexp="yes">has|have</token>
- <token postag="VBD|VBP|VB" postag_regexp="yes"><exception
postag="VBN|NN:U.*|JJ.*|RB" postag_regexp="yes"/></token>
+ <marker>
+ <token postag="VBD|VBP|VB" postag_regexp="yes">
+ <exception postag="VBN|NN:U.*|JJ.*|RB" postag_regexp="yes"/>
+ </token>
+ </marker>
<token><exception postag="VBG"/></token>
</pattern>
-<message>Possible agreement error -- use past participle here:
<suggestion><match no="2" postag="VBN"/></suggestion>.</message>'); ?>
+<message>
+ Possible agreement error -- use past participle here:
+ <suggestion><match no="2" postag="VBN"/></suggestion>.
+</message>'); ?>
<p>The above rule takes the second verb with a POS tag "VBN", "VBP" or
"VB" and displays its
form with a POS tag "VBN" in the suggestion. You can also specify POS
tags using
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Languagetool-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/languagetool-cvs
