Re: [Apertium-stuff] Demande d'information fedora 33 apertium

[Tino Didriksen]

I have now enabled Fedora 33, though there are some new weird build
failures I need to deal with.

I often forget to enable new Fedora versions because OBS takes a while to
allow them, so I have to remember to check OBS 1-2 months after the
distro's release ... and I forget to do that. One of the things I want to
do is move RPM builds back under my own control, to avoid this and many
other issues.

Plus I've been fighting an osc failure for a while, and only just now found
this workaround:
https://github.com/openSUSE/osc/issues/771#issuecomment-668556447

-- Tino Didriksen


On Sat, 5 Dec 2020 at 19:03, KADIK Stéphane  wrote:

> Bonjour,
>
> J'utilise fedora et apertium depuis plusieurs années.
>
> J'aimerais savoir s'il existe un dépôt
> http://download.opensuse.org/repositories/home:/TinoDidriksen:/nightly/Fedora_33/
>  ?
>
> Car je ne l'ai pas trouvé sur internet.
>
> Merci pour votre réponse.
>
> Stéphane KADIK
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] An easy tool to report bad translations and propose alternatives

[Flammie A Pirinen]

On Sat, Dec 05, 2020 at 12:28:14PM +0300, Hèctor Alòs i Font wrote:
> A Sardinian collaborator commented to me: "Wouldn't it be possible that
> every time there are more possible translations these come out in a little
> window where the user chooses the right solution, as in spell checkers"?

> This could be an idea for a GSoC tool project. Nevertheless, I don't think
> that, as he puts it, this is the best option because, in general, we have
> few multiple options in the bilingual dictionaries. Probably, another type
> of interface would be more appropriate. Is there anything done in the GSoC
> projects that could be used?

Which app are we talking about here? I proposed this kind of stuff for
the apertium webpage for GSOC regarding to untranslated words,
and as far as I understood it is done but not enabled? I think it could
be used for this kind of stuff as well?  I think "suggest a better
translation" kind of feature there, that can be optionally populated
with the alternative translations, would be quite ok for this.
Google translate has had some similar stuff too in the past.

One of the good things for stuff like this is iI envision that we can collect a
corpus of good and bad translations that can be useful for lots of
research projects.


-- 
Regards, Flammie 
(Please note, that I will often include my replies inline instead of
top or bottom of the mail)


signature.asc
Description: PGP signature
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] An easy tool to report bad translations and propose alternatives

[Daniel Swanson]

One thing that occurs to me is to have the form check the edit distance
between the output and the suggestion and if they're too far apart notify
the user, because it seems rather unlikely that the translator would get
every single word wrong. That might cut down on useless results a little
bit (though a decent number of people would probably just hit the "yes, I
mean it" button regardless).

On Sat, Dec 5, 2020 at 11:27 AM Xavi Ivars  wrote:

> I did that for quite a long time for Softcatalà, and gave up: most of the
> reports were actually wrong or useless. From people that picked the wrong
> language pair, to people who was suggesting wrong translations, including
> many people writing something like "this is wrong" in the form.
>
>
> --
> Xavi Ivars
> < http://xavi.ivars.me >
>
> El ds., 5 de des. 2020, 12:24, Tino Didriksen  va
> escriure:
>
>> We can trivially make a Report Bad Translation button on the website that
>> pops up a 3-field dialog, where the input (static), output (static), and
>> user's correction (that they fill in) can be submitted to a database.
>>
>> -- Tino Didriksen
>>
>>
>> On Sat, 5 Dec 2020 at 10:28, Hèctor Alòs i Font 
>> wrote:
>>
>>> A Sardinian collaborator commented to me: "Wouldn't it be possible that
>>> every time there are more possible translations these come out in a little
>>> window where the user chooses the right solution, as in spell checkers"?
>>>
>>> This could be an idea for a GSoC tool project. Nevertheless, I don't
>>> think that, as he puts it, this is the best option because, in general, we
>>> have few multiple options in the bilingual dictionaries. Probably, another
>>> type of interface would be more appropriate. Is there anything done in the
>>> GSoC projects that could be used?
>>>
>>> With him, we use a simple spreadsheet in a Google Documents-like system.
>>> He enters a word or phrase, the current translation, the suitable
>>> translation and the context (sentence). This is not at all intuitive, nor
>>> easy, for a conventional user, but it is very useful. We have already dealt
>>> with several hundred errors in the Italian-Sardinian translator.
>>>
>>> Hèctor
>>>
>> ___
>> Apertium-stuff mailing list
>> Apertium-stuff@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>>
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] An easy tool to report bad translations and propose alternatives

[Xavi Ivars]

I did that for quite a long time for Softcatalà, and gave up: most of the
reports were actually wrong or useless. From people that picked the wrong
language pair, to people who was suggesting wrong translations, including
many people writing something like "this is wrong" in the form.


--
Xavi Ivars
< http://xavi.ivars.me >

El ds., 5 de des. 2020, 12:24, Tino Didriksen  va
escriure:

> We can trivially make a Report Bad Translation button on the website that
> pops up a 3-field dialog, where the input (static), output (static), and
> user's correction (that they fill in) can be submitted to a database.
>
> -- Tino Didriksen
>
>
> On Sat, 5 Dec 2020 at 10:28, Hèctor Alòs i Font 
> wrote:
>
>> A Sardinian collaborator commented to me: "Wouldn't it be possible that
>> every time there are more possible translations these come out in a little
>> window where the user chooses the right solution, as in spell checkers"?
>>
>> This could be an idea for a GSoC tool project. Nevertheless, I don't
>> think that, as he puts it, this is the best option because, in general, we
>> have few multiple options in the bilingual dictionaries. Probably, another
>> type of interface would be more appropriate. Is there anything done in the
>> GSoC projects that could be used?
>>
>> With him, we use a simple spreadsheet in a Google Documents-like system.
>> He enters a word or phrase, the current translation, the suitable
>> translation and the context (sentence). This is not at all intuitive, nor
>> easy, for a conventional user, but it is very useful. We have already dealt
>> with several hundred errors in the Italian-Sardinian translator.
>>
>> Hèctor
>>
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] An easy tool to report bad translations and propose alternatives

[Tino Didriksen]

We can trivially make a Report Bad Translation button on the website that
pops up a 3-field dialog, where the input (static), output (static), and
user's correction (that they fill in) can be submitted to a database.

-- Tino Didriksen


On Sat, 5 Dec 2020 at 10:28, Hèctor Alòs i Font 
wrote:

> A Sardinian collaborator commented to me: "Wouldn't it be possible that
> every time there are more possible translations these come out in a little
> window where the user chooses the right solution, as in spell checkers"?
>
> This could be an idea for a GSoC tool project. Nevertheless, I don't think
> that, as he puts it, this is the best option because, in general, we have
> few multiple options in the bilingual dictionaries. Probably, another type
> of interface would be more appropriate. Is there anything done in the GSoC
> projects that could be used?
>
> With him, we use a simple spreadsheet in a Google Documents-like system.
> He enters a word or phrase, the current translation, the suitable
> translation and the context (sentence). This is not at all intuitive, nor
> easy, for a conventional user, but it is very useful. We have already dealt
> with several hundred errors in the Italian-Sardinian translator.
>
> Hèctor
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] An easy tool to report bad translations and propose alternatives

[Tanmai Khanna]

Also,
If someone proposes an alternative translation to a phrase, rather than
writing rules for disambiguation, lexical selection, transfer, generation,
etc. to fix the translation, there should be an option to just add it to
the translation memory until someone properly analyses it and adds the
rules. I know a TM exists in Apertium already, but I'm not sure if it's
being used on apertium.org, plus user given translations can definitely
improve TMs for language pairs that don't have a lot of parallel corpora to
learn TMs from.

*तन्मय खन्ना *
*Tanmai Khanna*


On Sat, Dec 5, 2020 at 2:59 PM Hèctor Alòs i Font 
wrote:

> A Sardinian collaborator commented to me: "Wouldn't it be possible that
> every time there are more possible translations these come out in a little
> window where the user chooses the right solution, as in spell checkers"?
>
> This could be an idea for a GSoC tool project. Nevertheless, I don't think
> that, as he puts it, this is the best option because, in general, we have
> few multiple options in the bilingual dictionaries. Probably, another type
> of interface would be more appropriate. Is there anything done in the GSoC
> projects that could be used?
>
> With him, we use a simple spreadsheet in a Google Documents-like system.
> He enters a word or phrase, the current translation, the suitable
> translation and the context (sentence). This is not at all intuitive, nor
> easy, for a conventional user, but it is very useful. We have already dealt
> with several hundred errors in the Italian-Sardinian translator.
>
> Hèctor
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] An easy tool to report bad translations and propose alternatives

[Hèctor Alòs i Font]

A Sardinian collaborator commented to me: "Wouldn't it be possible that
every time there are more possible translations these come out in a little
window where the user chooses the right solution, as in spell checkers"?

This could be an idea for a GSoC tool project. Nevertheless, I don't think
that, as he puts it, this is the best option because, in general, we have
few multiple options in the bilingual dictionaries. Probably, another type
of interface would be more appropriate. Is there anything done in the GSoC
projects that could be used?

With him, we use a simple spreadsheet in a Google Documents-like system. He
enters a word or phrase, the current translation, the suitable translation
and the context (sentence). This is not at all intuitive, nor easy, for a
conventional user, but it is very useful. We have already dealt with
several hundred errors in the Italian-Sardinian translator.

Hèctor
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff