Re: [Apertium-stuff] Question sus la desambigüizacion dins Apertium

[Tino Didriksen]

G'day,

Questions like these should really go to the whole mailing list, so I've
added it.

The pipe can handle language variations in a few ways.

There is the FST variant, to handle different scripts (e.g. Latin vs.
Cyrillic) and false friends, which apertium-oci-fra uses for the _gascon
mode. More recently, there is the preferences system, to handle semantic or
preferential differences.

Both are documented at
https://wiki.apertium.org/wiki/Dialectal_or_standard_variation - and the
mailing list and IRC can answer further questions.

-- Tino Didriksen


On Tue, 4 Jun 2024 at 17:44, Aure Séguier  wrote:

> Adiu
>
> Soi Aure Séguier. Contribuissi a l'Apertium occitan dins l'encastre de mon
> trabalh al Congrès permanent de la lenga occitana.
>
> Coma sèm a soscar a i ajustar d'autras varietats (primièr enriquesir
> l'occitan aranés, mas mai tard ajustar tanben lo lemosin e lo provençal),
> sèm a soscar a la gestion de la varietat de faiçon mai larga. Dins aquel
> encastre, ai una question rapòrt a l'analisi morfosintaxica (Hectòr Alòs me
> diguèt qu'èras la persona a la quala demandar).
>
> Es possible de far de règlas de desambiguïzacion especificas a una
> varietat ? Per exemple, en gascon, avèm los enonciatius ("que", "ne", etc.)
> qu'existisson pas dins las autras varietats. Se cambiam lo sistèma de
> gestion de las varietats, serà benlèu pas pus possible d'indicar dins lo
> monodix que "que" (enonciatiu) existís sonque en gascon. Riscarà d'èstre
> reconegut en lengadocian e de faussar la traduccion. I a tanben d'autres
> cases especifics ("de" partitiu que se ditz quasi pas jamai en gascon, mas
> totjorn en lengadocian...).
>
> Se es pas possible de far de règlas especificas a una varietat, es quicòm
> que se pòt pensar per l'avenidor ? Se òc, amb quala carga de trabalh e
> qualas competéncias ?
>
> Mercés
> --
> Aure SÉGUIER
>
> Responsabla del pòle informatic
>
> Congrès permanent de la lenga occitana
>
>
>
> [image: mobilePhone] +33 (0)5 32 00 00 64 <+33%20(0)5%2032%2000%2000%2064>
> [image: website] www.locongres.org 
> [image: address] La Ciutat - Creem! , 5-7 rue de la Fontaine, 64000 Pau
>
>
>
>
> [image: facebook] <https://www.facebook.com/lo.congres>
>
> [image: twitter] <https://twitter.com/locongres>
>
> [image: linkedin]
> <https://www.linkedin.com/company/congres-permanent-de-la-lenga-occitane/>
>
> [image: instagram] <https://www.instagram.com/locongres/>
>
>
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] GSoC 2024 mentors & admins must log in

[Tino Didriksen]

Yes, even if you already registered last year. We just got a warning that
we only have 1 admin (me), even though I was sure we had 3. So,
https://summerofcode.withgoogle.com/

"Before you can add an Org Member who has participated in previous programs
to your organization for 2024, they must first agree to the 2024 Program
Rules and Org Member agreement by logging into their GSoC dashboard and
clicking the 2024 and expanding it to see the 2024 Terms."

As soon as possible, or we'll be kicked out of the program.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Fwd: GSoC 2024: Thanks for submitting Apertium's application

[Tino Didriksen]

-- Forwarded message -
From: 
Date: Tue, 6 Feb 2024 at 17:58
Subject: GSoC 2024: Thanks for submitting Apertium's application

[image: Google Summer of Code]

Thank you for submitting your application for Apertium to be a part of
Google Summer of Code 2024.

You will be informed on February 20, 2024 if your organization has been
accepted to participate as a mentor organization.

Included below is the information you submitted as part of your Program
Application:

   - Ideas List URL:
   https://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code
   - Number of Mentors: 6

If there are any issues with the information (captured above) from your
application, withdraw your application from your dashboard
 and
submit a new one before February 06, 2024.

You are receiving this email because of your participation in Google Summer
of Code 2024.
https://summerofcode.withgoogle.com

For any questions, please contact gsoc-supp...@google.com. Replies to this
message go to an unmonitored mailbox.

© 2024 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Apertium in GSoC 2024?

[Tino Didriksen]

[CC: -stuff and PMC]

Should we apply for Google Summer of Code this year? Deadline Feb 6th.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] GSoC 2023 Code Collection

[Tino Didriksen]

https://apertium.projectjj.com/gsoc2023/ updated - let me know if something
is missing.

-- Tino Didriksen


On Thu, 24 Aug 2023 at 19:07, Tino Didriksen  wrote:

> As for previous years, I will run a code collection for GSoC changes.
>
> I just need to know who and what. GitHub usernames, the emails you use for
> them, and what repos you want included.
>
> The results wind up at https://apertium.projectjj.com/gsoc2023/ where I
> have already added AhmedSiam.
>
> The extraction script itself is pretty simple PHP code:
> https://apertium.projectjj.com/gsoc2023/extract.txt
>
> -- Tino Didriksen
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] GSoC 2023 Code Collection

[Tino Didriksen]

As for previous years, I will run a code collection for GSoC changes.

I just need to know who and what. GitHub usernames, the emails you use for
them, and what repos you want included.

The results wind up at https://apertium.projectjj.com/gsoc2023/ where I
have already added AhmedSiam.

The extraction script itself is pretty simple PHP code:
https://apertium.projectjj.com/gsoc2023/extract.txt

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] newbie

[Tino Didriksen]

No, there is currently no way to run the whole pipe in Java, and we have no
plans to upgrade the Java port to be usable.

For easier administration, you can run Apertium in a Debian/Ubuntu Docker
container. Either via the apertium-apy server, or execute the pipe directly.

Pure Android version would similarly need a native NDK build of the tools.
We know it all builds on NDK and runs on Android, but haven't taken the
time to build an actual app.

-- Tino Didriksen

On Tue, 22 Aug 2023 at 13:30, Zoltan Levardy  wrote:

> Thank you Kevin
>
> I was asked to find offline translator for a tomcat based webapp. Tomcat
> itself is running on linux (development on win and mac). Our goal was with
> pure java to get less integration issues with system administration and to
> keep all logic in the same (WAR) file. But know my understanding, that
> lttoolbox-java is part of the game.
> No way to get a java only version? Even how pure android version would go?
>
> thx
>
> > On 2023. Aug 22., at 9:31, Kevin Brubeck Unhammer 
> wrote:
> >
> > Hi,
> >
> > lt-proc is just one part of the pipeline, you also need transfer, tagger
> > etc. – the full pipeline is at
> >
> https://github.com/apertium/apertium-eng-deu/blob/master/modes.xml#L19..L62
> > It also depends on cg-proc, lsx-proc and lrx-proc which don't have Java
> > ports. So as of now, you can't run it with just lttoolbox.jar. The
> > easiest option is to just shell out to the regular Apertium pipeline.
> >
> > Is this meant to run on Android or something since you're looking at
> > Java?
> >
> > best regards,
> > Kevin Brubeck Unhammer
> >
> >
> >
> > ___
> > 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] Installing in a new system partition

[Tino Didriksen]

I don't package for 32bit Debian Bullseye - only 64bit. If you need 32bit
and nightly packages, then you can run 32bit Debian Sid in Docker or chroot.

32bit is on the verge of being dropped entirely, for many reasons.

-- Tino Didriksen


On Sat, 24 Jun 2023 at 17:38, Bernard Chardonneau 
wrote:

> Hello
>
> I try to install apertium in a partition with a new OS just installed
> before :
> a Debian 11 (bullseye) 32 bits.
>
> After following
> https://wiki.apertium.org/wiki/Install_Apertium_core_using_packaging
> I get these messages when doing :
> apt-get install apertium-all-dev
>
> 
>
> So, what to do to get a Apertium installation compatible with languages and
> language pairs compilations ?
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Ready to release: spa-arg 0.6.0 and arg-cat 0.3.0

[Tino Didriksen]

Done. Tarballs put on GitHub, website containers updated, and pushed
onwards to Debian experimental (due to freeze).

I had to branch off spa and cat's release tags because
https://github.com/apertium/apertium-spa/commit/03758b61fe6183a949938f2ae67ac5dcd3a8e9fc
and
https://github.com/apertium/apertium-cat/commit/2fbc818f3e23c10623eb977189281735ef98a045
by donissegui broke the build. The build is still broken in the default
branches - someone please fix those.

-- Tino Didriksen


On Fri, 5 May 2023 at 01:23, Juan Pablo  wrote:

> Dear all,
>
> The pairs Spanish-Aragonese and Aragonese-Catalan are ready to release
> (can anyone tag them?)
>
> apertium-spa-arg 0.6.0 (commit 61048e9) depends on apertium-spa (commit
> d2455cf, needs new tag)  and apertium-arg 0.2.0 (commit 0b9f06e).
>
> apertium-arg-cat 0.3.0 (commit 5255af5) depends on apertium-arg 0.2.0
> (commit 0b9f06e) and apertium-cat (commit 201dcec, needs new tag).
>
> Although they include some new entries and paradigms (especially in the
> monolingual apertium-arg), the mean reason for the release is that both
> pairs have been adapted to generate Aragonese according to the new
> official spelling system approved by the Academia Aragonesa de la Lengua
> (while still analyzing text with the previous spelling system).
>
> Best,
>
> Juan Pablo
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] G Soc candidate:Interested in Project Web API extensions

[Tino Didriksen]

You can apply for anything you like. The project requires little more than
knowing Python and HTML5.

-- Tino Didriksen


On Sat, 1 Apr 2023 at 20:20, pratham bhanushali <
prathambhanushal...@gmail.com> wrote:

> Hello
>
> I hope this email finds you well. I am very interested in this project but
>  there was no coding challenge so I was afraid to apply to this project I
> completed the coding challenge of the localization project .But I am more
> inclined toward this project. Since the deadline is near can I apply for
> this project
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apply for GSOC [English-Bodo language pair]

[Tino Didriksen]

"User account Maharaj was created and password was sent by email"

-- Tino Didriksen


On Mon, 3 Apr 2023 at 07:49, Maharaj Brahma via Apertium-stuff <
apertium-stuff@lists.sourceforge.net> wrote:

> Hello Hector,
>
> I have been working on the coding challenge, and I'm facing many
> difficulties in doing so in respect to the references materials for Bodo
> language. I will further elaborate this in subsequent communications.
>
> Can I have wiki access?
>
> possible username: maharaj
>
> Thanks!
>
> With Regards,
> Maharaj Brahma
> Research Scholar
> Dept. of Computer Science & Engineering
> CS23RESCH01004
>
>
> On Sat, Mar 25, 2023 at 1:22 AM Maharaj Brahma 
> wrote:
>
>> Thanks, Hector, for the quick reply.
>>
>> I agree with your comments and acknowledge the difficulties. However, I
>> believe that language technologies such as Apertium can significantly
>> impact. Therefore, your suggestion of Developing a Morphological Analyser
>> for Bodo is a prerequisite to making English-Bodo language pair possible in
>> Apertium in the near future. I want to take this up if selected for the
>> GSoC 2023 program.
>>
>> I hope to contribute to Apertium beyond the GSoC.
>>
>> I have already installed apertium. I agree lexd is a best choice of
>> parser for Bodo as it is an aggulative, and morphologically rich language.
>> Also, I'm already on IRC (under the handle maharaj), and would like to know
>> more about the coding challenge.
>>
>> With Regards,
>> Maharaj Brahma
>> Research Scholar
>> Dept. of Computer Science & Engineering
>> CS23RESCH01004
>>
>>
>> On Fri, Mar 24, 2023 at 11:29 PM Hèctor Alòs i Font 
>> wrote:
>>
>>> Hi, Maharaj,
>>>
>>> Bodo seems to me to be an excellent language for Apertium.
>>> Unfortunately, we have no morphological parser for it, even embryonic.
>>> That's why  to develop one seems to me much more realistic than to think of
>>> an automatic translator project between Bodo and another language (and even
>>> more so, if it belongs to another language family).
>>>
>>> It would therefore be a matter of doing this type of project:
>>> https://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code#Develop_a_morphological_analyser
>>>
>>>
>>> I've been looking a bit at the morphology of the language, and lexd [2]
>>> seems the best choice for developing a parser (e.g. because of the
>>> possessive prefixes).
>>>
>>> It would now be a matter of making the coding challenge of the project.
>>> There are about ten days left before the deadline. That is not a lot of
>>> time.
>>>
>>> I would suggest joining IRC to get faster help, if needrf:
>>> https://wiki.apertium.org/wiki/IRC
>>>
>>> Best regards,
>>> Hèctor
>>>
>>> [1] https://github.com/apertium/lexd
>>>
>>> Missatge de Maharaj Brahma via Apertium-stuff <
>>> apertium-stuff@lists.sourceforge.net> del dia dv., 24 de març 2023 a
>>> les 15:54:
>>>
>>>> Dear Apertium folks,
>>>>
>>>> I'm writing to express my interest in participating in the GSoC with
>>>> Apertium. I'm a first-year Ph.D. student in the NLP domain. I'm excited to
>>>> work with the Apertium community on developing translation technology for
>>>> low-resource languages, particularly Bodo. Bodo is a low-resource language
>>>> primarily spoken in the Northeastern region of India. As an NLP researcher
>>>> and native speaker of Bodo, I'm committed to building technology to
>>>> preserve and promote indigenous languages like Bodo.
>>>>
>>>> I'm interested in adding a new language English-Bodo to the Apertium
>>>> platform through this GSoC program or otherwise. I believe this can
>>>> potentially impact the translation technology for low resources.
>>>> Additionally, due to the following points:
>>>> (i) There is no existing publicly available translation technology for
>>>> English-Bodo.
>>>> (ii) Bodo is a low-resource language (potentially ample contribution
>>>> space remains).
>>>> (iii) Belongs to the Sino-Tibetan language family, unlike other Indian
>>>> languages like Hindi and Assamese.
>>>>
>>>> I would like to know if this is a potential project. If so, I would
>>>> like to interact with potential mentors.
>>>>
>>>> Any c

Re: [Apertium-stuff] Formally deprecate lttoolbox-java?

[Tino Didriksen]

True, but it's not much work to make it run on Linux. Just have to call
gksudo instead of downloading 7z files.

Since it seems OmegaT is important to people, I'll commit to ensuring
omegat-native works on the same platforms that the nightly builds target,
before marking lttoolbox-java as deprecated.

-- Tino Didriksen


On Mon, 27 Mar 2023 at 10:24, Felipe Sánchez Martínez 
wrote:

> Hi,
>
> According to the wiki this plugin does not work on Linux.
>
> Felipe
> El 26/3/23 a las 21:32, Tino Didriksen escribió:
>
> The replacement is https://github.com/apertium/apertium-omegat-native -
> which admittedly also needs updating, but it's far easier to get functional
> again.
>
> -- Tino Didriksen
>
>
> On Sun, 26 Mar 2023 at 21:06, Felipe Sánchez Martínez 
> wrote:
>
>> Hi all,
>>
>> I guess that the Apertium plugin for OmegaT is running internally
>> lttoolbox-java. I do no have information on the amount of people using this
>> plugin, but I guess there are some (me for example). How much time would it
>> cost to port the latter developments to Java?
>>
>> Regards
>>
>> Felipe
>> El 26/3/23 a las 19:12, Tino Didriksen escribió:
>>
>> [CC apertium-stuff & PMC]
>>
>> Cf. https://github.com/apertium/organisation/issues/34
>>
>> Given that lttoolbox-java and its downstream dependents have been falling
>> further and further behind the native tools, I say we formally deprecate
>> the Java port, mark all related wiki pages with a warning, and archive the
>> relevant repos.
>>
>> -- Tino Didriksen
>>
>>
>>
>> ___
>> Apertium-stuff mailing 
>> listApertium-stuff@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/apertium-stuff
>>
>> --
>> [image: Universitat d'Alacant / Universidad de Alicante]
>>
>> Dept. de Llenguatges i Sistemes Informàtics
>>
>> Felipe Sánchez Martínez
>>
>> Associate Professor - Profesor Titular de Universidad
>>
>> Tel.: (+34) 965 90 34 00 ext. 2966
>>
>> Email: fsanc...@ua.es, fsanc...@dlsi.ua.es
>>
>> Web: https://www.dlsi.ua.es/~fsanchez/
>>
>
>
> ___
> Apertium-stuff mailing 
> listApertium-stuff@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
> --
> [image: Universitat d'Alacant / Universidad de Alicante]
>
> Dept. de Llenguatges i Sistemes Informàtics
>
> Felipe Sánchez Martínez
>
> Associate Professor - Profesor Titular de Universidad
>
> Tel.: (+34) 965 90 34 00 ext. 2966
>
> Email: fsanc...@ua.es, fsanc...@dlsi.ua.es
>
> Web: https://www.dlsi.ua.es/~fsanchez/
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Formally deprecate lttoolbox-java?

[Tino Didriksen]

The replacement is https://github.com/apertium/apertium-omegat-native -
which admittedly also needs updating, but it's far easier to get functional
again.

-- Tino Didriksen


On Sun, 26 Mar 2023 at 21:06, Felipe Sánchez Martínez 
wrote:

> Hi all,
>
> I guess that the Apertium plugin for OmegaT is running internally
> lttoolbox-java. I do no have information on the amount of people using this
> plugin, but I guess there are some (me for example). How much time would it
> cost to port the latter developments to Java?
>
> Regards
>
> Felipe
> El 26/3/23 a las 19:12, Tino Didriksen escribió:
>
> [CC apertium-stuff & PMC]
>
> Cf. https://github.com/apertium/organisation/issues/34
>
> Given that lttoolbox-java and its downstream dependents have been falling
> further and further behind the native tools, I say we formally deprecate
> the Java port, mark all related wiki pages with a warning, and archive the
> relevant repos.
>
> -- Tino Didriksen
>
>
>
> ___
> Apertium-stuff mailing 
> listApertium-stuff@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
> --
> [image: Universitat d'Alacant / Universidad de Alicante]
>
> Dept. de Llenguatges i Sistemes Informàtics
>
> Felipe Sánchez Martínez
>
> Associate Professor - Profesor Titular de Universidad
>
> Tel.: (+34) 965 90 34 00 ext. 2966
>
> Email: fsanc...@ua.es, fsanc...@dlsi.ua.es
>
> Web: https://www.dlsi.ua.es/~fsanchez/
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Formally deprecate lttoolbox-java?

[Tino Didriksen]

[CC apertium-stuff & PMC]

Cf. https://github.com/apertium/organisation/issues/34

Given that lttoolbox-java and its downstream dependents have been falling
further and further behind the native tools, I say we formally deprecate
the Java port, mark all related wiki pages with a warning, and archive the
relevant repos.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] GSoc candidate: Interested in Project: Localization (l10n/i18n) of Apterium tools

[Tino Didriksen]

G'day...

See
https://github.com/apertium/organisation/issues/28#issuecomment-803474833

Also, please communicate via the apertium-stuff mailing list and/or IRC so
that all mentors see the questions and answers. That way we can ensure
things get seen even if someone is unavailable.

-- Tino Didriksen


On Mon, 13 Mar 2023 at 10:57, pratham bhanushali <
prathambhanushal...@gmail.com> wrote:

> Hello.
>
> My name is Pratham Bhanushali. I am a third-year Information technology
> student at the University of Mumbai, India.
>
> I am very interested in contributing to  Project: *Localization
> (l10n/i18n) of Apertium tools*
>
>
> I am familiar with C, C++, XML, Java, Html, JavaScript , and python.
>
> I would like to be in touch with you and other mentors.
>
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Request for addition information about the project.

[Tino Didriksen]

G'day...

https://github.com/apertium/organisation/issues/28 should explain
everything you need to know about the project.

Also, please communicate via the apertium-stuff mailing list and/or IRC so
that all mentors see the questions and answers. That way we can ensure
things get seen even if someone is unavailable.

-- Tino Didriksen


On Fri, 24 Feb 2023 at 23:25, Md Tanvir Alfesani <
tanviralfesani3...@gmail.com> wrote:

> Respected Sir,
>
> I hope this email finds you well. My name is Md Tanvir Alfesani and I'm a
> student who is interested in contributing to Apertium's project,
> 'Localization of Apertium tools' for Google Summer of Code 2023.
>
> As I was going through the project idea, I realized that I need to learn
> more about the technology used in the project. I'm particularly interested
> in how I can use c++ to contribute to this project and was hoping you could
> help me get a better understanding of it. I would appreciate any advice or
> resources you could provide to help me prepare for the project.
>
> Thank you for taking the time to read my email. I look forward to hearing
> from you and hopefully working together on the project.
>
> Thank you.
>
> Best regards,
> Md Tanvir Alfesani
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Regarding the GSoC Project - WASM Compilation

[Tino Didriksen]

G'day...

The idea stems from https://github.com/apertium/organisation/issues/21 and
I did a quick test in https://github.com/apertium/wasm to see if it was
viable. It is, and that's where I left it.

We haven't worked out a coding challenge for this yet, but a good start
would be to get the existing test building and run some text through it.

Also, please communicate via the apertium-stuff mailing list and/or IRC so
that all mentors see the questions and answers. That way we can ensure
things get seen even if someone is unavailable.

-- Tino Didriksen


On Mon, 27 Feb 2023 at 03:54, Vinayak Nigam 
wrote:

> Hey,
> I'm Vinayak
> I'm a front-end developer who has worked with JS, C++ and ReactJS
> I am interested in the WASM Compilation Project and wanted more
> information and where I should start if I want to contribute to Apertium
> Also, could you tell me where further talks should take place?
> --
> From,
> *Vinayak*
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] GSoC Ideas project lengths

[Tino Didriksen]

We need to add expected project lengths to
https://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code - whether we
expect something is a half-time 175 hour or full-time 350 hour project.

See https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list
for reference.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] GSoC 2023 Mentors & Ideas?

[Tino Didriksen]

GSoC 2023 org application is open, but do we have mentors for this year?
Please report in if you want to mentor.

And as every year, please review
https://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code -
add/remove/amend ideas.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Released: swe-nor 0.4.0, dan-nor 1.5.0

[Tino Didriksen]

These are now all published on apertium.org, GitHub, and pushed to Debian.

-- Tino Didriksen


On Mon, 19 Dec 2022 at 13:22, Kevin Brubeck Unhammer 
wrote:

> Goddag,
>
> I've just tagged new releases of swe-nor and dan-nor.
>
> The work on swe-nor is partially funded by the Norwegian News Agency,
> and dan-nor by Store norske leksikon.
>
> For both pairs, all directions now use apertium-separable (lsx) and
> recursive transfer (rtx), with testing by apertium-regtest.
>
> Most of the work has been focused on the nob→{swe,dan} direction, but
> all directions have of course improved vocabulary and seem to have
> improved quality. The directions into Nynorsk are also usable with style
> preferences (though it hasn't been added to the UI yet in this release).
>
> Some stats:
>
> dan-nor:
> - Over 22.000 new non-name bidix entries
> - Over 300 new lexical selection rules
> - Over 300 new lexical selection rules
> - ~60 separable/mwe entries, including comma insertion rules for
>   generating Danish
>
> swe-nor:
> - Over 20.000 new non-name bidix entries
> - Over 300 new lexical selection rules manually added
> - Nearly 7000 new lexical selection rules based on corpus frequencies
> - ~30 separable/mwe entries
>
> and the newer monolingual dependencies mean much better bokmål
> disambiguation (and some improvements there for the other languages as
> well) as well as much better compound epenthetic choices and tweaks all
> round.
>
> Moving from chunking transfer to recursive for these pairs was a joy. I
> have spent very little time on the rules, but they already cover more
> than the old rules did, in much fewer lines of code (including comments
> and everything, dan-nor has ~1011 lines of rtx in one file per
> direction, and 8347 of t?x with three files per direction). Each
> direction has about 20 rtx rules (where a rule is NP→n|ncmp n|…), 50 if
> you count alternatives. There's a lot less redundancy than before, and
> the recursion means we can have e.g. compounds of arbitrary length.
>
> -Kevin
>
>
>
> ___
> 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] CG workshop at Nodalida 2023?

[Tino Didriksen]

Anyone got any new Constraint Grammars to potentially write about? Or novel
(ab)uses of CG? We're gathering interest for a CG workshop at
https://www.nodalida2023.fo/

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] New Occitan-French release

[Tino Didriksen]

On Fri, 4 Nov 2022 at 08:22, Hèctor Alòs i Font 
wrote:

> 1) We need a first CG process that finds out whether the text has
> enunciatives. Probably it should return somehow 0 or 1. How?
> 2) Depending on this, we will have two slightly different pipes, but
> how? Should the syntax of the modes.xml be expanded to include a kind
> of "if-else"?
>
> More generally, it would be desirable to have a first step that
> recognises from which variety of Occitan we are translating.
> Currently, we force the user to say whether he is translating from
> Languedocien (called "Occitan" in Apertium and "Occitan Languedocien"
> in the translator of the Congrès Permanent de la Lenga Occitana). A
> user does not necessarily know it. When there are two possibilities,
> there is not too much of a problem: try one and, if it doesn't work
> too well, try the other. But when we have four or more variants, it
> will be less obvious. But, for now, the question is to differentiate
> between two Gascon "flavours".
>

We can have a program in the single-pass pipe that will hold on to whole
paragraphs at a time, do some analysis on them, and then spit out
https://visl.sdu.dk/cg3/chunked/streamcmds.html#cmd-setvar or similar
metadata before them.

CG can by itself do this with lookahead, but it's not optimized for that
task. But making a hold-for-analysis tool is very easy - we just need to
define how big a chunk is. For documents that pass through Transfuse (HTML,
docx, etc) then the division is roughly on a natural paragraph level. But
for corpus streams we may need to just hold X bytes at a time. Or a
combination thereof.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] New Occitan-French release

[Tino Didriksen]

On Tue, 1 Nov 2022 at 11:45, Kevin Brubeck Unhammer 
wrote:

> Hèctor Alòs i Font 
> čálii:
>
> > As for your proposal, I do not yet have sufficient knowledge of CG to
> fully
> > understand it. My idea would be to make a first pass through a whole text
> > to understand if enunciatives are used in it (for example, recognising
> > other, more infrequent, but more easily recognisable enunciatives). In
> the
> > solution you propose, it seems that this knowledge is acquired
> > progressively, as sentences are translated. I fear that "que" is so messy
> > that at least the first sentences of a text would have the same problems
> as
> > we have now when we translate a Gascon text without enunciatives.
>
> That should be possible too, though I'm not sure how feasible it is to
> get CG to go that far into a text. By default, CG keeps a context of two
> windows, but that's configurable. It should be possible (perhaps with
> minor modifications to cg-proc) to read a bunch of sentences and use
> Window Spanning tests https://visl.sdu.dk/cg3/single/#test-spanning
>
> Tino, have you tried looking ahead several paragraphs, are there any
> downsides? This should be a fairly simple rule file.
>

The max I've seen in production is 9 windows, but there is no hard limit.
Just have to be careful of spanning tests, as they are going to look ahead
for every active window. A multi-pass system will perform better, and for
this particular task I'd say multi-pass is the correct approach.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Debian Bookworm freeze

[Tino Didriksen]

Debian Bookworm will close for new/updated packages in 3 months, so any
Apertium releases that we want in should happen soon.

-- Tino Didriksen

On Thu, 13 Oct 2022 at 10:00, Paul Gevers  wrote:

> On 12 January 2023 we're hitting the first milestone of the bookworm
> release: the Transition and Toolchain Freeze. If you made plans for
> the bookworm release, now is the time to evaluate if it's realistic to
> go ahead or if time is running too short. Keep in mind that others may
> have less time to work on your plans than you do.
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] [Apertium-contact] Apertium Simpleton UI bug

[Tino Didriksen]

It's almost certainly same as this:
https://github.com/apertium/apertium-simpleton/issues/6

-- Tino Didriksen


On Tue, 13 Sept 2022 at 03:01, Jonathan Washington <
jonathan.n.washing...@gmail.com> wrote:

> Hei Jørgen,
>
> Could you describe the problem in more detail?  We didn't receive the
> screenshot.
>
> P.S. I'm sorry that I couldn't respond to you in Norwegian, but please
> feel free to write back in Norwegian!  Plenty of people who can help you
> here know Norwegian.
>
> --
> Jonathan
>
> 31 avq 2022, Ç. tarixində 14:48 tarixində Jørgen Finsveen <
> jor...@stud.ntnu.no> yazdı:
>
>> Hei,
>>
>> Jeg har oppdaget en bug som oppstår når jeg prøver å oversette diverse
>> setninger på skrivebordsversjonen av Apertium simpleton. Dette har blitt
>> testet på en windows-11 maskin. Jeg har prøvd å framkalle den samme feilen
>> på MacOS, men der oppsto ikke denne buggen. Alle språkpakker samt «Required
>> Core Tools» og «apertium-all-dev» har blitt oppdatert uten at dette
>> påvirket resultatene. Bilde er vedlagt.
>>
>> Mvh
>> Jørgen Finsveen
>>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Bootstrapping a new language pair: lttoolbox version condition

[Tino Didriksen]

The most likely cause is that you don't have the tools from our nightly
repository:
https://wiki.apertium.org/wiki/Install_Apertium_core_using_packaging#Debian-based

So I recommend running:
$ curl -sS https://apertium.projectjj.com/apt/install-nightly.sh | sudo bash
$ sudo apt-get dist-upgrade
$ sudo apt-get install apertium-all-dev

-- Tino Didriksen


On Sat, 13 Aug 2022 at 15:48, Anil Singh  wrote:

> HI,
>
> I am trying to bootstrap a new language pair. One of them is available via
> apertium-get, but the other is not. So I tried using apertium-init.py. On
> running it, it seems to partially succeed, but I get an error regarding the
> version of lttoolbox.
>
> Trying to install lttoolbox from source code from GitHub also causes an
> error. However, I am able to build (skipping tests) lttoolbox-java and it
> seems to be working. This, I understand, is a complete port of both
> apertium and lttoolbox.
>
> Can I use lttoolbox-java.jar to initialize a new language? If so, how? Or
> is there a way to fix the error with version of lttoolbox:
>
> Requested 'lttoolbox >= 3.6.9' but version of lttoolbox is 3.6.6
>>
>
> I am working on Ubuntu WSL on Windows 10.
>
> Regards,
>
> Anil Kumar Singh
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium PMC Election: Bypass election?

[Tino Didriksen]

I think we can call it done. All the non-candidates who replied (both here
and on IRC) are in favour of unanimous consent.

Once we have a Foundation set up then we'll need elections every year, and
we'll need an initial vote to pass said Foundation's bylaws, so any
question of legitimacy will quickly be moot. And practically speaking, we
need Francis and Mikel's active involvement until a legally binding formal
structure exists. They personally hold the important assets (domains,
bank), so they are de facto benevolent dictators for life even if they want
otherwise. Not that there's ever been a question they'd veto something.

-- Tino Didriksen


On Wed, 27 Apr 2022 at 23:26, Bernard Chardonneau 
wrote:

> Well, in France we recently had a presidential election and for many
> people, neither of the 2 candidates selected for the 2nd round was
> fully satisfactory.
>
> For the PMC election, I'm happy to see that Unhammer who informed people
> a lot when I started working on apertium about 10 years ago is a candidate.
> Other PMC candidates also suit me and I would have voted for them. If I
> had to choose between 2 presidents, I would have voted for Francis.
> So for me too, whether there is an election or not, both are fine for me.
>
> One way to settle the problem could be to ask if there are volunteers
> among those who are not PMC candidates to organize the election.
>
> If we find 3 volunteers, it will be philosophically preferable to organize
> the election, even if it would take one month.
> If they are not found, and especially if there are no volunteers at all,
> we will be able to conclude that there is a consensus to accept all the
> candidates without proceeding to an election.
>
>
> > Date: Tue, 26 Apr 2022 21:11:54 +0530
> > From: Tanmai Khanna 
> > To: Tino Didriksen 
> > Cc: "\[apertium-stuff\]" 
> > Reply-To: apertium-stuff@lists.sourceforge.net
> > Subject: Re: [Apertium-stuff] Apertium PMC Election: Bypass election?
> > Pièce(s) jointes(s) probable(s)>
> > I get the sentiment but to be honest, not holding elections at all does
> > dent credibility a little. Tino offered to stand for President, and so
> did
> > Francis. Maybe we should have a vote, secure a mandate and then move on.
> >
> > That way it'll be clear to everyone that the leader is elected and not
> just
> > selected unopposed.
> >
> > What do you guys think?
> >
> > On Tue, Apr 26, 2022, 19:54 Tino Didriksen 
> wrote:
> >
> > > G'day everyone,
> > >
> > > It's been a week, and we have 7 candidates for PMC and 2 for President:
> > > https://github.com/apertium/elections
> > >
> > > - PMC: Francis M. Tyers, Jonathan N. Washington, Kevin Brubeck
> > > Unhammer, Mikel L. Forcada, Tanmai Khanna, Tino Didriksen, Xavi Ivars
> > >
> > > - President: Francis, Tino
> > >
> > > Given that exactly 7 for PMC would avoid the need for an election, I'm
> > > happy to forego the whole thing and let Francis continue in the role of
> > > President.
> > >
> > > So, I propose that if this is still the status by end-of-day UTC
> tomorrow
> > > (2022-04-27 23:59:59 UTC, ~34 hours from now), then we don't hold the
> > > election and simply replace Sushain K. Cherivirala with Kevin Brubeck
> > > Unhammer. CC'ed Sushain directly.
> > >
> > > -- Tino Didriksen
> > >
> >
> 
> Bernard Chardonneau (France)
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium PMC Election: Bypass election?

[Tino Didriksen]

There is precedence even in legislative bodies:
https://en.wikipedia.org/wiki/Unanimous_consent

We've given ample time and updates, and we have a possible outcome that can
be achieved by unanimous consent. I say we take it and get on with the
business of forming the Foundation, which the (new) PMC can delegate the
legwork of to anyone.

-- Tino Didriksen


On Tue, 26 Apr 2022 at 17:41, Tanmai Khanna  wrote:

> I get the sentiment but to be honest, not holding elections at all does
> dent credibility a little. Tino offered to stand for President, and so did
> Francis. Maybe we should have a vote, secure a mandate and then move on.
>
> That way it'll be clear to everyone that the leader is elected and not
> just selected unopposed.
>
> What do you guys think?
>
> On Tue, Apr 26, 2022, 19:54 Tino Didriksen  wrote:
>
>> G'day everyone,
>>
>> It's been a week, and we have 7 candidates for PMC and 2 for President:
>> https://github.com/apertium/elections
>>
>> - PMC: Francis M. Tyers, Jonathan N. Washington, Kevin Brubeck
>> Unhammer, Mikel L. Forcada, Tanmai Khanna, Tino Didriksen, Xavi Ivars
>>
>> - President: Francis, Tino
>>
>> Given that exactly 7 for PMC would avoid the need for an election, I'm
>> happy to forego the whole thing and let Francis continue in the role of
>> President.
>>
>> So, I propose that if this is still the status by end-of-day UTC tomorrow
>> (2022-04-27 23:59:59 UTC, ~34 hours from now), then we don't hold the
>> election and simply replace Sushain K. Cherivirala with Kevin Brubeck
>> Unhammer. CC'ed Sushain directly.
>>
>> -- Tino Didriksen
>>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Apertium PMC Election: Bypass election?

[Tino Didriksen]

G'day everyone,

It's been a week, and we have 7 candidates for PMC and 2 for President:
https://github.com/apertium/elections

- PMC: Francis M. Tyers, Jonathan N. Washington, Kevin Brubeck
Unhammer, Mikel L. Forcada, Tanmai Khanna, Tino Didriksen, Xavi Ivars

- President: Francis, Tino

Given that exactly 7 for PMC would avoid the need for an election, I'm
happy to forego the whole thing and let Francis continue in the role of
President.

So, I propose that if this is still the status by end-of-day UTC tomorrow
(2022-04-27 23:59:59 UTC, ~34 hours from now), then we don't hold the
election and simply replace Sushain K. Cherivirala with Kevin Brubeck
Unhammer. CC'ed Sushain directly.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Pair releases

[Tino Didriksen]

G'dair pair developers,

Unless someone has good reason to block a given pair, this weekend I will
make releases from current master/main state and push to Debian for all
repos listed in
https://qa.debian.org/developer.php?login=tino%40didriksen.cc

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium PMC Election: Census & Candidates

[Tino Didriksen]

Election status update before the weekend:

- No change to the census

- 4 candidates for the PMC: Francis Tyers, Tanmai Khanna, Tino Didriksen,
Xavi Ivars

- 2 candidates for President: Francis, Tino

- Auditor: Daniel Swanson

-- Tino Didriksen


On Tue, 19 Apr 2022 at 13:20, Tino Didriksen  wrote:

> G'day everyone,
>
> It is almost time to vote for the
> https://wiki.apertium.org/wiki/Project_Management_Committee again, but
> first some introductory motions, namely updating the census and calling for
> candidates.
>
> Actual election will start in a week, barring complications.
>
> === Census:
> See https://github.com/apertium/elections/blob/main/census.tsv
>
> If you are not on the census list and want to be, or we have the wrong
> email for you, or you wish to be removed from the census, let us know or
> submit a PR for the change.
>
> === Candidates:
> Do you want to be a PMC member? Speak up!
>
> Do you want to be the Apertium President? Likewise, speak up!
>
> Or amend the https://github.com/apertium/elections repo.
>
> === The election itself:
> We will likely use https://www.belenios.org/ to run the election itself,
> and while that doesn't require as much trust in the election runners, it'd
> still be nice if someone who isn't planning on running for PMC or President
> will want to be one of the admins for the election. Any volunteers?
>
> -- Tino Didriksen
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Apertium PMC Election: Census & Candidates

[Tino Didriksen]

G'day everyone,

It is almost time to vote for the
https://wiki.apertium.org/wiki/Project_Management_Committee again, but
first some introductory motions, namely updating the census and calling for
candidates.

Actual election will start in a week, barring complications.

=== Census:
See https://github.com/apertium/elections/blob/main/census.tsv

If you are not on the census list and want to be, or we have the wrong
email for you, or you wish to be removed from the census, let us know or
submit a PR for the change.

=== Candidates:
Do you want to be a PMC member? Speak up!

Do you want to be the Apertium President? Likewise, speak up!

Or amend the https://github.com/apertium/elections repo.

=== The election itself:
We will likely use https://www.belenios.org/ to run the election itself,
and while that doesn't require as much trust in the election runners, it'd
still be nice if someone who isn't planning on running for PMC or President
will want to be one of the admins for the election. Any volunteers?

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Apertium Google Cloud owner?

[Tino Didriksen]

Hello everyone,

Who owns https://console.cloud.google.com/home/dashboard?project=apertium ?

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] No GSoC 2022 for Apertium

[Tino Didriksen]

[forwarded]

-- Tino Didriksen


On Sun, 6 Mar 2022 at 19:01,  wrote:

> [image: Google Summer of Code]
>
> Thank you for applying to be a Google Summer of Code 2022 mentor
> organization. Sadly, we were unable to accept Apertium this year. We had
> many more applications than available slots. We hope you will apply again
> in the future!
>
> You are receiving this email because of your participation in Google
> Summer of Code 2022.
> https://summerofcode.withgoogle.com
>
> For any questions, please contact gsoc-supp...@google.com. Replies to
> this message go to an unmonitored mailbox.
>
> © 2022 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] issue with apertium

[Tino Didriksen]

G'day,

Unfortunately I haven't taken the time to add Windows builds of various
newer core tools. Mostly because there is no practical need any longer,
since there's the website for online translation and Windows 10's WSL for
offline translation and development environment. See
https://wiki.apertium.org/wiki/Installation#Install_Apertium_Core_by_packaging.2Fvirtual_environment

And I admit WSL or VirtualBox is much larger than what Simpleton installs,
but it is exceedingly rare that someone only wants to translate but also
needs it offline.

-- Tino Didriksen


On Sun, 27 Feb 2022 at 18:43, Samuel Sagatun 
wrote:

> Hello tino!
>
> I just want to say that Apertium has been a blessing on several occasions.
> Thanks for providing such a good service!
>
> Although, I seem to have an issue with apertium simpleton. I can translate
> in certain languages, like nor-dan, but not with the language package
> nob-nno.
>
> i get this fault code "lsx-proc is not recognized". the simpleton iu used
> to work a few years ago for nno-nob, but not anymore.
>
> Is there an easy solution for this?
>
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Apertium? GSoC Org Apps close Monday, Feb 21 at 1800 UTC

[Tino Didriksen]

Forgot about GSoC application - are we doing it this year? Has anyone
started the application yet?

-- Tino Didriksen


On Fri, 18 Feb 2022 at 22:23, 'sttaylor' via Google Summer of Code Mentors
List  wrote:

> Hi all,
>
> If your organization is interested in participating as a Mentor Org for
> GSoC 2022 be sure to complete your organization application *before
> Monday at 1800 UTC* by going to *g.co/gsoc <http://g.co/gsoc>*.
>
> Once you have completed the application you will receive an email letting
> you know your application will be reviewed over the next two weeks with
> orgs being contacted March 6th with their status. You can also verify you
> successfully submitted your application by looking at your Org Admin
> dashboard where you will see 'Application Submitted, Pending Approval.'
>
> Helpful Links
>
> Roles and Responsibilities
> <https://developers.google.com/open-source/gsoc/help/responsibilities>
>
> Timeline <https://developers.google.com/open-source/gsoc/timeline>, FAQs
> <https://developers.google.com/open-source/gsoc/faq>
>
> Marketing Materials
> <https://developers.google.com/open-source/gsoc/resources/marketing>
> (slide deck, flyers), Videos
> <https://developers.google.com/open-source/gsoc/videos>
>
>
> As always please feel free to email us at gsoc-supp...@google.com with
> any questions. Thanks!
>
> Best,
>
> Stephanie Taylor, GSoC Program Lead
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Request for the addition of New Santali Mono Dictionary and apertium-eng-sat pair

[Tino Didriksen]

It's not a Wikipedia site; it's our own wiki. Any of us admins can create
an account for you - what username do you want?

-- Tino Didriksen


On Sun, 9 Jan 2022 at 09:25, Prasanta Hembram 
wrote:

> Hi, I want to contribute something in documentation for the
> English-Santali pair. I'm unable to edit https://wiki.apertium.org/wiki/
> page. I have one wikipedia account that seems like it's credentials are not
> working. How to proceed?
>
> Thanks
> with regards
> Prasanta Hembram
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Request for the addition of New Santali Mono Dictionary and apertium-eng-sat pair

[Tino Didriksen]

Done:
- https://github.com/apertium/apertium-sat
- https://github.com/apertium/apertium-eng-sat

You've been added as maintainer for both.

-- Tino Didriksen

On Thu, 6 Jan 2022 at 20:00, Prasanta Hembram 
wrote:

> Hi,
> I was recently working for an English-Santali pair and have added some
> 1000 entries and updated some rules which will make it work for at least
> for nouns (mostly added names of people) and added some other words and
> parafdef which shows some plural forms. Is there any rule or threshold to
> add these language pairs or we can add at half completion also??. If not
> then I'm excited for this pair and one monodix to be passed to Apertium.
>
> Santali monodix: https://github.com/Prasanta-Hembram/apertium-sat
> English-Santali bidix:
> https://github.com/Prasanta-Hembram/apertium-eng-sat
>
> --
> Thanks
> with best regards
> Prasanta Hembram
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] English-Santali Plural form not working

[Tino Didriksen]

For the 3rd time, you can unsubscribe via:
https://sourceforge.net/projects/apertium/lists/apertium-stuff/unsubscribe

-- Tino Didriksen


On Tue, 21 Dec 2021 at 08:41, Ramansh Sharma  wrote:

> someone please unsubscribe me from this mailing list.
>
> --
> Ram
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Changes on apertium-apy

[Tino Didriksen]

Same as I replied to you 2 weeks ago, you can unsubscribe via:
https://sourceforge.net/projects/apertium/lists/apertium-stuff/unsubscribe

In addition, every email from the list has a footer with links to this
information.

-- Tino Didriksen


On Wed, 15 Dec 2021 at 07:51, Ramansh Sharma  wrote:

> I am begging the moderator for this conversation. Please unsubscribe me
> from this list. Or please tell me how to.
>
> --
> Ram
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Unsubscribe

[Tino Didriksen]

You can unsubscribe via:
https://sourceforge.net/projects/apertium/lists/apertium-stuff/unsubscribe

-- Tino Didriksen


On Thu, 2 Dec 2021 at 07:37, Uttam  wrote:

> Me as well
>
> best regards
>
> On Thu, Dec 2, 2021 at 12:03 PM Ramansh Sharma 
> wrote:
>
>> can someone unsubscribe me from this mailing list please?
>>
>> --
>> Ram
>>
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Apertium dependencies & support

[Tino Didriksen]

code
to build on the older distros, but there are limits. E.g., we require at
minimum C++14. Using newer versions of C++ cleans up the code quite a bit,
and newer libraries have important bug and security fixes.

4) "only with 64 bits processors"? No. Debian Sid is always the newest
versions of everything, and that's built as 32 bit. So we make sure
everything builds as 32 bit. But I don't want to waste build time on archs
that are unused, and 32 bit market share is vanishingly small.

So if you really need 32 bit, the newest versions of everything can be
installed in a 32 bit Debian Sid chroot or container.

5) "separately a version of the same apertium tools with the code of any
external functions" - absolutely bloody not. That would be such a huge
maintenance burden. There is no Standard C++ Unicode handler, so what
replacement for ICU do you propose? Same for the other needed libraries. We
don't use libraries for the fun of it or on a whim - we use them because
they're the best at what they do, where best is a combination of "widely
available in distros" and "quality output".

E.g., libxml2 is very old and there are several newer shinier XML
libraries, but they aren't as widely available nor can they handle HTML, so
we use libxml2.


Overall, for an open source project, I'd say we're doing very well. There's
a good balance between wanting to use new shiny things, but also wanting to
accommodate old distros (and Windows + macOS). We don't break backwards
compat just because - we break it when distros go EOL upstream.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] can't install language pairs packages on debian 11

[Tino Didriksen]

Yes, I don't build for 32 bit platforms any longer, except for Debian Sid
just to ensure it actually builds on 32 bit.

Why are you still running 32 bit? If there's a good reason, I can re-enable
32 bit builds for Debian. But other big distros no longer care - Ubuntu,
Fedora, etc, completely ditched 32 bit.

-- Tino Didriksen


On Thu, 18 Nov 2021 at 10:11, Alexander V 
wrote:

> Thanks for your reply.
>
> My system is 32-bit (Linux debian 5.10.0-9-686-pae #1 SMP Debian 5.10.70-1
> (2021-09-30) i686 GNU/Linux) , can it be the reason of this issue?
>
> чт, 18 нояб. 2021 г. в 10:34, Tino Didriksen :
>
>> Cannot reproduce - works for me.
>>
>> $ docker run -it --rm amd64/debian:bullseye /bin/bash
>> $ apt-get update
>> $ apt-get install apt-utils curl
>> $ curl -sS https://apertium.projectjj.com/apt/install-nightly.sh |  bash
>>
>> $ apt-cache policy apertium
>> apertium:
>>   Installed: (none)
>>   Candidate: 3.8.0+g862~6d1d2fb5-1~bullseye1
>>   Version table:
>>  3.8.0+g862~6d1d2fb5-1~bullseye1 1001
>>1001 http://apertium.projectjj.com/apt/nightly bullseye/main
>> amd64 Packages
>>  3.7.1-1 500
>> 500 http://deb.debian.org/debian bullseye/main amd64 Packages
>>
>> $ apt-get install apertium apertium-spa-ita
>>
>> $ echo 'Amplia gama, los mejores precios: proteínas, vitaminas,
>> aminoácidos y muchos más del fabricante.' | apertium spa-ita
>> Ampia gamma, i migliori prezzi: proteine, vitamine, amminoacidi e *muchos
>> più del fabbricante.
>>
>> -- Tino Didriksen
>>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] can't install language pairs packages on debian 11

[Tino Didriksen]

Cannot reproduce - works for me.

$ docker run -it --rm amd64/debian:bullseye /bin/bash
$ apt-get update
$ apt-get install apt-utils curl
$ curl -sS https://apertium.projectjj.com/apt/install-nightly.sh |  bash

$ apt-cache policy apertium
apertium:
  Installed: (none)
  Candidate: 3.8.0+g862~6d1d2fb5-1~bullseye1
  Version table:
 3.8.0+g862~6d1d2fb5-1~bullseye1 1001
   1001 http://apertium.projectjj.com/apt/nightly bullseye/main amd64
Packages
 3.7.1-1 500
500 http://deb.debian.org/debian bullseye/main amd64 Packages

$ apt-get install apertium apertium-spa-ita

$ echo 'Amplia gama, los mejores precios: proteínas, vitaminas, aminoácidos
y muchos más del fabricante.' | apertium spa-ita
Ampia gamma, i migliori prezzi: proteine, vitamine, amminoacidi e *muchos
più del fabbricante.

-- Tino Didriksen


On Wed, 17 Nov 2021 at 17:13, Alexander V 
wrote:

> Hi there! i tried to install, for example, apertium-eng-ita package on my
> debian system. but no luck, cause of dependencies. What was done:
>
> 1) clear debian 11 system installed
> 2) curl -sS https://apertium.projectjj.com/apt/install-nightly.sh |  bash
> 3) apt-get install apertium (and it installed the 3.7 version)
> 4) apt-get install apertium-spa-ita :
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Reading package lists... DoneBuilding dependency tree... DoneReading
> state information... DoneSome packages could not be installed. This may
> mean that you haverequested an impossible situation or if you are using the
> unstabledistribution that some required packages have not yet been
> createdor been moved out of Incoming.The following information may help to
> resolve the situation:The following packages have unmet
> dependencies: apertium-eng-ita : Depends: apertium (>= 3.8.0) but 3.7.1-1
> is to be installedDepends: apertium-lex-tools (>=
> 0.3.0) but 0.2.7-1 is to be installedE: Unable to correct problems, you
> have held broken packages.*
>
> It happened only with debian 11, everything is ok with fresh Ubuntu.
> Please tell me what to do in Debian 11 case.
>
> Thanks
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Questionnaire: GSoC: Mentors’ Perspective

[Tino Didriksen]

>From our IRC channel this morning:

 I am an assistant professor from Beihang University. Our team is
doing a study about GSoC mentors, aiming to understand the motivations,
challenges, strategies, and gains of GSoC mentors. To this end, we designed
a questionnaire and sincerely invite GSoC mentors to participate in this
survey. Your feedback is very important for us.  Questionnaire link:
https://forms.gle/rgAWwmrvrCb5XdAq9  If you are interested in this study,
welcome to join our follow-up interview! Thank you very much!

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] A question about Apertium Kazakh and Tatar packages

[Tino Didriksen]

On Thu, 2 Sept 2021 at 09:53, Kevin Brubeck Unhammer 
wrote:

> However – there are people who want to use debug modes but would rather
> not want to compile a pair and manually
> `git pull && make && make test || revert-to-last-working-revision`.
>
> Would it make sense to install debug-modes to a debug-modes folder? Put
> stuff like -biltrans etc. in /usr/share/apertium/debug-modes, and then
> `apertium -l` only shows translation /modes while `apertium -L` shows
> both /modes and /debug-modes? (And `apertium kaz-rus-biltrans` works
> without any special switches because why not, while `apertium
> nonexistent` runs `apertium -l` and gives a hint to use `-L` to show the
> rest.)
>


That's a good idea, but some debug modes require files that are not
normally installed. We shouldn't clutter end-user installs with these files.

But we could install everything to 2 packages: A main package
apertium-zzz-xxx for end-users and another apertium-zzz-xxx-corpus (or
whatever bikeshed -name we come up with) with the extras. That would also
lead nicely into the spellers going into a separate package, as people who
just want spellers probably don't care about anything else.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] A question about Apertium Kazakh and Tatar packages

[Tino Didriksen]

G'day, and CC'ing the apertium-stuff mailing list,

Firstly, I recommend getting in the Apertium IRC channel for live support
and developer feedback. We're on irc.oftc.net #apertium (
https://wiki.apertium.org/wiki/Contact#IRC ).

As to your question, then those are debug modes. If you look in e.g.
https://github.com/apertium/apertium-tat-rus/blob/master/modes.xml then you
can see which modes are marked install="yes" - those are the only modes
that "make install" will install. Debug modes often depend on temporary
files that aren't installed either.

The installed modes are what the language/pair developers consider useful
for end-users. It is thus not really an issue or bug if a given debug mode
isn't installed - it's usually an informed choice. If anything, I would say
it's a bug that rus-kaz installs the debug modes that it does - and indeed,
such a bug is filed: https://github.com/apertium/apertium-kaz-rus/issues/1

The monolingual packages install many more modes, because they are used for
further development. So you can get morph from those. But biltrans is not
normal to want if you aren't a developer, and thus building from source.

But it's all what people are used to, so I'd expect the particular pair
developers are open for discussion and looking at new use-cases. Hence the
CC to the mailing list, as I am not a language pair developer.

-- Tino Didriksen



On Wed, 1 Sept 2021 at 18:58, Андрей Клочко  wrote:

> Dear Tino Didriksen,
> My name is Andrew and I'm a developer of web-platform Lingvodoc (
> http://lingvodoc.ispras.ru/). We have an idea to use some of Apertium
> linguistic packages in our system to implement the ability of performing
> automatical morphological analysis and translation to Russian (now I'm
> working on Kazakh and Tatar languages support). I use apertium-tat-rus and
> apertium-kaz-rus packages with modes "biltrans" and "morph" and they work
> well if these packages are built from Github sources, though I face with
> some problems while trying to use them from APT repository (
> https://apertium.projectjj.com/apt/install-nightly.sh):
> The output of
> $ echo "Сәлем!" | apertium kaz-rus
> is
> $ Error: can't stat file
> '/usr/share/apertium/apertium-kaz-rus/apertium-kaz-rus.kaz-rus.t4x'
> showing that an important file is absent in the apertium-kaz-rus DEB
> package.
> Modes "kaz-rus-morph", "kaz-rus-biltrans", "tat-rus-morph",
> "tat-rus-biltrans" don't exist among Apertium modes after apertium-tat,
> apertium-kaz, apertium-rus, apertium-kaz-rus, apertium-tat-rus packages
> installation, all available modes are listed below:
>   kaz_Arab-gener
>   kaz_Cyrl-gener
>   kaz-disam
>   kaz-gener
>   kaz-lexc
>   kaz-morph
>   kaz-rus
>   kaz-spell
>   kaz-tagger
>   kaz-tokenise
>   kaz-twol
>   rus-disam
>   rus-gener
>   rus-kaz-biltrans
>   rus-kaz-interchunk
>   rus-kaz
>   rus-kaz-postchunk-and-cleanup
>   rus-kaz-postchunk
>   rus-kaz-transfer
>   rus-morph
>   rus-tagger
>   tat-disam
>   tat-gener
>   tat-morph
>   tat-rus
>   tat-spell
>   tat-tagger
>   tat-tokenise
>   tat-twol
> Is it possible to fix this issue?
> Best regards,
> Andrew.
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] GSoC 2021 Code Collection

[Tino Didriksen]

Done.

And I think the URL alone will suffice, but some explanation of what the
work resulted in is of course better. We generally prefer reports on our
own wiki so that we can't lose them.

-- Tino Didriksen

On Sun, 22 Aug 2021, 07:02 Gourab Chakraborty IIIT Dharwad, <
19bcs...@iiitdwd.ac.in> wrote:

> Hi Tino,
>
> I have concluded my coding. Can you run the code collection once to record
> the final changes?
>
> Also what URL do I put in the work product URL? A Report (say a public
> Github Gist like Google suggests) with the link to
> https://apertium.projectjj.com/gsoc2021/gourab337.html or just this link
> directly?
>
> Thanks!
>
> On Tue, Aug 17, 2021, 8:55 PM Tino Didriksen 
> wrote:
>
>> As for previous years, I will run a code collection for GSoC changes.
>>
>> I just need to know who and what. Github usernames, the emails you use
>> for them, and what repos you want included.
>>
>> E.g., https://apertium.projectjj.com/gsoc2021/ I have already
>> added OverPoweredDev, mr-martian, and vivekvardhanadepu.
>>
>> -- Tino Didriksen
>>
>>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] GSoC 2021 Code Collection

[Tino Didriksen]

(duplicate, since original was rejected by mailing list due to too many CCs)

As for previous years, I will run a code collection for GSoC changes.

I just need to know who and what. Github usernames, the emails you use for
them, and what repos you want included.

E.g., https://apertium.projectjj.com/gsoc2021/ I have already added
OverPoweredDev, mr-martian, and vivekvardhanadepu.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] #apertium is now on OFTC

[Tino Didriksen]

Git repos are now all updated, and while I was at it I also fixed other
pending URL changes such as http -> https and apertium.com -> apertium.org

...and I've fixed the mishaps that an unguarded s/
apertium.com/apertium.org/g caused.

-- Tino Didriksen


On Thu, 27 May 2021 at 09:37, Tino Didriksen  wrote:

> G'day everyone,
>
> The PMC has made a decision that affects all Apertium members and
> contributors:
>
> As with many other projects, we cannot in good faith abide what's going on
> with Freenode, so Apertium's official IRC channel is now on
> https://oftc.net/ :
> - irc://irc.oftc.net/apertium
> - https://webchat.oftc.net/?channels=apertium
>
> We chose OFTC because it's an established network and has Debian's
> channels. We wish all the best for Libera.chat and hope they'll continue
> the best of the spirit that once inhabited Freenode. Many of us will be on
> both OFTC and Libera.
>
> The wiki and website has been updated to point people towards OFTC. Git
> repos will be updated soon.
>
> -- Tino Didriksen
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] #apertium is now on OFTC

[Tino Didriksen]

G'day everyone,

The PMC has made a decision that affects all Apertium members and
contributors:

As with many other projects, we cannot in good faith abide what's going on
with Freenode, so Apertium's official IRC channel is now on
https://oftc.net/ :
- irc://irc.oftc.net/apertium
- https://webchat.oftc.net/?channels=apertium

We chose OFTC because it's an established network and has Debian's
channels. We wish all the best for Libera.chat and hope they'll continue
the best of the spirit that once inhabited Freenode. Many of us will be on
both OFTC and Libera.

The wiki and website has been updated to point people towards OFTC. Git
repos will be updated soon.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Welcome Apertium GSoC Students

[Tino Didriksen]

(Mail originally also CC'ed (not BCC'ed) to all GSoC students, but
apertium-stuff rejected it)

Welcome to Apertium!

Some practical information for students (and mentors who may not have seen
it yet).

Firstly, why not BCC in these GDPR/privacy times? For copyright reasons, we
need to be able to tie your contribution to you in a legally sound manner,
and name just isn't enough. But name + email will do, which means your
email will wind up public anyway. As the main packager, I would also prefer
if you disable email protection for your Github accounts as that otherwise
mangles the emails in commit history, but I can work around it if you don't.

If you aren't already, please subscribe to the
https://lists.sourceforge.net/lists/listinfo/apertium-stuff mailing list.
This is where Apertium-wide information is distributed, such as breaking
changes to tools and environments, or your fellow students asking for
community input. If you enable digest mode, don't reply to digest mails -
but it's better to just not enable digest mode.

Personally, I would also prefer everyone also join us on
https://wiki.apertium.org/wiki/IRC but there is no requirement. But for
quick questions IRC is hard to beat. Especially for technical questions
where we prefer to help you in real time.

We have a Linux (Ubuntu 20.04) development server available for everyone to
use, accessible over SSH. This is suitable for heavy processing, or simply
easier collaboration where everyone can see the same files. See
https://www.mail-archive.com/apertium-stuff@lists.sourceforge.net/msg08533.html
for details.

And at the end of GSoC, I have a helper script that will gather up all your
contributions and make a zip file suitable for uploading to Google. Last
year looked like https://apertium.projectjj.com/gsoc2020/ . All I need to
know is your Github username and repositories to look at for each of you.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium Simpleton UI

[Tino Didriksen]

G'day,

That's because apertium-separable isn't built at all for Windows
yet. Native Windows has been rather on the back-foot because WSL works so
well.

You can use the WSL version via
https://docs.microsoft.com/en-us/windows/wsl/install-win10 followed by
https://wiki.apertium.org/wiki/Install_Apertium_core_using_packaging
although this is rather more advanced.

I'll see if I can find time for more Windows native builds.

-- Tino Didriksen


On Thu, 13 May 2021 at 01:21, Terje  wrote:

> Hey!
>
> I am having difficulties getting Apertium Simpleton UI to work. The
> program launches fine and the packages seem to have no issues with
> downloading (language package and Core Tools). But when I hit 'Run', this
> error pops up:
>
> 'lsx-proc' is not recognized as an internal or external command,
>
> operable program or batch file
>
>
> My knowledge of software is superficial.I don't understand any of the
> stuff you do. There was little help to find online. I thought it wouldn't
> hurt to send you an email. Is this an easy fix?
>
>
> Thanks either way!
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Ubuntu 16.04 (Xenial) going EOL

[Tino Didriksen]

I think Apertium's support model is a very good balance of bleeding edge
and long term support, but as the packager I am also the one who basically
decided it so I'll admit I am biased. Still, I think it's objectively good,
and I'll try to argue my point.

First of all, security. Distros and vendors drop support for old platforms
when they no longer make economic sense to backport security fixes for.
Ubuntu LTS has 5 years of security support, which I think is a completely
reasonable limit. That means customers have to upgrade every 5 years,
though ideally they would do so every 2 years when new LTSs come out.

But if someone continues to use a distro for which there are no longer
security updates? In this day and age of automated bot networks that
actively hunt for vulnerable systems and inject exploits into websites?
That's beyond my sympathy limit.

Secondly, Unicode. We are in the language technology business, and we need
to process Unicode and handle locales. New versions of Unicode and CLDR
some out regularly, with ICU being the official support library. So distros
with ancient Unicode/CLDR versions will potentially misbehave. Again, I
think 5 years of support is reasonable here.

Thirdly, language and tool features available in distros. As the packager,
I have pushed for everything to be buildable and testable with only
distro-provided packages - no 3rd party repos (pip, cargo, etc). Currently
only 2 packages don't build on older distros: apertium-apy and lexd. APy
because distros' versions of Python 3 simply got too old, and lexd because
of a g++ bug.

This is an area where I actively hold back Apertium code, to some
consternation of developers including myself. Us developers want to use
latest language features because they are better and cleaner, but the
packager in me says we must support oldest Ubuntu LTS which means we have
to hold back on writing bleeding edge code.

The set of supported distros at any given time comes out to roughly 5 years
of support. If a distro is at most 5 years old (not counting point
releases), it will almost certainly work. As both packager and developer, I
think this is a good balance. And given how both end-users and developers
grumble equally about it (it's too new AND too old at the same time!), I
feel confident we've objectively found a good balance.

Fourthly, Docker, et al. Most of the above quickly becoming a moot point,
because anyone can run any version of anything they want in various kinds
of containers / snaps / appimage / etc. That's not to say we will drop the
5 year support, but it's something to think about.

-- Tino Didriksen


On Sun, 9 May 2021 at 23:05, Bernard Chardonneau  wrote:

> > Date: Wed, 21 Apr 2021 13:38:56 +0200
> > From: Tino Didriksen 
> > To: "[apertium-stuff]" 
> > Reply-To: apertium-stuff@lists.sourceforge.net
> > Subject: [Apertium-stuff] Ubuntu 16.04 (Xenial) going EOL
> > Pièce(s) jointes(s) probable(s)>
> > Reminder that Ubuntu 16.04 Xenial will reach end-of-life in a few days.
> If
> > you're still on Xenial, upgrade.
> >
> > Similarly, Debian 9 Stretch is becoming long in the tooth.
> >
> > -- Tino Didriksen
> >
>
> Well, I was waiting a message of that kind to do a suggestion.
>
> I am of a generation who find it normal to use a camera to take pictures,
> a phone to make phone calls, a watch to get the exact time, and a hammer
> to hit something.
>
> But a computer stays a multi-use device. If somebody uses a computer ONLY
> to work with Apertium, there should not be a problem changing distribution
> every 6 months. In fact, even then, it is not entirely true as a text
> editor
> is needed, and the behavior of the favorite text editor (especially if it
> is graphical) may change from one distribution to the next one.
>
> When something exists and works fine, it should never disappear to be
> replaced by something worse.
> But for things we can buy as for software, including free software, it
> sometimes happens.
>
> When I discovered Apertium, I had Mandriva 2009 installed on my computer.
> Apertium didn't work with it. So, I also installed Debian 6. On Mandriva
> 2009, there were 2 things that I liked and never found again: a gadget
> displaying a color world map with the areas where it's daylight called
> kworldclock and a file explorer on which, when clicking on an picture file,
> the picture was displayed into a tab, instead of opening a new window which
> was often too small from the first photo and quickly always too small when
> using arrows to see other ones, some portrait oriented, others landscape
> oriented.
> So, even if Debian 6 has extra possibilities, I still used Mandriva 2009
> for a few more years for image processing with Gimp.
>
> A few years later, I needed Debian 7 to make Apertium work. I did a copy
> of Debia

Re: [Apertium-stuff] Fwd: Apertium simpleton not working on mac

[Tino Didriksen]

G'day Olav,

macOS 10.12 is not supported. The oldest macOS we currently support is
10.13 (High Sierra), and only because we haven't run into any issues with
10.13.

Rule of thumb is that most recent 3 major releases of macOS is supported,
which currently means 11 (Big Sur), 10.15 (Catalina), and 10.14 (Mojave).
Unfortunately Apple doesn't officially state any of this, but they very
strongly imply it via e.g.
https://developer.apple.com/documentation/macos-release-notes only listing
10.14 and newer.

-- Tino Didriksen


On Mon, 3 May 2021 at 14:46, Jonathan Washington <
jonathan.n.washing...@gmail.com> wrote:

> Hi Olav,
>
> Perhaps someone on the apertium-stuff mailing list can help.  I'm
> forwarding your message there.
>
> --
> Jonathan
>
> -- Forwarded message --
> From: olav lund solheim 
> To: apertium-cont...@lists.sourceforge.net
> Cc:
> Bcc:
> Date: Mon, 3 May 2021 12:33:36 +0200
> Subject: Apertium simpleton not working on mac
> Hi,
>
> I'm currently trying to run Apertium simpleton on my mac. I've installed
> all required tools and specific packages for the languages I'm trying to
> translate. I've tried a wide range of different languages and the same
> error message shows up regardless. I'm currently running macOS Sierra
> version 10.12.6 on my 2015 MacBook air.
>
> Error message:
> dyld: lazy symbol binding failed: Symbol not found: chkstk_darwin
>
>   Referenced from: /Users/olavsolheim/Library/Application Support/Tino
> Didriksen Consult/Apertium
> Simpleton/apertium-all-dev/bin/../lib/libpcre.1.dylib
>
>   Expected in: /usr/lib/libSystem.B.dylib
>
>
>
> This message shows up five times.
>
> Hope you can help me with this issue as soon as possible.
>
> Regards Olav Solheim
> ___
> 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] Ubuntu 16.04 (Xenial) going EOL

[Tino Didriksen]

Reminder that Ubuntu 16.04 Xenial will reach end-of-life in a few days. If
you're still on Xenial, upgrade.

Similarly, Debian 9 Stretch is becoming long in the tooth.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] std::exception in es-ca

[Tino Didriksen]

es-ca 1.2.1 is dead and gone, replaced with
https://github.com/apertium/apertium-spa-cat a long time ago. Guess I'll
have to clean up SourceForge's files to avoid such mistakes.

Depending on your OS/distro you can get builds of apertium-spa-cat from our
nightly repos https://wiki.apertium.org/wiki/Installation , or just build
it from a git clone if you prefer.

-- Tino Didriksen


On Thu, 15 Apr 2021 at 11:07, Helena Egea Piñeiro 
wrote:

> Hi!
>
> I'm trying to manually check the pipeline of apertium translation in es-ca
> 1.2.1 and I come out with this std::exception trying to generate the final
> translation.
>
>
> echo "tengo trabajo" |  /usr/local/bin/lt-proc
> /usr/local/share/apertium/apertium-es-ca/es-ca.automorf.bin
> |/usr/local/bin/apertium-tagger -g $2
> /usr/local/share/apertium/apertium-es-ca/es-ca.prob
> |/usr/local/bin/apertium-pretransfer|/usr/local/bin/apertium-transfer
> /usr/local/share/apertium/apertium-es-ca/es-ca.t1x
>  /usr/local/share/apertium/apertium-es-ca/es-ca.t1x.bin
>  /usr/local/share/apertium/apertium-es-ca/es-ca.autobil.bin
> |/usr/local/bin/lt-proc $1
> /usr/local/share/apertium/apertium-es-ca/es-ca.autogen.bin
> |/usr/local/bin/lt-proc -p
> /usr/local/share/apertium/apertium-es-ca/es-ca.autopgen.bin
>
> >> std::exception
>
> echo "tengo trabajo"  /usr/local/bin/lt-proc
> /usr/local/share/apertium/apertium-es-ca/es-ca.automorf.bin
> |/usr/local/bin/apertium-tagger -g $2
> /usr/local/share/apertium/apertium-es-ca/es-ca.prob
> |/usr/local/bin/apertium-pretransfer|/usr/local/bin/apertium-transfer
> /usr/local/share/apertium/apertium-es-ca/es-ca.t1x
>  /usr/local/share/apertium/apertium-es-ca/es-ca.t1x.bin
>  /usr/local/share/apertium/apertium-es-ca/es-ca.autobil.bin
> >> ^tenir$ ^treball$
>
>
> Also, I found some warnings when compiling in files t1x saying rule 9
> blocks rule 12 and other rules.. I don't know if these two thing could be
> related.
>
> When I translate directly with apertium es-ca everything goes fine. And
> that pipeline I copied it from es-ca.mode. So I don't know what is
> executing apertium that is actually working but not when I do it.
>
>
> Thanks!
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] GSoC Students & Mentors, check proposals

[Tino Didriksen]

GSoC students have 29 hours to get their proposals submitted. Make sure you
have a Final proposal in the system several hours before the deadline, even
if it's not perfect.

GSoC mentors, if you don't already have access to
https://summerofcode.withgoogle.com/ and want it, speak up. Those of you
who have access, check if there are any proposals that sound promising but
need a bit more from the student.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Requests for Suggestions

[Tino Didriksen]

I would say the entire functionality that you propose could be implemented
and tested in ~3 weeks, also in a cross-browser manner. Mouseover
translation is trivial. Whole document translation is not trivial, but also
not that hard. But that's speaking as someone who has implemented this
exact DOM manipulation in multiple languages.

Still, I think this is a worthwhile project.

Since I am quite sure you'll be done before time, I propose a stretch goal
of inline gisting, which is like mouseover translation but with context.
It's essentially a combination of full document translation, but retaining
the original language text and giving the translation on hover/touch. This
is not trivial, as it would require alignment of input with output - which
is something last year's GSoC made possible, but nobody has used yet.

-- Tino Didriksen


On Fri, 9 Apr 2021 at 17:50, Omkar Prabhune 
wrote:

> Hello Everyone,
>
> I'm Omkar Prabhune, a sophomore in CompSci and I have submitted a
> proposal for GSoC 2021 on the Project Idea: *Reworked Apertium Browser
> Plugin*
>
> I have prepared a draft here and have received some great ideas on it but
> I'd always appreciate more suggestions. I'm also usually active on the IRC
> chat with the username 
>
> Link to the Document:
> https://docs.google.com/document/d/1HtvZH7Vg08n0XmedMEVzXceKbu0QPhvv92xSzqDI25E/edit?usp=sharing
>
> Thanks,
> Omkar Prabhune
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Bitrotted releases redux

[Tino Didriksen]

This is less critical than I thought. I just re-tested all existing
packages, and they run. So I can update the main site with existing
packages for the ones that can't currently build.

I don't know what changed, because I am quite sure they didn't previously
run. But oh well, this is good news.

-- Tino Didriksen


On Mon, 29 Mar 2021 at 21:58, Tino Didriksen  wrote:

> https://github.com/apertium/organisation/issues/23 is still open, and
> these languages/pairs need someone to sign off on current state or make a
> formal new release.
>
> * https://github.com/apertium/apertium-cym
> * https://github.com/apertium/apertium-hin
> * https://github.com/giellalt/lang-sme
> * https://github.com/apertium/apertium-es-gl and must depend on a
> specific release of https://github.com/apertium/apertium-spa
> * https://github.com/apertium/apertium-cym-eng and must depend on a
> specific release of https://github.com/apertium/apertium-cym and
> https://github.com/apertium/apertium-eng
> * https://github.com/apertium/apertium-eng-spa
> * https://github.com/apertium/apertium-sme-nob
> * https://github.com/apertium/apertium-spa-ita and must depend on a
> specific release of https://github.com/apertium/apertium-spa and
> https://github.com/apertium/apertium-ita
> * https://github.com/apertium/apertium-urd-hin and must depend on a
> specific release of https://github.com/apertium/apertium-urd and
> https://github.com/apertium/apertium-hin
>
> The existing releases cannot build and/or run with current Apertium tools.
> These are holding back Apertium 3.7 from the main site. The alternative is
> that I remove these languages/pairs from the main site.
>
> -- Tino Didriksen
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Bitrotted releases redux

[Tino Didriksen]

On Tue, 30 Mar 2021 at 18:58, Xavi Ivars  wrote:

> I was looking into this, and I'm not sure why apertium-es-gl needs to
> depend on a specific release of spa. As far as I see, this package hasn't
> still moved to use monolingual packages, and has its own Spanish
> dictionaries, tagger, etc. Am I missing something?
>

I just react to
https://github.com/apertium/apertium-es-gl/blob/master/configure.ac#L35

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Good First Issues

[Tino Didriksen]

I've gone through the entire 30 pages of open issues and tagged the ones I
figure are Good First Issue as such. And closed and commented on a bunch of
stuff in the process.

Also added links to these from https://github.com/apertium/organisation and
https://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Lexical Selection

[Tino Didriksen]

Quick note: You're talking about Apertium version 3.2 and 3.3. Those
versions are from 2010 and 2014. We're at Apertium version 3.7.1 these
days, and we only support development with latest versions of all tools.

Version 3.3 is so old it's not even in the oldest supported Ubuntu or
Debian.

If you need help installing newer versions (please use our binaries), ask
on IRC (Freenode #apertium).

-- Tino Didriksen


On Tue, 23 Mar 2021 at 11:49, Helena Egea Piñeiro 
wrote:

> Hola!
>
> Quería preguntar sobre la diferencia de la selección léxica de apertium
> 3.2 a 3.3. En un hilo anterior pedía como sería posible obtener varias
> opciones de traducción como "Tengo mucho trabajo" > "Tinc molta
> feina/treball". Para esto seguí recomendaciones de interrumpir el pipelline
> ya que para algunos ejemplos en el apertium que instalé del paquete spa-cat
> la desambiguación no se hacía mediante entradas en los diccionarios del
> tipo SRL o SLR, sino que había entradas independientes. Si esto no es así
> no consigo ninguna opción en el flujo de:
>
>  lt-proc -w '/usr/share/apertium/apertium-spa-cat/spa-cat.automorf.bin' |
> cg-proc -w '/usr/share/apertium/apertium-spa-cat/spa-cat.rlx.bin' |
> apertium-tagger -g $2 '/usr/share/apertium/apertium-spa-cat/spa-cat.prob' |
> apertium-pretransfer| lt-proc -b
> '/usr/share/apertium/apertium-spa-cat/spa-cat.autobil.bin'
>
> No sé si en apertium 3.2 es posible tener entradas sin desambiguación y
> que se resuelvan despues. O si hay alguna manera de con las herramientas de
> apertium se muestre la opción sin elegir previa al procesar las entradas de
> tipo SRL o SLR. O si puedo modificar los diccionarios y dejar entradas
> separadas sin que afecte a la selección posterior
>
> Gracias!
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] (no subject)

[Tino Didriksen]

First off, don't reply to an unrelated message. That breaks threading.

Everything you need to know about us in GSoC is available via
https://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code and links on
that page.

IRC is the best place for most discussion.

-- Tino Didriksen


On Thu, 25 Mar 2021 at 06:54, 17_158_Manish Kumar Paul <
manishkumarpa...@gmail.com> wrote:

> Hello, I would like to work on Natural Language Processing under Google
> Summer Of Code 2021. What are the available subdomains?
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] About Morphological analyser

[Tino Didriksen]

G'day...

You can start by seeing how useful https://github.com/apertium/apertium-jpn
is.

The helper apertium-get can fetch and build it from source for you, and you
get apertium-get and the other needed core tools from our binary packages,
https://wiki.apertium.org/wiki/Installation

If you need more direct help, come on IRC:
https://wiki.apertium.org/wiki/Contact

-- Tino Didriksen


On Mon, 22 Mar 2021 at 14:12, <10.atsuh...@gmail.com> wrote:

>
> Hi, I'm Atsuhiro.
> I would like to participate in GSoC and I'm interested in "Develop a
> morphological analyser" in the idealist. I'm thinking of making a
> morphological analyser of Japanese because I'm a Japanese-speaker.
>
> Could you tell me more about this project?  I want to learn how I can work
> with this project. I read the official documentation.
>
> Thank you.
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Core tools for M1 Mac

[Tino Didriksen]

All the core tools are now also available for M1 Mac (arm64). The script
https://apertium.projectjj.com/osx/install-nightly.sh is updated to fetch
the correct arch. Also left a symlink to the x86_64 bundle in the old place
because it'll still work thanks to Rosetta.

Speaking of, the performance of native vs. emulated is that native arm64 is
25% faster. Building giella-kal on M1 with x86_64 tools takes 775 real (889
user, 15.5 sys) seconds, but with arm64 tools it takes 598 real (664 user,
30 sys) seconds.

And 16 GB RAM is definitely needed. It would've swapped with less, and I
had nothing else running. With the 8 GB models I can't imagine how much it
would thrash if one had some IDEs, browsers, etc, open while building a
language.

The only code adjustment needed was in CG-3, and wasn't even
arch-portability related - was just a C++20 quirk.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Fwd: GSoC org apps open Jan 29-Feb 19

[Tino Didriksen]

Are we doing GSoC this year with half-time projects? If so, we need to
overhaul https://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code

-- Tino Didriksen


On Fri, 15 Jan 2021 at 08:34, 'sttaylor' via Google Summer of Code Mentors
List  wrote:

> Happy new year everyone!
>
> Just a quick reminder that if your org would like to apply for the 2021
> GSoC program please start thinking about the ~175 hr projects you would
> like students to work on and also reach out to your community members to
> ask if they would like to be mentors for the program. Having a thorough and
> well thought out list of Project Ideas
> <https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list>
> is the most important part of your application.
>
> We realize many of you have project ideas from a previous GSoC Ideas List
> based on a 350 hour size project, please look at ways to either break the
> project into smaller chunks or consider completely new project ideas that
> will be ~175 hours for students to work on over the summer.
>
> You can check out the 2021 GSoC Org Application Questions
> <https://docs.google.com/document/d/1REKWPUUurpDVb7HWlxXjqC2BKIPtJLGEd1Rp9x3Jzeo/edit?usp=sharing>
> if you’d like to start preparing your responses in advance so you can copy
> over your answers once the org applications open Jan 29 - Feb 19 at
> g.co/gsoc - there are a few new questions this year.
>
> Please encourage other open source orgs to apply -- if you know of other
> open source projects that may be interested in applying to GSoC as a first
> time org please remind them to check out the available resources below and
> have them put your org (or you) down as a reference.
>
> Open source projects can apply <https://summerofcode.withgoogle.com/> to
> be mentoring organizations from January 29th - February 19th at 1900 UTC.
>
> *Resources:*
>
> Mentor Guide <https://google.github.io/gsocguides/mentor/>
>
> Timeline <https://developers.google.com/open-source/gsoc/timeline>
>
> FAQs <https://developers.google.com/open-source/gsoc/faq>
>
> Roles and Responsibilities
> <https://developers.google.com/open-source/gsoc/help/responsibilities>
>
> Marketing Materials
> <https://developers.google.com/open-source/gsoc/resources/marketing>
> (slide deck, flyers)
>
> Videos <https://developers.google.com/open-source/gsoc/videos>
>
> If you have any questions please email me at gsoc-supp...@google.com
>
> Best,
>
> Stephanie Taylor
>
> GSoC Program Lead
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] The French-Arpitan translator is ready to be packed

[Tino Didriksen]

apertium-fra, apertium-frp, and apertium-fra-frp are now finally also
tagged on Github and in the release repo. It's been on apertium.org for a
while, but was otherwise held up by the core tool packages.

And for Debian:
- https://salsa.debian.org/science-team/apertium-fra-frp v1.0.0, bundling
apertium-fra v1.10.0 and apertium-frp v1.0.0. Requires latest cg3,
lttoolbox, apertium, -lex-tools, and -separable.

-- Tino Didriksen


On Tue, 1 Sept 2020 at 16:29, Hèctor Alòs i Font 
wrote:

> As a result of this year's GSoC, I've prepared a French-Arpitan
> bidirectional translator. In principle, it is ready to be packed. It uses
> apertium-separator and this summer's improvements of apertium-lex-tools
> done by Daniel Swanson.
>
> A bit of a detailed explanation of the pair can be found here:
> https://wiki.apertium.org/wiki/Hectoralos/GSOC_2020_rapport_final (in
> French). The WER from French to Arpitan is 5.7% and from Arpitan to French
> is 15.5% (this final results are consistent with the first results I got in
> a first test at the end of July). This unexpectedly low WER in the
> French-Arpitan side is the result of a great involvement of two language
> specialists, Dominique Stich and Alan Favro, with whom I've been
> continuously in touch throughout the whole project. I would also like to
> thank Tino Didriksen, Daniel Swanson, Marc Riera and my supervisors Xavi
> Ivars and Gianfranco Fronteddu for their support during the development.
>
> Hèctor
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] English to Hindi/Bengali and vice versa

[Tino Didriksen]

First off, read
https://wiki.apertium.org/wiki/Frequently_Asked_Questions#The_Blurb

The wiki has several other pages full of documentation on how to
contribute. As for English <-> Hindi/Bengali, we have these repos that you
can build on:
- https://github.com/apertium/apertium-hin
- https://github.com/apertium/apertium-ben
- https://github.com/apertium/apertium-eng
- https://github.com/apertium/apertium-eng-hin
- https://github.com/apertium/apertium-bn-en

For further help, I recommend IRC. We are on Freenode in channel #apertium

-- Tino Didriksen


On Sun, 13 Dec 2020 at 09:10, Atreya Majumdar  wrote:

> Hi!
> I was going through the list of available language pair packages in the
> Apertium Language Pair wiki, and I noticed that there was a lack of Indian
> languages there. If there are no current projects, is it possible for me to
> start contributing by adding English-Bengali (Bidirectional) and
> English-Hindi(Bidirectional) support?
> How do I get started in doing so? And what is the tech stack/ NLP model
> architecture that is generally used at Apertium?
>
> Yours Sincerely,
> Atreya Majumdar.
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Releases for everything

[Tino Didriksen]

The following are now in the release repos, Github tags, and tarballs:
- https://github.com/TinoDidriksen/Transfuse v0.5.6 (new package)
- https://github.com/TinoDidriksen/cg3 v1.3.2
- https://github.com/hfst/hfst v3.15.3 (new library version)
- https://github.com/apertium/lttoolbox v3.5.3
- https://github.com/apertium/apertium v3.7.0 (new library version)
- https://github.com/apertium/apertium-get v1.0.0 (split from apertium)
- https://github.com/apertium/apertium-lex-tools v0.2.6 (binary break since
last release)
- https://github.com/apertium/apertium-recursive v1.0.0
- https://github.com/apertium/apertium-separable v0.3.6
- https://github.com/apertium/apertium-anaphora v1.0.1

And pushed to Debian repos:
- https://salsa.debian.org/science-team/transfuse (new)
- https://salsa.debian.org/science-team/cg3
- https://salsa.debian.org/science-team/hfst (ABI 52 -> 53)
- https://salsa.debian.org/science-team/lttoolbox
- https://salsa.debian.org/science-team/apertium (ABI 3.6 -> 3.7)
- https://salsa.debian.org/science-team/apertium-get (new)
- https://salsa.debian.org/science-team/apertium-lex-tools
- https://salsa.debian.org/science-team/apertium-recursive
- https://salsa.debian.org/science-team/apertium-separable
- https://salsa.debian.org/science-team/apertium-anaphora

Still remaining ToDo: All language pairs and APy.

-- Tino Didriksen


On Mon, 21 Sept 2020 at 18:44, Tino Didriksen 
wrote:

> Given that Apertium has undergone big changes and a binary compat break
> since last formal release, just about everything is getting re-released and
> re-packaged.
>
> So if any of you have any changes that will break binary compat, and that
> you can commit this week, now would be a good time to make those.
>
> -- Tino Didriksen
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Enabled Github Discussions

[Tino Didriksen]

I've enabled https://github.com/apertium/organisation/discussions - but not
on any other repo.

And I've asked Github to please also make this new feature org-wide,
because it doesn't really make sense on a per-repo basis for us.

Maybe it'll be used as little as the Sourceforge forums, maybe not...we can
always kill it if it proves pointless.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

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

[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] Releases for everything

[Tino Didriksen]

The world conspired against me being productive in any way, so everything
stalled.

But since then, https://github.com/apertium/apertium/issues/108 has come
up, which feels like a larger underlying issue. I hope
https://github.com/apertium/lttoolbox/pull/105 will fix that - will test
that today.

-- Tino Didriksen


On Tue, 20 Oct 2020 at 23:51, Xavi Ivars  wrote:

> Hi!
>
> Any updates on new releases?
>
> I was looking at the current released versions of "apertium", and it seems
> that it's 3.6.1, which was released last October (2019).
>
> Tag 3.6.3 (released July 1st 2020) hasn't been released yet, and nothing
> that includes all the amazing work done this summer (including new
> blank/format handling, posttransfer, etc) has been released either (it
> hasn't even been tagged in Github).
>
> Are there any blockers for these releases to happen?
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium on Colab?

[Tino Didriksen]

https://colab.research.google.com/notebooks/snippets/importing_libraries.ipynb
- it's possible to install the Python modules on Colab and clone arbitrary
Github Python repos, but does that help? Are the Python modules usable to
edit and compile languages/pairs?

It doesn't seem like something Colab was meant for, and searches finds
various less-than-elegant workarounds with Google Drive.

-- Tino Didriksen


On Fri, 25 Sep 2020 at 15:21, Francis Tyers  wrote:

> Hi all,
>
> I just got this message from Vincent Vandeghinste:
>
> "Hi Fran,
>
> Hope you are alright.
>
> For a course I am teaching, I would like to introduce some RBMT through
> Apertium. Is there by any chance a way to setup Apertium in Google
> Colab, so I can use that environment, and the students won't have to
> bother with getting used to the virtual linux environment?
>
> thanks,
> v."
>
>
> Does anyone know if this is possible?
>
> Fran
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] let's move the mailing lists to sourcehut

[Tino Didriksen]

On Wed, 23 Sep 2020 at 16:27, Francis Tyers  wrote:

> El 2020-09-23 15:03, Jonathan Washington escribió:
> > One other question:
> >
> > Will it be possible to move existing apertium-stuff (and PMC, etc)
> > archives to the new location?  Or would we be starting over with those
> > archives?
> >
>
> I think the PMC list is a distribution list, not a mailing list, so we
> don't have archives.
>

I've thought about that before, when writing the Bylaws proposal. Several
of us have years worth of emails with to: or cc: the PMC that we can easily
export to an mbox and import to mailman.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Releases for everything

[Tino Didriksen]

Given that Apertium has undergone big changes and a binary compat break
since last formal release, just about everything is getting re-released and
re-packaged.

So if any of you have any changes that will break binary compat, and that
you can commit this week, now would be a good time to make those.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] let's move the mailing lists to sourcehut

[Tino Didriksen]

On Mon, 21 Sep 2020 at 10:10, Kevin Brubeck Unhammer 
wrote:

> Considering the trouble people have just setting up their own e-mail
> server without getting constantly spam-listed by other people's Gmail
> accounts – and the fact that the mailing lists are supposed to be public
> anyway – it'd be nice to have a third party host our mailing lists.
>

We have at least 2 private mailing lists: PMC and GSoC mentors. The PMC
list we absolutely should run ourselves on our own server(s) for
confidentiality reasons, and better so that future PMC members can actually
refer to the archives. GSoC lists are per year, but no less confidential.

So if we're going to run mailman or whatever for those, we might as well
run it for all of them - with appropriate public mirrors for the relevant
lists. We could even run the Sourcehut software, if it's that good.

But yes, it is annoying to run your own MTA. There's unfortunately a lot of
email providers that blacklists IPs for rather annoying and bad reasons.
But the wiki already sends mail from the apertium.org server, so we know
that works.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] let's move the mailing lists to sourcehut

[Tino Didriksen]

On Mon, 21 Sep 2020 at 12:13, Flammie A Pirinen  wrote:

> > Discourse looks nice.
> >
>
> Is this discourse.mozilla.org? I really dislike that, last I was forced
> to move bug report from github issues to discourse and it manaaged to be
> worse than github issue for discussing.
>

Mozilla runs a Discourse service, but the underlying software is
https://github.com/discourse/discourse - it can function as a mailing list
manager.

I strongly dislike the Discourse look'n'feel. The underlying software may
be good, but every time I run across a community that uses Discourse, I
dread interacting with it.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] let's move the mailing lists to sourcehut

[Tino Didriksen]

We could host our own lists and other groupware. No reason to outsource it,
and it would give 100% control.

-- Tino Didriksen


On Sun, 20 Sep 2020 at 19:04, Francis Tyers  wrote:

> Sourcehut is a free/open-source "forge" type thing run by Drew DeVault.
> They have
> mailing lists.
>
> Our current mailing lists are with SourceForge and all of the terrible
> stuff that
> goes with that.
>
> Here is a link:
>
> https://lists.sr.ht/
>
> What do people think?
>
> Fran
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] We now have markup handling and reordering in Apertium!

[Tino Didriksen]

I have adjusted Transfuse with how spaces are treated for Apertium, and
implemented adding temporary spaces around  and . Changes are
deployed on beta.

I repeat my plea that all symbols should have an analysis. It breaks markup
that things like - and : are not tokens.

-- Tino Didriksen


On Wed, 2 Sep 2020 at 13:23, Tino Didriksen  wrote:

> That's not something the pipe ever sees - you can't fix it on your end.
> It's something I have to adjust in Transfuse.
>
> https://github.com/TinoDidriksen/Transfuse/blob/master/src/dom.cpp#L604
> and L629 expands inline tags to encompass surrounding plain text, because
> it is unfortunately common for formatting to be partially on a word while
> you really want the whole word translated as a unit.
>
> However, for HTML I should add spaces around  and  so that they
> can't gobble up their surroundings. Tracked as
> https://github.com/TinoDidriksen/Transfuse/issues/7
>
> -- Tino Didriksen
>
>
> On Wed, 2 Sep 2020 at 12:58, Hèctor Alòs i Font 
> wrote:
>
>> I'm taking a look on how this list of names on Wikipedia:
>> https://frp.wikipedia.org/wiki/Lista_des_comtos_et_ducs_de_Savou%C3%A8
>> and how it is translated in beta.apertium:
>> https://beta.apertium.org/index.fra.html?dir=frp-fra=https%3A%2F%2Ffrp.wikipedia.org%2Fwiki%2FLista_des_comtos_et_ducs_de_Savou%25C3%25A8#webpageTranslation
>>
>> There still are quite a few problems with HTML-tags if we look that the
>> whole Iér is becoming a superscript, and also with italics. The space after
>> the hyphen is an already known problem.
>>
>> By the way, I wonder whether it is possible to match in our dictionaries
>> Iér. I have Iér in the dictionary, but when the ending ér stays
>> as a superscript, as usually done in the texts, it is not matched. Should I
>> add Iér to the dictionary?
>>
>> Hèctor
>>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] We now have markup handling and reordering in Apertium!

[Tino Didriksen]

That's not something the pipe ever sees - you can't fix it on your end.
It's something I have to adjust in Transfuse.

https://github.com/TinoDidriksen/Transfuse/blob/master/src/dom.cpp#L604 and
L629 expands inline tags to encompass surrounding plain text, because it is
unfortunately common for formatting to be partially on a word while you
really want the whole word translated as a unit.

However, for HTML I should add spaces around  and  so that they
can't gobble up their surroundings. Tracked as
https://github.com/TinoDidriksen/Transfuse/issues/7

-- Tino Didriksen


On Wed, 2 Sep 2020 at 12:58, Hèctor Alòs i Font 
wrote:

> I'm taking a look on how this list of names on Wikipedia:
> https://frp.wikipedia.org/wiki/Lista_des_comtos_et_ducs_de_Savou%C3%A8
> and how it is translated in beta.apertium:
> https://beta.apertium.org/index.fra.html?dir=frp-fra=https%3A%2F%2Ffrp.wikipedia.org%2Fwiki%2FLista_des_comtos_et_ducs_de_Savou%25C3%25A8#webpageTranslation
>
> There still are quite a few problems with HTML-tags if we look that the
> whole Iér is becoming a superscript, and also with italics. The space after
> the hyphen is an already known problem.
>
> By the way, I wonder whether it is possible to match in our dictionaries
> Iér. I have Iér in the dictionary, but when the ending ér stays
> as a superscript, as usually done in the texts, it is not matched. Should I
> add Iér to the dictionary?
>
> Hèctor
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Update about superblanks in transfer

[Tino Didriksen]

Why is - a blank in the first place? If it's needed in contexts, it should
be fully analyzed as a token.

This goes for all Apertium languages and pairs. I don't understand why
punctuation generally isn't analyzed. I assume it's just historic.

-- Tino Didriksen


On Sun, 30 Aug 2020 at 08:27, Hèctor Alòs i Font 
wrote:

> Unfortunately, I found a lot of problems cased by superblanks, especially
> with the handling of hyphens. See a couple of differences in translations
> of my French test corpus into Arpitan before and after the update:
>
> < 00607. Tandis que les Tétes Broulâyes sont en *permission sur *Espritos
> Marcos, tomba amouerox de Yvonne, una Franco-Japonêsa.
> ---
> > 00607. Tandis que les Tétes Broulâyes sont en *permission sur *Espritos
> Marcos, tomba amouerox de Yvonne, una- Franco Japonêsa.
>
> < 00748. On povêt per ègzemplo parlar, sot Charlo-lo-Pelâ, de la
> "*foresta" des pêrches de la Sêna.
> ---
> > 00748. On povêt per ègzemplo parlar, sot Charlo-lo- Pelâ, de la
> "*foresta" des pêrches de la Sêna.
>
> Hèctor
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] GSoC 2020 Code Collections - need info

[Tino Didriksen]

First run is now online at https://apertium.projectjj.com/gsoc2020/

Collected for elmurod1202, hectoralos, khannatanmai, priyankmodiPM.
Collection period is 2020-05-04 through 2020-08-31.

-- Tino Didriksen


On Sat, 22 Aug 2020 at 14:21, Tino Didriksen  wrote:

> As for previous years, I will run a code collection for GSoC changes.
>
> I just need to know who and what. Usernames and repos.
>
> -- Tino Didriksen
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] GSoC 2020 Code Collections - need info

[Tino Didriksen]

As for previous years, I will run a code collection for GSoC changes.

I just need to know who and what. Usernames and repos.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Testing markup reordering in Apertium

[Tino Didriksen]

Transfuse now understands PPTX, so these formats are supported: text, html,
html-fragment, odt, odp, docx, pptx

There is now a helper tf-apertium (replaces tf-html-fragment) which will
auto-detect input format, run akin to:
cat file.docx | tf-apertium /usr/share/apertium/modes/eng-spa.mode >
out.docx

Or the full form:
tf-extract file.docx | bash <(tf-mangle-mode
/usr/share/apertium/modes/eng-spa.mode) -g | tf-inject out.docx

The difference between HTML and a HTML fragment is that HTML has the whole
 structure, while a fragment is some
piece of HTML that would be valid to put inside .

-- Tino Didriksen


On Thu, 23 Jul 2020 at 10:26, Tino Didriksen  wrote:

> Transfuse ( https://github.com/TinoDidriksen/transfuse ) is now in the
> nightly repos for Debian, Ubuntu, and macOS.
>
> It is by no means done, but it's usable for HTML documents and HTML
> fragments, which is enough to test the various pipes.
>
> Everything Tanmai has worked on is also merged and in the nightly builds,
> so it should all be testable.
>
> -- Tino Didriksen
>
>
> On Wed, 22 Jul 2020 at 15:57, Tanmai Khanna 
> wrote:
>
>> Hey Xavi,
>> Postgeneration has been modified to deal with wordbound blanks. It deals
>> with wordbound blanks in one-one, one-many, many-one and many-many rules in
>> postgeneration. (Pull Request
>> <https://github.com/apertium/lttoolbox/pull/102>)
>>
>> Regards,
>> *तन्मय खन्ना *
>> *Tanmai Khanna*
>>
>>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Testing markup reordering in Apertium

[Tino Didriksen]

Transfuse ( https://github.com/TinoDidriksen/transfuse ) is now in the
nightly repos for Debian, Ubuntu, and macOS.

It is by no means done, but it's usable for HTML documents and HTML
fragments, which is enough to test the various pipes.

Everything Tanmai has worked on is also merged and in the nightly builds,
so it should all be testable.

-- Tino Didriksen


On Wed, 22 Jul 2020 at 15:57, Tanmai Khanna  wrote:

> Hey Xavi,
> Postgeneration has been modified to deal with wordbound blanks. It deals
> with wordbound blanks in one-one, one-many, many-one and many-many rules in
> postgeneration. (Pull Request
> <https://github.com/apertium/lttoolbox/pull/102>)
>
> Regards,
> *तन्मय खन्ना *
> *Tanmai Khanna*
>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium syntax highlighting

[Tino Didriksen]

Done, https://github.com/apertium/apertium-syntax-highlight - and added
every contributor to the repo.

-- Tino Didriksen



On Fri, 3 Jul 2020 at 21:39, mansur <6688...@gmail.com> wrote:

> Hi!
>
> Several months ago we started merging three different repositories with
> vim plugins for Apertium related formats. Initially we placed them in my
> account here:
> https://github.com/mansayk/apertium-syntax-highlight
>
> The idea was to move them to the Apertium account after some testing. So,
> it passed quite a lot of time, most of the problems were fixed and it seems
> quite good now. If you don't mind, let's finally move it? :)
>
> We also need to improve the description there (readme), but right now I'm
> too busy. It's not urgent, we can do that part any time later...
>
> With best wishes,
> Mansur
> ___
> 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] dev.apertium.org for Apertium dev/collab work

[Tino Didriksen]

If someone needs a powerful machine to run tests on or collaborate on other
Apertium-related tasks, there is one available over SSH at dev.apertium.org

Specs:
- Intel Xeon E3-1275 v5 @ 3.6 GHz (4c/8t)
- 64 GB RAM
- 2x 512 GB NVMe SSD in RAID1, of which 2x32 GB is swap
- OS: Ubuntu 20.04 LTS, with Docker installed

I set it up for Nick Howell's attempt at building Chukti (which failed even
after consuming all 128 GB RAM) and he's been running various other tests
on it, but it would probably be nice to have a scratch space for everyone
to collaborate on - and this also ensures Torro (apertium.org main server)
is not used for development work.

So far, these people have SSH root access via SSH keys (no passwords
involved):
- Tino Didriksen
- Nick Howell (nlhowell)
- Kevin Brubeck Unhammer (Unhammer)
- Jonathan North Washington (firespeaker)
- Sushain Cherivirala (sushain)
- Francis M. Tyers (spectie)
- Xavi Ivars (xavivars)
- Daniel Swanson (popcorndude / mr-martian)
- Tommi Pirinen (Flammie)
- Tanmai Khanna (khannatanmai)

Feel free to add more people. Just don't step on others' work, and try to
keep the .ssh/authorized_keys file organized. Add users and/or use Docker
to keep your tests contained so they don't infest the whole machine.

And be mindful this is a scratch space server. No backups, no permanent
sites, everything is subject to nukes.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Anaphora Resolution 1.0.0

[Tino Didriksen]

Now also pushed to Debian
https://salsa.debian.org/science-team/apertium-anaphora

-- Tino Didriksen


On Sun, 21 Jun 2020 at 14:09, Tanmai Khanna  wrote:

> Hey Guys,
> The low resource anaphora resolution module
> <https://github.com/apertium/apertium-anaphora> of Apertium has a new
> release
> <https://github.com/apertium/apertium-anaphora/releases/tag/v1.0.0>.
>
> A summary of the new features:
> - Arx files now accept multiple anaphor-antecedent types using parameters.
> - Scores can be given to individual parameters.
> - exclude-tags and lemma can also be used in pattern matching.
> - apertium-validate-anaphora is installed, which validates arx files using
> a dtd file.
> - Automated tests added. Run using make test.
>
> These features make the module a lot more customisable, and can help you
> tailor the arx file to your language pair and the kind of data you want to
> deal with. If you need anaphora resolution in your language pair then you
> can reply to this email or contact me on the IRC and I'll help you set it
> up. You can refer to the documentation
> <https://wiki.apertium.org/wiki/Anaphora_resolution_module> if you want
> to get an idea about what it looks like.
>
> Francis and I are writing a paper on this module so if your language pair
> needs anaphora resolution then we can work on it and it will help us
> evaluate the module on other languages as well.
>
> Any clarifications can be asked here or on the IRC. I'd also appreciate it
> if you guys let me know about any feature requests you might have from a
> module like this. :)
>
> Thanks and Regards,
> *तन्मय खन्ना *
> *Tanmai Khanna*
> ___
> 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] New release for apertium-fra-cat

[Tino Didriksen]

Fixed.

No clue why the previous didn't take effect - the commands were in history
and some of the installed files had the right timestamp, but not all of
them.

-- Tino Didriksen


On Tue, 16 Jun 2020 at 23:17, Hèctor Alòs i Font 
wrote:

> apertium.org still has the old apertium-fra-cat version. Could someone
> update it?
> Thanks in advance.
> Hèctor
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium's Wider Use & Secondary Tags

[Tino Didriksen]

On Sat, 13 Jun 2020 at 17:50, Francis Tyers  wrote:

> As far as I understand the objective is to be able
> to
> put the original surface form in the output translation as an unknown
> token
> instead of the lemma.
>
> ...
>
> I think that the appropriate way to deal with this is by coming up with
> a
> clear plan for the linguistic eventualities. I don't see that in the
> current
> proposal. I have been showing Tanmai through the creation of a new MT
> system,
> and we have been documenting these issues as they arise. I don't think
> it makes
> sense to start development before they have been resolved.
>


Those are important issues, but they're orthogonal to how to transport
secondary information through the pipe. Even at the earliest stages of the
proposal, it was expanded to be 1) Get secondary tags through the pipe. 2)
Use that ability to eliminate trimming. 3) Use the same ability for a
myriad of other things, such as markup handling.

The objections and worries to #2 is blocking #1. And #1 in itself has
multiple quirks that need handling, such as what should happen to secondary
information when tokens are merged/split. We need to implement and solve #1
first - be able to transport (and potentially manipulate) any amount of
data that might be needed to solve #2 and #3 and ... #9.

The strategy for surface form handling has little to do with how to
transport them. So let us implement the generic flexible transport in the
best way first, as was the plan. If it then turns out surface form handling
needs more or different data, at that point we will have the way to
transport it.

Even if you entirely object to the goal of eliminating trimming, the goals
of generic flexible secondary data and what they lead to is sufficiently
important for the project to go ahead. And nobody has to eliminate trimming
- but they should be allowed to.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Apertium's Wider Use & Secondary Tags

[Tino Didriksen]

hould further lead
to a broader spectrum of uses, but this hasn't been consciously voiced by
anyone: Apertium is now more than a pet project for machine translation.

We have a wider ecosystem we should strive to work with. We already have
spell checkers in monolinguals - those have nothing to do with machine
translation. It is natural evolution that monolingual packages should be
able to stand on their own and provide corpus analysis, computer assisted
language learning (CALL), spell checkers, proofing tools, etc. Many of
those uses will require easy-to-use non-linguistic secondary tags in some
form. And even with machine translation, many uses will need secondary tags
in some form or another.

And I am not just talking without a basis here. I have implemented this
kind of stuff in GrammarSoft's pipelines. I have practical experience with
what the surrounding ecosystems want. We should make this easy and flexible
now - not hacks upon hacks that need adjusting every year.

I am not trying to usurp the linguistic basis. Naturally, Apertium should
be developed linguistics-first - which I also made rather clear in the last
PMC election. But I want to do away with the linguistics-only mindset.

Practically, right now I want a mandate from the community and PMC to
let Khannatanmai continue with inline secondary tags with short textual
prefixes, as originally envisioned and discussed in prior emails.

But I also want to open the discussion about what we actually want from
Apertium, because there's clearly a difference of opinion that needs
hashing out.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] pairs/apertium-uzb-kaa failed nightly build

[Tino Didriksen]

PKG_CHECK_MODULES(APERTIUM_RECURSIVE, apertium-recursive >= 0.0.1)

Wouldn't have helped in this case, because the build doesn't (and must not)
re-discover dependencies. When you add a new dep, it will break the first
build unless apertium-packaging is updated alongside.

-- Tino Didriksen



On Wed, 10 Jun 2020 at 06:15, Jonathan Washington <
jonathan.n.washing...@gmail.com> wrote:

> How do I require rtx-comp in configure?
>
> --
> Jonathan
>
> On Wed, Jun 10, 2020, 00:05  wrote:
>
>>
>> Package: pairs/apertium-uzb-kaa
>> started: Wed Jun 10 04:03:55 UTC 2020
>> latest: 0.2.0+g22~37f5f5e7
>> existing: 0.2.0+g20~7dc30f8f-1
>> distv: 1
>> making source package
>> data only
>> launching build
>> docker sid:amd64 build fail
>> stopped: Wed Jun 10 04:05:35 UTC 2020
>> FAILED:
>>
>> https://apertium.projectjj.com/apt/logs/apertium-uzb-kaa/sid-amd64.log
>> blames in revisions
>> 7dc30f8f..37f5f5e7bce618bc09599a6fc63dcf6b4e7e18af :
>> jonathan.north.washing...@gmail.com
>>
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium Query Results

[Tino Didriksen]

CC: apertium-stuff

Of the https://pastebin.com/ptRZz2XN queries, only 4 yielded any results:
https://apertium.projectjj.com/shashwat/

Is this
http://dbserver.acoli.cs.uni-frankfurt.de:5005/dataset.html?tab=query=/ds
something that we can run locally? Or can we approximate it? I've got
servers with 32 GB RAM and 2 TB free space to install stuff on.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Dysfunctional Languages & Pairs

[Tino Didriksen]

Tracked in https://github.com/apertium/organisation/issues/14 - if you fix
something, please reply there.

These languages and pairs do not currently build, for various reasons:

Languages:
https://github.com/apertium/apertium-ady see
https://github.com/apertium/apertium-ady/issues/2

https://github.com/apertium/apertium-ain segfaults when
generating ain.autogen.bin

https://github.com/apertium/apertium-ckt see
https://github.com/apertium/apertium-ckt/issues/1

https://github.com/apertium/apertium-ell see
https://github.com/apertium/apertium-ell/issues/4

https://github.com/apertium/apertium-epo missing modes.xml and see
https://github.com/apertium/apertium-epo/issues/2

https://github.com/apertium/apertium-gle has no modes.xml

https://github.com/apertium/apertium-lao is missing most things

https://github.com/apertium/apertium-mal errors out with:
.deps/mal.LR.lexc:24910.46-73: syntax error, unexpected ULSTRING, expecting
LEXICON_NAME or ':': [near: `പീപ്പള്സ്']

https://github.com/apertium/apertium-msa errors out with: No rule to make
target 'corpus/msa.tagged', needed by 'msa.prob'.

https://github.com/apertium/apertium-nio errors out with: The file
.deps/nio.LR.lexc did not compile cleanly.

https://github.com/apertium/apertium-pes has no configure.ac or modes.xml

https://github.com/apertium/apertium-quc has no configure.ac

https://github.com/apertium/apertium-snd has no configure.ac or modes.xml

https://github.com/apertium/apertium-trw errors out with:
.deps/trw.LR.lexc:309.10-16: syntax error, unexpected ULSTRING, expecting
LEXICON_NAME or ':': [near: `پوخ']

Pairs:
https://github.com/apertium/apertium-deu-dan errors out
with: deu-dan.autolex.bin: empty set of final states

https://github.com/apertium/apertium-ell-eng blocked by broken apertium-ell

https://github.com/apertium/apertium-en-ga see
https://github.com/apertium/apertium-en-ga/issues/1

https://github.com/apertium/apertium-en-pl see
https://github.com/apertium/apertium-en-pl/issues/2

https://github.com/apertium/apertium-eng-afr see
https://github.com/apertium/apertium-eng-afr/issues/4

https://github.com/apertium/apertium-eng-pes blocked by broken apertium-pes

https://github.com/apertium/apertium-eo-ru blocked by broken apertium-epo

https://github.com/apertium/apertium-eus-fin see
https://github.com/apertium/apertium-eus-fin/issues/1

https://github.com/apertium/apertium-fao-dan see
https://github.com/apertium/apertium-fao-dan/issues/1

https://github.com/apertium/apertium-fin-udm errors out
with: .deps/fin.LR.lexc:19.7-9: syntax error, unexpected ULSTRING,
expecting LEXICON_NAME: [near: `PX']

https://github.com/apertium/apertium-it-pt see
https://github.com/apertium/apertium-it-pt/issues/1

https://github.com/apertium/apertium-kpv-fin see
https://github.com/apertium/apertium-kpv-fin/issues/1

https://github.com/apertium/apertium-kpv-mhr see
https://github.com/apertium/apertium-kpv-mhr/issues/1

https://github.com/apertium/apertium-mal-eng blocked by broken apertium-mal

https://github.com/apertium/apertium-mlt-spa errors out
with: apertium-mlt-spa.mlt-spa.lrx:8: parser error : Specification mandates
value for attribute fil

https://github.com/apertium/apertium-mrj-fin errors out with:
.deps/fin.RL.lexc:769.11-18: syntax error, unexpected ULSTRING, expecting
LEXICON_NAME or ':': [near: `V_ISTUA']

https://github.com/apertium/apertium-oci-spa see
https://github.com/apertium/apertium-oci-spa/issues/1

https://github.com/apertium/apertium-olo-fin errors out
with: .deps/olo.RL.lexc:115.14: syntax error, unexpected ERROR, expecting
LEXICON_START or LEXICON_START_WRONG_CASE: [near: `%']

https://github.com/apertium/apertium-pes-eng blocked by broken apertium-pes

...which just made me realize both
https://github.com/apertium/apertium-eng-pes and
https://github.com/apertium/apertium-pes-eng exist? Someone fix that.

https://github.com/apertium/apertium-quc-spa blocked by broken apertium-quc

https://github.com/apertium/apertium-snd-hin blocked by broken apertium-snd

https://github.com/apertium/apertium-spa-pol fails to validate the acx from
https://github.com/apertium/apertium-pol

https://github.com/apertium/apertium-tgk-pes blocked by broken apertium-pes

https://github.com/apertium/apertium-tha-lao blocked by broken apertium-lao

https://github.com/apertium/apertium-tuk-tur see
https://github.com/apertium/apertium-tuk-tur/issues/1

https://github.com/apertium/apertium-tur-aze errors out
with: 010-exception_deye.fst: 21terminate called after throwing an instance
of 'std::logic_error'

https://github.com/apertium/apertium-tur-fin see
https://github.com/apertium/apertium-tur-fin/issues/1

https://github.com/apertium/apertium-tzh-spa feels like most files were
forgotten in a commit

https://github.com/apertium/apertium-urd-snd blocked by broken apertium-snd

https://github.com/apertium/apertium-urd-trw blocked by broken apertium-trw

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium

Re: [Apertium-stuff] New release for apertium-fra-cat

[Tino Didriksen]

Done.

Tarballs uploaded to Github, release live on apertium.org, and pushed to
https://salsa.debian.org/science-team/apertium-fra-cat

-- Tino Didriksen


On Fri, 22 May 2020 at 06:14, Hèctor Alòs i Font 
wrote:

> A new release of apertium-fra-cat is ready to be packaged.
>
> It mostly contains almost 3,000 new translations in the bidix, many of
> them on the basis of translations of current newspaper news and social
> network chats, especially from French to Catalan. Colloquial (and Covid-19)
> language is now much better grasped.
>
> Please, @Tino Didriksen , could you package the
> release?
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium Beta Portal

[Tino Didriksen]

https://beta.apertium.org/ is now back online.

-- Tino Didriksen
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Nightly Batch Add & Edit

[Tino Didriksen]

And done. Added the below packages, and modified the further below ones.
Same caveat applies - just because it's added doesn't mean it builds,
though I have polished away a ton of bit-rot.

Also added all the public giella-* packages, since some Apertium pairs
depend on those.

The list at https://apertium.projectjj.com/pkgs.php will show what's
actually available via apt-get.

Added pairs:
apertium-fin-eng
apertium-fin-fkv
apertium-fin-fra
apertium-fin-gle
apertium-fin-hbs
apertium-fin-hun
apertium-fin-isl
apertium-fin-ita
apertium-fin-kaz
apertium-fin-krl
apertium-fin-nor
apertium-fin-olo
apertium-fin-por
apertium-fin-rus
apertium-fin-spa
apertium-fin-swe
apertium-fin-udm
apertium-fra-frp
apertium-fra-ina
apertium-fra-ita
apertium-fra-por
apertium-fra-ron
apertium-ga-gd
apertium-gle-eng
apertium-grn-spa
apertium-guc-spa
apertium-guj-hin
apertium-haw-eng
apertium-hbs-rus
apertium-hin-pan
apertium-ht-en
apertium-ina-spa
apertium-ind-eng
apertium-isl-rus
apertium-it-pt
apertium-ita-nor
apertium-kan-mar
apertium-kaz-kaa
apertium-kaz-kum
apertium-kaz-sah
apertium-kaz-tur
apertium-kaz-tyv
apertium-kaz-uig
apertium-khk-kaz
apertium-kik-lin
apertium-kir-uzb
apertium-kmr-eng
apertium-kpv-fin
apertium-kpv-koi
apertium-kpv-mhr
apertium-krl-olo
apertium-la-es
apertium-lat-eng
apertium-liv-fin
apertium-lv-lg
apertium-mal-eng
apertium-mar-hin
apertium-mkd-sqi
apertium-mlt-heb
apertium-mlt-spa
apertium-mrj-fin
apertium-myv-fin
apertium-myv-mdf
apertium-ne-en
apertium-nor-eng
apertium-oci-cat
apertium-oci-spa
apertium-olo-fin
apertium-pes-eng
apertium-pl-csb
apertium-pl-sk
apertium-pol-rus
apertium-pol-ukr
apertium-por-ina
apertium-quc-spa
apertium-ro-it
apertium-scn-spa
apertium-si-en
apertium-sjo-eng
apertium-sl-mk
apertium-slv-ita
apertium-slv-spa
apertium-sme-est
apertium-snd-hin
apertium-spa-cos
apertium-spa-deu
apertium-spa-glg
apertium-spa-lvs
apertium-spa-pol
apertium-spa-qve
apertium-swe-eng
apertium-tam-eng
apertium-tat-bak
apertium-tat-kaa
apertium-tel-mar
apertium-tgk-pes
apertium-tha-eng
apertium-tha-lao
apertium-tlh-swe
apertium-tuk-tur
apertium-tur-aze
apertium-tur-fin
apertium-tur-kir
apertium-tur-tat
apertium-tur-uzb
apertium-tzh-spa
apertium-udm-kpv
apertium-udm-rus
apertium-uig-tur
apertium-urd-pan
apertium-urd-snd
apertium-urd-trw
apertium-uzb-kaa
apertium-vro-est
apertium-zho-spa


Modified in some way:
apertium-bak
apertium-grn
apertium-hin
apertium-isl
apertium-kaa
apertium-kaz
apertium-kmr
apertium-lat
apertium-mar
apertium-mlt
apertium-pol
apertium-sah
apertium-spa
apertium-tel
apertium-tha
apertium-tur
apertium-uig
apertium-uzb

apertium-fin-eng
apertium-fin-fkv
apertium-fin-fra
apertium-fin-ita
apertium-fin-spa
apertium-fin-swe
apertium-fin-udm
apertium-ga-gd
apertium-grn-spa
apertium-hbs-rus
apertium-ht-en
apertium-isl-rus
apertium-it-pt
apertium-kaz-kaa
apertium-kaz-kum
apertium-kaz-uig
apertium-khk-kaz
apertium-kir-uzb
apertium-kpv-fin
apertium-kpv-mhr
apertium-la-es
apertium-liv-fin
apertium-lv-lg
apertium-mlt-spa
apertium-mrj-fin
apertium-ne-en
apertium-oci-spa
apertium-olo-fin
apertium-pl-csb
apertium-ro-it
apertium-si-en
apertium-sl-mk
apertium-slv-spa
apertium-spa-glg
apertium-spa-pol
apertium-tat-kaa
apertium-tuk-tur
apertium-tur-aze
apertium-tur-fin
apertium-udm-rus

-- Tino Didriksen


On Fri, 29 May 2020 at 19:04, Tino Didriksen  wrote:

> I've batch-added the below packages to the nightly build. They don't all
> build, but most do, and the ones that don't have errors that I can't fix.
>
> In order to make some of them build, I've made changes to their repos.
> Many with force-pushed history rewrites to remove files that should never
> have been in the repo to begin with. That list is further below.
>
> This is part 1 of probably 2. I got a long way today, but still have
> another 117 pairs to check.
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Apertium Beta Portal

[Tino Didriksen]

It will be fixed soon (probably this long weekend), and with much more
content. We've moved server, and beta hasn't been re-established yet.

-- Tino Didriksen


On Sat, 30 May 2020 at 15:51, mansur <6688...@gmail.com> wrote:

> Hey!
>
> It turned out, the Apertium Beta portal stopped working for some reason:
> http://beta.apertium.org/
> If I use httpS it redirects to the wiki page.
>
> Will it be fixed sometime soon? If not, what should we use that includes
> beta features?
>
> With best regards,
> Mansur
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff