W dniu 2014-04-05 12:04, Marcin Miłkowski pisze:
> W dniu 2014-04-04 19:43, Daniel Naber pisze:
>> On 2014-04-04 10:32, Marcin Miłkowski wrote:
>>
>>> Another one: adding a second example (under Chrome) creates incorrect
>>> XML:
>> Can you specify the exact workflow that leads to this? I couldn't
>> reproduce so far.
> I don't remember it anymore :(
>
> I'll see if it happens again.
OK, it happened again:
<!-- Polish rule, 2014-04-05 -->
<rule id="ID" name="">
<pattern>
<token regexp='yes'>.*\p{Ll}+ie</token>
<token regexp='yes' spacebefore='no'>['`’]</token>
<token regexp='yes'>e?(?:go|mu|m)</token>
</pattern>
<message>Ten wyraz odmienia się prawdopodobnie tak: <suggestion><match
no="1"/><match no="3" regexp_match=".*(go|mu|m)"
regexp_replace="$1"/></suggestion>.</message>
<url>http://so.pwn.pl/lista.php?co=Chaplin</url>
<short>Błąd ortograficzny</short>
<example type='incorrect'>Zaprośmy <marker>Charlie'go</marker>. Zaprośmy
Charlie'ego.</example>
<example type='correct'>Zaprośmy Charliego.</example>
<example type='incorrect'>Zaprośmy Charlie'ego.</example>
</rule>
What I did was to edit manually two examples, change the rule, and then
add another example, change the rule, and it was there. I'm sure I only
changed the suggestions (match parameters to be exact).
Regards,
Marcin
------------------------------------------------------------------------------
_______________________________________________
Languagetool-devel mailing list
Languagetool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/languagetool-devel
