apertium-stuff Mailing List for Apertium: Machine Translation Toolbox

Aperitium spa-cat heavily uses the preferences system to choose features
between variants (and even different standards or language styles within
the same dialect) by doing exactly what Kevin and Tino propose.

The dictionary is tagged with the features, and then different modes apply
different cg files (see
https://github.com/apertium/apertium-cat/blob/master/apertium-cat.cat_valencia.prefs.rlx
and other similar files) that apply those preferences by default.
--
Xavi Ivars
< http://xavi.ivars.me >

El dc., 19 de juny 2024, 15:44, Kevin Brubeck Unhammer <unh...@fs...>
va escriure:

> > How can I define src_lengadocian as the variable that means the source
> > language is lengadocian ?
>
> Hm, it kind of depends. In general, if you use variables, you can do
>
>     export AP_SETVAR=src_lengadocian
>     echo mau o mal | apertium -d . oci-fra
>
> and that variable will be available to the CG as VAR:src_lengadocian
>
> If you put it in oci-fra.preferences.xml, it will also show up on the
> web like the Preferences d'estil button at
> https://beta.apertium.org/index.cat.html#?dir=cat-spa
>
> But maybe these source language differences actually *should* be kept as
> separate pipelines, and shown as different source languages in the
> language selector in the web UI? In that case, it might actually be
> simpler to not do variables at all, and just have a separate CG file
> with lengadocian rules that runs before the regular CG. So in your
> oci-fra_lengadocian mode in
> https://github.com/apertium/apertium-oci-fra/blob/master/modes.xml#L373
> instead of
>
>       <program name="lt-proc -w">
>         <file name="oc...@le...n"/>
>       </program>
>       <program name="cg-proc -w" debug-suff="disamb">
>         <file name="oci-fra.rlx.bin"/>
>       </program>
>
> you would have the general automorf, but two CG disambiguator steps
>
>       <program name="lt-proc -w">
>         <file name="oci-fra.automorf.bin"/>
>       </program>
>       <program name="cg-proc" debug-suff="disamb-lengadocian">
>         <file name="oc...@le...n"/>
>       </program>
>       <program name="cg-proc -w" debug-suff="disamb">
>         <file name="oci-fra.rlx.bin"/>
>       </program>
>
> and the first CG would just have a few rules for lengadocian-specific
> stuff.
>
>
>
>
> _______________________________________________
> Apertium-stuff mailing list
> Ape...@li...
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>

> How can I define src_lengadocian as the variable that means the source
> language is lengadocian ?

Hm, it kind of depends. In general, if you use variables, you can do

    export AP_SETVAR=src_lengadocian
    echo mau o mal | apertium -d . oci-fra 

and that variable will be available to the CG as VAR:src_lengadocian

If you put it in oci-fra.preferences.xml, it will also show up on the
web like the Preferences d'estil button at
https://beta.apertium.org/index.cat.html#?dir=cat-spa

But maybe these source language differences actually *should* be kept as
separate pipelines, and shown as different source languages in the
language selector in the web UI? In that case, it might actually be
simpler to not do variables at all, and just have a separate CG file
with lengadocian rules that runs before the regular CG. So in your
oci-fra_lengadocian mode in
https://github.com/apertium/apertium-oci-fra/blob/master/modes.xml#L373
instead of

      <program name="lt-proc -w">
        <file name="oc...@le...n"/>
      </program>
      <program name="cg-proc -w" debug-suff="disamb">
        <file name="oci-fra.rlx.bin"/>
      </program>

you would have the general automorf, but two CG disambiguator steps

      <program name="lt-proc -w">
        <file name="oci-fra.automorf.bin"/>
      </program>
      <program name="cg-proc" debug-suff="disamb-lengadocian">
        <file name="oc...@le...n"/>
      </program>
      <program name="cg-proc -w" debug-suff="disamb">
        <file name="oci-fra.rlx.bin"/>
      </program>

and the first CG would just have a few rules for lengadocian-specific
stuff.

Thanks a lot !

How can I define src_lengadocian as the variable that means the source 
language is lengadocian ?

	


    AureSÉGUIER

Responsabla del pòle informatic

Congrès permanent de la lenga occitana

	

	
	

	
mobilePhone

	+33 (0)5 32 00 00 64 <tel:+33 (0)5 32 00 00 64>
website

	www.locongres.org <//www.locongres.org>
address

	La Ciutat - Creem! , 5-7 rue de la Fontaine, 64000 Pau





	
facebook <https://www.facebook.com/lo.congres> 	

	twitter <https://twitter.com/locongres> 	

	linkedin 
<https://www.linkedin.com/company/congres-permanent-de-la-lenga-occitane/> 	

	instagram <https://www.instagram.com/locongres/> 	



Le 19/06/2024 à 10:53, Kevin Brubeck Unhammer a écrit :
>> Occitan can manage variety in its metadix file. My question is, is
>> there a way to manage variety in the .rlx file ?
> There is :)
>
>> For instance, we have the word "bad", "evil" which is "mal" in
>> lengadocian and "mau" en gascon. But "mau" can also be a conjugated
>> verb (a pretty rare one). I did this rule in the RLX file : REMOVE V
>> IF (0 ("<mau>"i));
>> But I would want this rule not to apply to lengadocian, where "mau"
>> can only be a conjugated verb.
>> Is that possible ? If not, is this something easy to implement ?
> Yes. You could for example say that "src_lengadocian" is the variable
> that signifies that the source language is lengadocian, and then have
> one rule that picks the verb if source language is lengadocian:
>
>      SELECT V IF (0 ("<mau>"i))        (0 (VAR:src_lengadocian)) ;
>
> and one that removes it if not:
>
>      REMOVE V IF (0 ("<mau>"i)) (NEGATE 0 (VAR:src_lengadocian)) ;
>
>
> I can't say for certain if this system makes things simpler or not for
> you compared to metadix, but it allows for a lot more flexibility, with
> much shorter compile times (since we have just one compiled FST which
> contains all the variety).
>
>
>
> _______________________________________________
> Apertium-stuff mailing list
> Ape...@li...
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff

> Occitan can manage variety in its metadix file. My question is, is
> there a way to manage variety in the .rlx file ?

There is :)

> For instance, we have the word "bad", "evil" which is "mal" in
> lengadocian and "mau" en gascon. But "mau" can also be a conjugated
> verb (a pretty rare one). I did this rule in the RLX file : REMOVE V
> IF (0 ("<mau>"i));
> But I would want this rule not to apply to lengadocian, where "mau"
> can only be a conjugated verb.
> Is that possible ? If not, is this something easy to implement ?

Yes. You could for example say that "src_lengadocian" is the variable
that signifies that the source language is lengadocian, and then have 
one rule that picks the verb if source language is lengadocian:

    SELECT V IF (0 ("<mau>"i))        (0 (VAR:src_lengadocian)) ;

and one that removes it if not:

    REMOVE V IF (0 ("<mau>"i)) (NEGATE 0 (VAR:src_lengadocian)) ;


I can't say for certain if this system makes things simpler or not for
you compared to metadix, but it allows for a lot more flexibility, with
much shorter compile times (since we have just one compiled FST which
contains all the variety).

Hi

I read the documentation you mentioned but I didn't understood very well.

Occitan can manage variety in its metadix file. My question is, is there 
a way to manage variety in the .rlx file ?

For instance, we have the word "bad", "evil" which is "mal" in 
lengadocian and "mau" en gascon. But "mau" can also be a conjugated verb 
(a pretty rare one). I did this rule in the RLX file : REMOVE V IF (0 
("<mau>"i));
But I would want this rule not to apply to lengadocian, where "mau" can 
only be a conjugated verb.
Is that possible ? If not, is this something easy to implement ?

I need to have an answer to this question in order to know if it would 
be interesting to change the way we manage variety or not.

Thanks

	


    AureSÉGUIER

Responsabla del pòle informatic

Congrès permanent de la lenga occitana

	

	
	

	
mobilePhone

	+33 (0)5 32 00 00 64 <tel:+33 (0)5 32 00 00 64>
website

	www.locongres.org <//www.locongres.org>
address

	La Ciutat - Creem! , 5-7 rue de la Fontaine, 64000 Pau





	
facebook <https://www.facebook.com/lo.congres> 	

	twitter <https://twitter.com/locongres> 	

	linkedin 
<https://www.linkedin.com/company/congres-permanent-de-la-lenga-occitane/> 	

	instagram <https://www.instagram.com/locongres/> 	



Le 14/06/2024 à 13:09, Tino Didriksen a écrit :
> 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 <a.s...@lo...> 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
>
>     -- 
>     	
>
>
>         AureSÉGUIER
>
>     Responsabla del pòle informatic
>
>     Congrès permanent de la lenga occitana
>
>     	
>     	
>     	
>     	
>     mobilePhone
>
>     	+33 (0)5 32 00 00 64 <tel:+33%20(0)5%2032%2000%2000%2064>
>     website
>
>     	www.locongres.org <//www.locongres.org>
>     address
>
>     	La Ciutat - Creem! , 5-7 rue de la Fontaine, 64000 Pau
>
>
>
>
>
>     	
>     facebook <https://www.facebook.com/lo.congres> 	
>     	twitter <https://twitter.com/locongres> 	
>     	linkedin
>     <https://www.linkedin.com/company/congres-permanent-de-la-lenga-occitane/>
>     	
>     	instagram <https://www.instagram.com/locongres/> 	
>
>
>

> On Tue, 4 Jun 2024 at 17:44, Aure Séguier <a.s...@lo...> wrote:

>> 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...).

If you use the "new" system documented at
https://wiki.apertium.org/wiki/Dialectal_or_standard_variation#Overlapping_variants
with AP_SETVAR etc., then the variant info is available in all CG files,
not just the ones that select bidix/generator choices, but also the disambiguator.

So you could have source variant tags as well as target variant. E.g. if
you want to say that your source language is gascon, you could

    export AP_SETVAR='src_gascon'

or something like that, and then in CG, if for example "que" is used as
a personal pronoun only in Gascon, you could do

    SELECT pers IF (0 ("que") + (VAR:src_gascon));
    REMOVE pers IF (0 ("que")); # not gascon

Or you could make it more nuanced and feature-based like

    export AP_SETVAR='src_que_pers,src_other_feature'

    SELECT pers IF (0 ("que") + (VAR:src_que_pers));
    …

(if, say, both Gascon and Bigourdan use que as personal pronoun, but only
Gascon has other_feature as well)

With this system, the .dix file is more ambiguous, but it's easy to do
early removal of irrelevant stuff from CG.

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 <a.s...@lo...> 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 <//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/>
>
>
>
>

Hello,

We are happy to announce the WMT 2024 shared task on machine translation of Spanish texts 
into the following underrepresented Romance languages of Spain: Aragonese, Aranese, and 
Asturian.

In Spain, alongside Spanish, languages like Basque, Catalan, and Galician enrich the 
linguistic landscape. While Spanish dominates machine translation resources, other 
languages like Basque, Catalan, and Galician now provide substantial data for modern 
systems. Yet, Spain also hosts truly low-resource languages like Aragonese, Aranese, and 
Asturian, with far fewer resources, particularly in bilingual data.

The objectives of this shared task are to advance machine translation in resource-scarce 
settings, investigate transferability among low-resource Romance languages when 
translating from Spanish, optimize the utilization of pre-trained models for 
Spanish-low-resource Romance language translation, and establish publicly accessible 
corpora for machine translation development and evaluation.

Tailored datasets and language detectors have been released, along with the FLORES+ 
sentences, now available in these three languages and revised by official language 
academies to align with current orthographic standards.

For more information please have a look at the shared task description: 
https://www2.statmt.org/wmt24/romance-task.html

For questions please write to rom...@dl....

We are looking forwards to your submission!

Juan Antonio Pérez-Ortiz, Universitat d’Alacant
Felipe Sánchez-Martínez, Universitat d’Alacant
Antoni Oliver, Universitat Oberta de Catalunya
-- 
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: fsa...@ua..., fsa...@dl...

Web: https://www.dlsi.ua.es/~fsanchez/

Dear Apertium Community,

I'm interested in taking part in GSOC-24. I have completed and communicated
the coding challenge through IRC. I'm sharing my proposal  (
https://wiki.apertium.org/wiki/User:Maharaj/GSoC2024Proposal) for review
and consideration.

Thanks.

-----
With Regards,
Maharaj Brahma
Research Scholar
Natural Language and Information Processing Lab (NLIP Lab)
Dept. of Computer Science & Engineering
Indian Institute of Technology Hyderabad (IITH)

-- 


Disclaimer:- This footer text is to convey that this email is sent by one 
of the users of IITH. So, do not mark it as SPAM.

Dear Daniel,

Sorry for not explaining that part in my proposal, Here's how it could work
for corrected translations:

Users can submit their suggestions for corrected translations through a
form on the website. This form could include fields for the original text,
the current translation, and the suggested correction. Users could also
provide context or explanations for their suggestions to help the team
understand the reasoning behind the correction. The suggestions would be
sent to the backend (apertium-apy) and stored in a database. This would
allow the team to review the suggestions and decide which ones to
implement. The team would regularly review the suggestions, they could use
these suggestions to improve the translation model, correct errors in the
database, or update the website content.

Best regards,
Ahmed A. Elhossieny

On Mon, 1 Apr 2024 at 03:03, Daniel Swanson <awe...@gm...>
wrote:

> Hi Ahmed,
>
> My biggest question after reading your proposal is how will the suggestion
> system work? What will people submit? Where will the suggestions be sent or
> stored?
>
> Daniel
>
> On Sun, Mar 31, 2024 at 8:55 PM Ahmed Elhossieny <
> ahm...@gm...> wrote:
>
>> Dear Apertium GSoC Mentors,
>> I hope this email finds you well. I'd appreciate your review of my GSoC
>> proposal for the "Website Improvements: Misc and Suggestions" project.
>>
>> Link to my proposal:
>> https://wiki.apertium.org/wiki/User:Cellzawy/GSoC2024Proposal
>>
>> Best regards,
>> Ahmed A. Elhossieny
>> _______________________________________________
>> Apertium-stuff mailing list
>> Ape...@li...
>> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>>
> _______________________________________________
> Apertium-stuff mailing list
> Ape...@li...
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>

Hi Ahmed,

My biggest question after reading your proposal is how will the suggestion
system work? What will people submit? Where will the suggestions be sent or
stored?

Daniel

On Sun, Mar 31, 2024 at 8:55 PM Ahmed Elhossieny <
ahm...@gm...> wrote:

> Dear Apertium GSoC Mentors,
> I hope this email finds you well. I'd appreciate your review of my GSoC
> proposal for the "Website Improvements: Misc and Suggestions" project.
>
> Link to my proposal:
> https://wiki.apertium.org/wiki/User:Cellzawy/GSoC2024Proposal
>
> Best regards,
> Ahmed A. Elhossieny
> _______________________________________________
> Apertium-stuff mailing list
> Ape...@li...
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>

Dear Apertium GSoC Mentors,
I hope this email finds you well. I'd appreciate your review of my GSoC
proposal for the "Website Improvements: Misc and Suggestions" project.

Link to my proposal:
https://wiki.apertium.org/wiki/User:Cellzawy/GSoC2024Proposal

Best regards,
Ahmed A. Elhossieny

The user account for Pedromanic (talk) has been created.

password sent by email

Daniel

On Thu, Mar 28, 2024 at 2:29 PM Pedro Manicardi Soares via Apertium-stuff <
ape...@li...> wrote:

> Dear Apertium admins,
>
> My name is Pedro Manicardi and I am writing to request the creation of a
> Wiki account.
> Username: pedromanic
> Email Address:  ped...@us...
>
> Thanks
> Best regards,
> Pedro
> _______________________________________________
> Apertium-stuff mailing list
> Ape...@li...
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>

Dear Apertium admins,

My name is Pedro Manicardi and I am writing to request the creation of a
Wiki account.
Username: pedromanic
Email Address:  ped...@us...

Thanks
Best regards,
Pedro

Dear Apertium Mentors

Please review my Gsoc proposal titled 'spell-checking interface for
Apertium's web tools.' Your feedback would be greatly appreciated
You can find my proposal here:
 https://wiki.apertium.org/wiki/User:Harikrishna/GSoC2024Proposal

Your suggestions would be incredibly helpful as I refine my project
proposal. Thank you very much for your time and consideration.

Best regards,
Hari Krishna

Dear Apertium Admins,
I am writing to request a Wiki account.

Username: pedromanic
email: ped...@us...

Thanks

Hi Apertium GSoC Mentors,

Just checking in on my GSoC proposal for "Robust Tokenization in
Lttoolbox." I'd really appreciate your review of the proposal before I move
forward.

You can check it out from here:
https://wiki.apertium.org/wiki/User:Medobob/GSoC2024Proposal

No worries if you're busy, but any feedback would be great!

Thanks,
Mohamed Adel


On Thu, Mar 21, 2024 at 10:35 PM Mohamed Adel <
moh...@gm...> wrote:

> Dear Apertium GSoC Mentors,
>
> I'd appreciate your review of my GSoC proposal: "Robust Tokenization in
> Lttoolbox".
>
> You can find the proposal here:
> https://wiki.apertium.org/wiki/User:Medobob/GSoC2024Proposal
>
> Thanks!
>
> Mohamed Adel.
>

Hi Xavi lvars,

I hope this email finds you well.

I'm interested in the project idea of the Spell Checker web interface.
Currently, I'm working on preparing a project proposal, and I noticed there
wasn't a coding challenge associated with it. Could you provide guidance on
the next steps?

Additionally, I've contributed approximately 4 pull requests to Apertium
HTML Tools.


Best regards,
Hari Krishna

Check your inbox (and spam folder if not there) for a password.

akun wiki

Pada Sen, 25 Mar 2024, 11.46, Hari <har...@gm...> menulis:

> Dear Apertium Community,
>
> My name is Hari Krishna, and I am writing to kindly request the creation
> of a Wiki account.
>
> Username: harikrishna
> Email Address: har...@gm...
>
> Thank you for considering my request.
>
> Best regards,
> Hari Krishna
> _______________________________________________
> Apertium-stuff mailing list
> Ape...@li...
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>

Dear Apertium Community,

My name is Hari Krishna, and I am writing to kindly request the creation of
a Wiki account.

Username: harikrishna
Email Address: har...@gm...

Thank you for considering my request.

Best regards,
Hari Krishna

Dear Apertium Admins,

I hope this email finds you well, I am reaching out to ask for a wiki
account.

Username: Cellzawy
Email address: ahm...@gm... <ahm...@gm...>

Thank you for considering my request. I appreciate your time and assistance.

Best regards,
Ahmed Elhossieny

Dear Apertium Members,

I'm Ahmed, a sophomore at Ain Shams University, pursuing my Computer
Science bachelor.
I am passionate about CSS and general web design. My true passion is
creating visually appealing and user-friendly interfaces. My skill set
includes C++, Javascript, React and some more.
I would love to participate in GSoC '24 with Apertium and I am interested
in working on the "Website Improvements: Misc" project.

My next step is to work on my proposal while solving some open issues.

Let's connect:
My github profile: https://github.com/Cellzawy
My linkedin profile: https://www.linkedin.com/in/aelhossieny/

Best Regards,
Ahmed A. Elhossieny

Dear Apertium GSoC Mentors,

I'd appreciate your review of my GSoC proposal: "Robust Tokenization in
Lttoolbox".

You can find the proposal here:
https://wiki.apertium.org/wiki/User:Medobob/GSoC2024Proposal

Thanks!

Mohamed Adel.

> 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.

OK, so under the heading saying "2024 Status: Accepted" you have to
click on the Rules and ToS and hit accept on them too.

(It was not immediately obvious that I still had something unfinished
there. They should have some kind of
    Inbox (2) 
to make it clear.)