languagetool-devel Mailing List for LanguageTool

Hi,

as discussed, this mailing list is now shutting down. Please use 
http://forum.languagetool.org from now on and use the 'Development' 
category for development-related issues.

Here's a post about how you can use the forum like a mailing list (at 
least for reading): 
http://forum.languagetool.org/t/how-to-use-this-forum-like-a-mailing-list/1067

You're NOT automatically migrated to the forum, so if you don't actively 
follow the forum now, you'll not get any LT emails anymore.

If you post to this list anyway, your message will be stuck in the 
moderation queue forever, so don't.

Regards
  Daniel

On 2016-09-25 12:22, Daniel Naber wrote:

> I
> suggest closing this mailing list and using our web forum instead. This
> should help against fragmentation of discussions.

Thanks for everyone's feedback. As most people agree with the move to 
the forum, I'll close this list soon. That means the list will 
technically still exist, but nothing new can be posted. I'll post a 
description to the forum describing how to 'subscribe' to it, i.e. how 
to use it like a mailing list.

Regards
  Daniel

Hi,

LanguageTool 3.5 has been released and is available at 
https://languagetool.org. Changes include:

* New rules and rule improvements for Catalan, English, Esperanto, 
French, German, Polish, Portuguese, Russian, Spanish, and Ukrainian
* Update of the English (GB) spell dictionary
* Speed-ups for the standalone version when checking long texts
* Bug fixes

A more detailed list of changes is available at 
https://languagetool.org/download/CHANGES.md

Check sums:

f6984ce87fa6564394e232201db7e167066c36371335a4e337d7b28b574917c1  
LanguageTool-3.5.oxt
643029da89041ccfb48772deaf0dd0e16942de2d381c5dc8ae9372f1b043bcab  
LanguageTool-3.5.zip

Regards
  Daniel

On 2016-09-27 21:06, Fernand FERDINANDE wrote:

> Where do I send unknown Dutch words to? (unknown by language tool or
> correct words told by language tool to be mistake)

According to the README, you can send them to info at taaltik.nl

Regards
  Daniel

Where do I send unknown Dutch words to? (unknown by language tool or correct words told by language tool to be mistake)

> Op 26 sep. 2016, om 16:12 heeft Daniel Naber <dan...@la...> het volgende geschreven:
> 
> On 2016-09-26 14:48, Idan Morad wrote:
> 
>> What about the spelling mistakes?
> 
> We don't maintain the spelling dictionary, but you can suggest words at 
> https://github.com/marcoagpinto/aoo-mozilla-en-dict/ (en-GB) and 
> http://wordlist.aspell.net/ (en-..)
> 
> Regards
>  Daniel
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Languagetool-devel mailing list
> Lan...@li...
> https://lists.sourceforge.net/lists/listinfo/languagetool-devel

I also agree with the change regarding moving mailing list to the forum.

Regards,
Sharad

On Sun, Sep 25, 2016 at 8:11 PM, <
lan...@li...> wrote:

> Send Languagetool-devel mailing list submissions to
>         lan...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/languagetool-devel
> or, via email, send a message with subject or body 'help' to
>         lan...@li...
>
> You can reach the person managing the list at
>         lan...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Languagetool-devel digest..."
>
> Today's Topics:
>
>    1. old API shutdown 2016-10-01 (Daniel Naber)
>    2. move mailing list to forum? (Daniel Naber)
>
>
> ---------- Forwarded message ----------
> From: Daniel Naber <dan...@la...>
> To: LanguageTool Developer List <lan...@li...>
> Cc:
> Date: Sat, 24 Sep 2016 22:20:41 +0200
> Subject: old API shutdown 2016-10-01
> Hi,
>
> this is a final warning about our old HTTP/XML API being shut down in 7
> days. It has been replaced with a more coherent JSON-based API, as
> documented at https://languagetool.org/http-api/migration.php
>
> For some time, the old API will then return an artificial "grammar error"
> on the first character of the text that describes that the API has been
> shut down and that points to the URL above.
>
> As the old Firefox add-on "LanguageToolFx" also uses the old API, I have
> set its status to "hidden" on http://addons.mozilla.org. This shouldn't
> be an issue, as the new add-on called simply "LanguageTool" has been
> available for more than three months now.
>
> Regards
>  Daniel
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Daniel Naber <dan...@la...>
> To: LanguageTool Developer List <lan...@li...>
> Cc:
> Date: Sun, 25 Sep 2016 12:22:13 +0200
> Subject: move mailing list to forum?
> Hi,
>
> there's not much traffic here on the list. Some discussions happen on the
> github bug tracker, some happen at http://forum.languagetool.org. I
> suggest closing this mailing list and using our web forum instead. This
> should help against fragmentation of discussions.
>
> You can follow the forum by email or by reading its RSS feed. What you
> cannot do is post to the forum by sending an email, you'll have to visit
> the forum for that. We probably wouldn't migrate to the forum in the sense
> that mailing list subscribers automatically get subscribed to the forum,
> they'd have to sign up at the forum by themselves. We could add a
> "development" category at the forum if needed.
>
> Any thoughts?
>
> Regards
>  Daniel
>
>
>
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> Languagetool-devel mailing list
> Lan...@li...
> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>
>

I felt like mailing list is used more by developers and users writing to
the forum.
I personally prefer mailing list, but I understand if maintaining both is
too much work.

Andriy

2016-09-26 12:14 GMT-04:00 Andre Couture <aco...@as...>:

> I personally like the idea of moving to a forum.
>
> I have register with many forums and most, if not all, of them have option
> to subscribe to threads.
> Doing this allow me to receive notifications when new content is added and
> even some allow to send the content of the changes so I dont need to even
> login to them anymore unless I need or want to “participate”
>
> Andre
>
>
> > On Sep 26, 2016, at 10:52, Silvan Jegen <me...@si...> wrote:
> >
> > On Mon, Sep 26, 2016 at 04:14:49PM +0200, Daniel Naber wrote:
> >> On 2016-09-26 15:49, Dmitri Gabinski wrote:
> >>> I find a mail list a better solution generally: you can archive
> >>> threads/messages that you deem relevant and delete ones that you deem
> >>> irrelevant.
> >>
> >> You can also do that with a forum, as you can get everything you're
> >> interested in via mail too.
> >
> > With a forum you have to log in everytime (provided you are not saving
> > your credentials) and you don't get to use the interface of your choice
> > to write messages. You can even use your tools of choice for search if
> > you have local mail and don't have to hope that the forum search works
> > as it should...
> >
> > For someone like me who is mostly stalking the mailing list, logging in
> > occasionally to reply in a thread should not make much of a difference
> > in practice though.
> >
> >
> > Cheers,
> >
> > Silvan
> >
> > ------------------------------------------------------------
> ------------------
> > _______________________________________________
> > Languagetool-devel mailing list
> > Lan...@li...
> > https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> Languagetool-devel mailing list
> Lan...@li...
> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>

I personally like the idea of moving to a forum.

I have register with many forums and most, if not all, of them have option to subscribe to threads. 
Doing this allow me to receive notifications when new content is added and even some allow to send the content of the changes so I dont need to even login to them anymore unless I need or want to “participate”

Andre


> On Sep 26, 2016, at 10:52, Silvan Jegen <me...@si...> wrote:
> 
> On Mon, Sep 26, 2016 at 04:14:49PM +0200, Daniel Naber wrote:
>> On 2016-09-26 15:49, Dmitri Gabinski wrote:
>>> I find a mail list a better solution generally: you can archive
>>> threads/messages that you deem relevant and delete ones that you deem
>>> irrelevant.
>> 
>> You can also do that with a forum, as you can get everything you're 
>> interested in via mail too.
> 
> With a forum you have to log in everytime (provided you are not saving
> your credentials) and you don't get to use the interface of your choice
> to write messages. You can even use your tools of choice for search if
> you have local mail and don't have to hope that the forum search works
> as it should...
> 
> For someone like me who is mostly stalking the mailing list, logging in
> occasionally to reply in a thread should not make much of a difference
> in practice though.
> 
> 
> Cheers,
> 
> Silvan
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Languagetool-devel mailing list
> Lan...@li...
> https://lists.sourceforge.net/lists/listinfo/languagetool-devel

On Mon, Sep 26, 2016 at 04:14:49PM +0200, Daniel Naber wrote:
> On 2016-09-26 15:49, Dmitri Gabinski wrote:
> > I find a mail list a better solution generally: you can archive
> > threads/messages that you deem relevant and delete ones that you deem
> > irrelevant.
> 
> You can also do that with a forum, as you can get everything you're 
> interested in via mail too.

With a forum you have to log in everytime (provided you are not saving
your credentials) and you don't get to use the interface of your choice
to write messages. You can even use your tools of choice for search if
you have local mail and don't have to hope that the forum search works
as it should...

For someone like me who is mostly stalking the mailing list, logging in
occasionally to reply in a thread should not make much of a difference
in practice though.


Cheers,

Silvan

On 2016-09-26 15:49, Dmitri Gabinski wrote:

> I find a mail list a better solution generally: you can archive
> threads/messages that you deem relevant and delete ones that you deem
> irrelevant.

You can also do that with a forum, as you can get everything you're 
interested in via mail too.

Regards
  Daniel

On 2016-09-26 14:48, Idan Morad wrote:

> What about the spelling mistakes?

We don't maintain the spelling dictionary, but you can suggest words at 
https://github.com/marcoagpinto/aoo-mozilla-en-dict/ (en-GB) and 
http://wordlist.aspell.net/ (en-..)

Regards
  Daniel

I find a mail list a better solution generally: you can archive
threads/messages that you deem relevant and delete ones that you deem
irrelevant. In a forum, you are at admin’s mercy, and virtually in all
forums I know, threads are not deleted even when they are obsolete.
Thus, a forum accumulates tons of information that eventually become
just garbage.

2016-09-25 13:22 GMT+03:00 Daniel Naber <dan...@la...>:
>
> there's not much traffic here on the list.

Really? Then what is _much_ to you? Among the mail lists I am
subscribed to, this list is one of the most active.

Of course, I am not an active participant/contributor and my opinion
can (and, probably, should) be ignored, but, please, if you decide to
shut down this list, don’t do that instantly and leave at least a
month. I have a question about making a rule, which I would like to
post here, but the question evolves as I acquire some more knowledge
digging in this list’s archives, so give me a chance.

Best regards,

Dmitri Gabinski

Hi thanks =)
What about the spelling mistakes?


Best Reagrds,
Idan Morad

On Sun, Sep 25, 2016 at 3:28 PM, Idan Morad <id...@se...> wrote:

> Hi,
>
> My corpus is mostly comprised of articles that comes from Information
> Technology and I'd like to find if the analysts that wrote those articles
> have done grammar mistakes.
> Now I getting a lot of false positive (made mistakes) with the rules
> related to the pronoun "it". such as:
>
>    1. "IT research firm" was failed by IT_VBZ ('it' + non-3rd person verb)
>    2. "high IT spend" was failed by IT_VBZ ('it' + non-3rd person verb)
>    3. "Sold IT end user research" was failed by IT_VBZ ('it' + non-3rd
>    person verb)
>    4. "Gartner's IT advice is used" was failed by ADVICE_ADVISE (advise
>    (verb) instead of advice (noun))
>    5. "reduce IT spend" was failed by IT_VBZ ('it' + non-3rd person verb)
>    6. "IT consulting" was failed by I_MOVING (personal pronoun + gerund)
>    7. "IT's" was failed by IT_IS (its vs. it's)
>
> and so on, because most of my focus in on grammar I really need it not to
> fail. How to solve this problem?
> another problem which is less significant because it is spelling is the
> fact that job titles such as CIO, CTO, CMO is correct spelling but when it
> comes in plurar such as CIOs, CTOs and CMOs it is a spelling mistake.
>
> Best Reagrds,
> Idan Morad
>
>

I agree.
--Jan

Am 26.09.2016 um 11:31 schrieb Mike Unwalla:
> I am in favour of this proposed change.
> 
> Mike
> 

I am in favour of this proposed change.

Mike

-----Original Message-----
From: Daniel Naber [mailto:dan...@la...] 
Sent: 25 September 2016 11:22
To: LanguageTool Developer List
Subject: move mailing list to forum?

Hi,

there's not much traffic here on the list. Some discussions happen on 
the github bug tracker, some happen at http://forum.languagetool.org. I 
suggest closing this mailing list and using our web forum instead. This 
should help against fragmentation of discussions.

<snip>

Any thoughts?

Regards
  Daniel

On 2016-09-25 14:28, Idan Morad wrote:

Hi Idan,

> My corpus is mostly comprised of articles that comes from Information
> Technology and I'd like to find if the analysts that wrote those
> articles have done grammar mistakes.
> Now I getting a lot of false positive (made mistakes) with the rules
> related to the pronoun "it". such as:

LanguageTool's rules are case-insensitive by default, which doesn't work 
too well with "IT". I've made the rules you mentioned more strict so 
they will not match anymore in the future.

Regards
  Daniel

Hi,

My corpus is mostly comprised of articles that comes from Information
Technology and I'd like to find if the analysts that wrote those articles
have done grammar mistakes.
Now I getting a lot of false positive (made mistakes) with the rules
related to the pronoun "it". such as:

   1. "IT research firm" was failed by IT_VBZ ('it' + non-3rd person verb)
   2. "high IT spend" was failed by IT_VBZ ('it' + non-3rd person verb)
   3. "Sold IT end user research" was failed by IT_VBZ ('it' + non-3rd
   person verb)
   4. "Gartner's IT advice is used" was failed by ADVICE_ADVISE (advise
   (verb) instead of advice (noun))
   5. "reduce IT spend" was failed by IT_VBZ ('it' + non-3rd person verb)
   6. "IT consulting" was failed by I_MOVING (personal pronoun + gerund)
   7. "IT's" was failed by IT_IS (its vs. it's)

and so on, because most of my focus in on grammar I really need it not to
fail. How to solve this problem?
another problem which is less significant because it is spelling is the
fact that job titles such as CIO, CTO, CMO is correct spelling but when it
comes in plurar such as CIOs, CTOs and CMOs it is a spelling mistake.

Best Reagrds,
Idan Morad

Hi,

there's not much traffic here on the list. Some discussions happen on 
the github bug tracker, some happen at http://forum.languagetool.org. I 
suggest closing this mailing list and using our web forum instead. This 
should help against fragmentation of discussions.

You can follow the forum by email or by reading its RSS feed. What you 
cannot do is post to the forum by sending an email, you'll have to visit 
the forum for that. We probably wouldn't migrate to the forum in the 
sense that mailing list subscribers automatically get subscribed to the 
forum, they'd have to sign up at the forum by themselves. We could add a 
"development" category at the forum if needed.

Any thoughts?

Regards
  Daniel

Hi,

this is a final warning about our old HTTP/XML API being shut down in 7 
days. It has been replaced with a more coherent JSON-based API, as 
documented at https://languagetool.org/http-api/migration.php

For some time, the old API will then return an artificial "grammar 
error" on the first character of the text that describes that the API 
has been shut down and that points to the URL above.

As the old Firefox add-on "LanguageToolFx" also uses the old API, I have 
set its status to "hidden" on http://addons.mozilla.org. This shouldn't 
be an issue, as the new add-on called simply "LanguageTool" has been 
available for more than three months now.

Regards
  Daniel

Hi,

this is a reminder that we're now in feature freeze for LT 3.5, to be
released in 10 days. Please don't introduce any new strings that would
require translation and visit transifex to complete the existing
translations.

Also, please make sure your changes in the last 3 months are mentioned
in CHANGES.md.

Regards
  Daniel

Hello!

Could someone update the GB speller to my version 2.40:
https://github.com/marcoagpinto/aoo-mozilla-en-dict
?

Thanks!

Kind regards,
     >Marco A.G.Pinto
       ------------------------


-- 

Hi,

this is a reminder that the feature freeze for LT 3.5 will start
2016-09-20. The release is planned for Friday, 2016-09-30.

Regards
  Daniel

I did a quick POC for allowing back reference in match lemmas. The (rough)
patch is attached.

I must say I have mixed feelings about this: the logic in match state is
quite complicated, I've modified the code path that works for my rule and
also for the new test I've added. But tracing and testing all possible
scenarios there will be quite time consuming for person that didn't write
the logic. On the other hand currently \\[\d] leads to infinite loop so it
would be nice to do something about it.
I would say if we decide not to implement this feature we want to add a
sanity check and if there's \\[\d] iniside <match> we should throw an error
saying it's not supported.

Regards,
Andriy

P.S. Dominique is correct - the trick is that resulting postag is also
regex and the tags are not symmertical; but to be complete I should have
modified my rule a bit so it would also catch when fname has extra tags
lname does not, like this (without $2):
postag="(noun.*:m.*:)fname(.*)" postag_replace="$1lname.*"
the actual regexp you want highly depends on the tags you have though

2016-09-13 18:05 GMT-04:00 Dominique Pellé <dom...@gm...>:

> Jesper wrote:
>
> > It looks very strange to me to include ".*" in a replacement expression.
>
> I understand that it looks strange.  But in some cases, the result of
> replacement
> is a regexp. That's why regexp syntax can appear inside the
> regexp_replace="....".
>
> I see other examples in:
>
> - the Polish grammar.xml in rule "RYMY":
>
> <match no="0" regexp_match=".*([aeuóiyęą][^aeuóiyęą]+[aeuóiyęą]+[^aeuóiyęą]*)"
> regexp_replace=".*$1"></match>
>
> - the Breton grammar.xml in rule  KLANV_PE_GLANVOCH:
>
> <match no="0" regexp_match="^.(.*)" regexp_replace="(k|c’h)$1oc’h"/>
> <match no="0" regexp_match=".(.*)" regexp_replace="[tz]$1oc’h"/>
> <match no="0" regexp_match=".(.*)" regexp_replace="[pf]$1oc’h"/>
> <match no="0" regexp_match=".(.*)" regexp_replace="[gk]$1oc’h"/>
>
> I cannot tell whether the Polish one is OK, but the Breton replacements
> look OK - I wrote them :-)  - and the tests pass.
>
> Regards
> Dominique
>
>
> Jesper Hertel <jes...@gm...> wrote:
>
> > Yes, but I think those would be included in the $2 which catches
> everything
> > after fname (.*).
> > It looks very strange to me to include ".*" in a replacement expression.
> >
> > But now I stated my observation so it is up to you if you want to go into
> > it.
> >
> > Best,
> > Jesper
> >
> >
> > 2016-09-13 23:21 GMT+02:00 Andriy Rysin <ar...@gm...>:
> >>
> >> There are some cases where last name would have extra tags.
> >>
> >> Regards,
> >> Andriy
> >>
> >>
> >> On Sep 13, 2016 5:05 PM, "Jesper Hertel" <jes...@gm...>
> wrote:
> >>>
> >>> Hi Andriy,
> >>>
> >>> As a beginner in LanguageTool I know almost nothing about this, but I
> do
> >>> have a few decades of experience in regular expressions, and the .*
> looks
> >>> strange to me in a replacement expression:
> >>>
> >>> postag_replace="$1lname$2.*"
> >>>
> >>> Are you sure it shouldn't simply be
> >>>
> >>> postag_replace="$1lname$2"
> >>>
> >>> ?
> >>>
> >>> Best,
> >>> Jesper
> >>>
> >>>
> >>>
> >>> 2016-09-13 22:27 GMT+02:00 Andriy Rysin <ar...@gm...>:
> >>>>
> >>>> Sorry if this is already written somewhere - I looked at wiki pages
> but
> >>>> could not find anything relevant.
> >>>>
> >>>> I have two tokens (first name and last name) and in the suggestion I
> >>>> want to inflect second token the same as the first. I tried to do
> this:
> >>>>
> >>>> <suggestion><match no="1" postag_regexp="yes"
> >>>> postag="(noun.*:m.*:)fname(.*)"
> >>>> postag_replace="$1lname$2.*">\2</match></suggestion>
> >>>>
> >>>> but it sends the tests into 100% CPU loop and I don't have access to
> my
> >>>> Eclipse to try to debug this.
> >>>>
> >>>> Is there a right way to do this? If not does it make sense to look why
> >>>> we deadloop with logic above and try to fix it?
> >>>>
> >>>> Thanks
> >>>> Andriy
> >>>>
> >>>> P.S. I have similar logic for token inflection agreement in Java rules
> >>>> but it's pretty heavy and this was a simple case I thought I could do
> in xml
> >>>>
> >>>>
> >>>> ------------------------------------------------------------
> ------------------
> >>>>
> >>>> _______________________________________________
> >>>> Languagetool-devel mailing list
> >>>> Lan...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
> >>>>
> >>>
> >>>
> >>>
> >>> ------------------------------------------------------------
> ------------------
> >>>
> >>> _______________________________________________
> >>> Languagetool-devel mailing list
> >>> Lan...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
> >>>
> >>
> >>
> >> ------------------------------------------------------------
> ------------------
> >>
> >> _______________________________________________
> >> Languagetool-devel mailing list
> >> Lan...@li...
> >> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
> >>
> >
> >
> > ------------------------------------------------------------
> ------------------
> >
> > _______________________________________________
> > Languagetool-devel mailing list
> > Lan...@li...
> > https://lists.sourceforge.net/lists/listinfo/languagetool-devel
> >
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> Languagetool-devel mailing list
> Lan...@li...
> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>
>

Jesper wrote:

> It looks very strange to me to include ".*" in a replacement expression.

I understand that it looks strange.  But in some cases, the result of
replacement
is a regexp. That's why regexp syntax can appear inside the
regexp_replace="....".

I see other examples in:

- the Polish grammar.xml in rule "RYMY":

<match no="0"
regexp_match=".*([aeuóiyęą][^aeuóiyęą]+[aeuóiyęą]+[^aeuóiyęą]*)"
regexp_replace=".*$1"></match>

- the Breton grammar.xml in rule  KLANV_PE_GLANVOCH:

<match no="0" regexp_match="^.(.*)" regexp_replace="(k|c’h)$1oc’h"/>
<match no="0" regexp_match=".(.*)" regexp_replace="[tz]$1oc’h"/>
<match no="0" regexp_match=".(.*)" regexp_replace="[pf]$1oc’h"/>
<match no="0" regexp_match=".(.*)" regexp_replace="[gk]$1oc’h"/>

I cannot tell whether the Polish one is OK, but the Breton replacements
look OK - I wrote them :-)  - and the tests pass.

Regards
Dominique

Jesper Hertel <jes...@gm...> wrote:

> Yes, but I think those would be included in the $2 which catches
everything
> after fname (.*).
> It looks very strange to me to include ".*" in a replacement expression.
>
> But now I stated my observation so it is up to you if you want to go into
> it.
>
> Best,
> Jesper
>
>
> 2016-09-13 23:21 GMT+02:00 Andriy Rysin <ar...@gm...>:
>>
>> There are some cases where last name would have extra tags.
>>
>> Regards,
>> Andriy
>>
>>
>> On Sep 13, 2016 5:05 PM, "Jesper Hertel" <jes...@gm...> wrote:
>>>
>>> Hi Andriy,
>>>
>>> As a beginner in LanguageTool I know almost nothing about this, but I do
>>> have a few decades of experience in regular expressions, and the .*
looks
>>> strange to me in a replacement expression:
>>>
>>> postag_replace="$1lname$2.*"
>>>
>>> Are you sure it shouldn't simply be
>>>
>>> postag_replace="$1lname$2"
>>>
>>> ?
>>>
>>> Best,
>>> Jesper
>>>
>>>
>>>
>>> 2016-09-13 22:27 GMT+02:00 Andriy Rysin <ar...@gm...>:
>>>>
>>>> Sorry if this is already written somewhere - I looked at wiki pages but
>>>> could not find anything relevant.
>>>>
>>>> I have two tokens (first name and last name) and in the suggestion I
>>>> want to inflect second token the same as the first. I tried to do this:
>>>>
>>>> <suggestion><match no="1" postag_regexp="yes"
>>>> postag="(noun.*:m.*:)fname(.*)"
>>>> postag_replace="$1lname$2.*">\2</match></suggestion>
>>>>
>>>> but it sends the tests into 100% CPU loop and I don't have access to my
>>>> Eclipse to try to debug this.
>>>>
>>>> Is there a right way to do this? If not does it make sense to look why
>>>> we deadloop with logic above and try to fix it?
>>>>
>>>> Thanks
>>>> Andriy
>>>>
>>>> P.S. I have similar logic for token inflection agreement in Java rules
>>>> but it's pretty heavy and this was a simple case I thought I could do
in xml
>>>>
>>>>
>>>>
------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Languagetool-devel mailing list
>>>> Lan...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>>>>
>>>
>>>
>>>
>>>
------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Languagetool-devel mailing list
>>> Lan...@li...
>>> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>>>
>>
>>
>>
------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Languagetool-devel mailing list
>> Lan...@li...
>> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>>
>
>
>
------------------------------------------------------------------------------
>
> _______________________________________________
> Languagetool-devel mailing list
> Lan...@li...
> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>

Yes, but I think those would be included in the $2 which catches everything
after fname (.*).
​​
It looks very strange to me to include ".*" in a replacement expression.

But now I stated my observation so it is up to you if you want to go into
it.

Best,
Jesper​


2016-09-13 23:21 GMT+02:00 Andriy Rysin <ar...@gm...>:

> There are some cases where last name would have extra tags.
>
> Regards,
> Andriy
>
> On Sep 13, 2016 5:05 PM, "Jesper Hertel" <jes...@gm...> wrote:
>
>> Hi Andriy,
>>
>> As a beginner in LanguageTool I know almost nothing about this, but I do
>> have a few decades of experience in regular expressions, and the .* looks
>> strange to me in a replacement expression:
>>
>> postag_replace="$1lname$2.*"
>>
>> Are you sure it shouldn't simply be
>>
>> postag_replace="$1lname$2"
>>
>> ?
>>
>> Best,
>> Jesper
>>
>>
>>
>> 2016-09-13 22:27 GMT+02:00 Andriy Rysin <ar...@gm...>:
>>
>>> Sorry if this is already written somewhere - I looked at wiki pages but
>>> could not find anything relevant.
>>>
>>> I have two tokens (first name and last name) and in the suggestion I
>>> want to inflect second token the same as the first. I tried to do this:
>>>
>>> <suggestion><match no="1" postag_regexp="yes"
>>> postag="(noun.*:m.*:)fname(.*)" postag_replace="$1lname$2.*">\
>>> 2</match></suggestion>
>>>
>>> but it sends the tests into 100% CPU loop and I don't have access to my
>>> Eclipse to try to debug this.
>>>
>>> Is there a right way to do this? If not does it make sense to look why
>>> we deadloop with logic above and try to fix it?
>>>
>>> Thanks
>>> Andriy
>>>
>>> P.S. I have similar logic for token inflection agreement in Java rules
>>> but it's pretty heavy and this was a simple case I thought I could do in xml
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>>
>>> _______________________________________________
>>> Languagetool-devel mailing list
>>> Lan...@li...
>>> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>>>
>>>
>>
>> ------------------------------------------------------------
>> ------------------
>>
>> _______________________________________________
>> Languagetool-devel mailing list
>> Lan...@li...
>> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>>
>>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> Languagetool-devel mailing list
> Lan...@li...
> https://lists.sourceforge.net/lists/listinfo/languagetool-devel
>
>