2017-02-06 19:02 GMT+03:00 Xavi Ivars <[email protected]>:
>
>
> 2017-02-06 16:38 GMT+01:00 Toyama Tokanawa <[email protected]>:
>
>>
>>
>> Hi!
>>
>> Is there a way to somehow check if my changes break something for other
>> language pairs? Do I have to install and test all apertium packages that
>> involve "fra", for every commit I do?
>>
>> The changes I introduced to apertium-fra were "aligned" with the ways
>> they handle pronouns in apertium-fra-eng and apertium-eng-deu.
>>
>> Anyway, I'll contact the maintainer of apertium-fra-cat and hopefully,
>> we'll get it sorted out.
>>
>>
> There's really no "maintainer" of apertium-fra-cat. Hèctor, myself and a
> few other people contribute once in a while adding new words/rules, but the
> pair is already released as stable (you'll see is the only package using
> apertium-fra that is in /trunk/).
>
> So I think we're the ones that need to sort this out :)
>
> --
> < Xavi Ivars >
> < http://xavi.ivars.me >
>
I don't really know if there is an easy way to test the Apertium packages,
but if one introduces changes in a language (not just new words or
correcting bugs), there are a lot of chances to bother other developers.
The "alieneation" of apertium-fra-eng and apertium-eng-deu
"dealineated" apertium-fra-cat,
a released pair. It's important to understand the possible consequences of
changes in shared resources like apertium-fra. Well, this kind of things
happen. We'd be happy if you could rollback this and similar changes. We've
noticed just this one until now.
Hèctor
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
