This is essentially how spellrelax works in modern language modules.
To see how it's implemented, you can have a look at the spellrelax file and
Makefile.am for recent language modules, e.g.:
https://github.com/apertium/apertium-yua
--
Jonathan
On Fri, May 19, 2023, 08:55 Zanga Chimombo wrote:
Washington
wrote:
>
> -- Forwarded message -
> From: Yunze Song
> Date: Thu, Mar 30, 2023, 11:39
> Subject: Questions regarding Apertium-related matters [Google Summer of
> Code]
>
>
>
> Dear Prof. Jonathan Washington,
>
> I hope this email finds
Hi Eijisan,
There's also the tokeniser used for Nuosu, which uses the transducer itself
to tokenise:
https://github.com/apertium/apertium-iii
I believe this is a later implementation of what's described in the thesis
sent by Kevin in [2].
This method has some downsides, but it also has some
I'm also happy to mentor! (And help with recursive transfer:) I made
sure my name was on all the projects I'd like to mentor.
--
Jonathan
27 yan 2023, C. tarixində 22:29 tarixində Hèctor Alòs i Font
yazdı:
>
> Missatge de Kevin Brubeck Unhammer del dia dv., 27 de
> gen. 2023 a les 23:41:
>>
Thanks for sharing this great news, Daniel!
Is there anything special that needs to be done to leverage this new
approach to capitalisation in new pairs created using apertium-init?
--
Jonathan
27 dek 2022, Ç.a. tarixində 10:33 tarixində Daniel Swanson
yazdı:
>
> Greetings Apertiumers!
>
> For
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, Ç.
(LISTED ALPHABETICALLY)
Atul Kr. Ojha, DSI, National University of Ireland Galway & Panlingua
Language Processing LLP
Chao-Hong Liu, Potamu Research Ltd
Ekaterina Vylomova, University of Melbourne, Australia
Jade Abbott, Retro Rabbit
Jonathan Washington, Swarthmore College
Nathaniel Oco, Nati
I'm also happy with either approach. I support avoiding bureaucracy,
but I get Tanmai's point about appearances. But then, being friendly
and going forward unanimously and unbureaucratically is also an
appearance :D
--
Jonathan
27 apr 2022, Ç. tarixində 08:08 tarixində Juan Pablo yazdı:
>
>
I would also like to run for the PMC again.
--
Jonathan
26 apr 2022, Ç.a. tarixində 03:36 tarixində Kevin Brubeck Unhammer
yazdı:
>
> > === Candidates:
> > Do you want to be a PMC member? Speak up!
>
> I do.
>
>
> -Kevin
> ___
> Apertium-stuff mailing
I think Sushain set up the analytics stuff a long time ago, if that's what
that is?
--
Jonathan
On Mon, Apr 18, 2022, 15:36 Xavi Ivars wrote:
> It didn't sound familiar, but I double-checked. I don't.
>
> Missatge de Tino Didriksen del dia dl., 18
> d’abr. 2022 a les 21:00:
>
>> Hello
21 noy 2021, B. tarixində 13:43 tarixində Bernard Chardonneau
yazdı:
> Last year, I decided to change Debian 7 to Debian 10. Still another horrible
> graphic interface and the graphic editor gedit changed loosing his top menu.
> I lost several file changes because I had problems to find the way
As to Andrey's question concerning kaz-rus not working because of a
missing .t4x file, that sounds like a legit packaging error, which I'm
not sure how to fix (I really should learn...)
In the meantime, Andrey, you should be able to just clone the pair and
compile from source (`apertium-get
-- Forwarded message -
From: Atul Kr. Ojha
Date: Wed, Jun 2, 2021 at 11:52 PM
Subject: LoResMT 2021: Final Call for Papers - Low-Resource Languages Workshop
To: Jonathan Washington
Cc: Chao-Hong
Dear Jonathan,
Hope you are doing well!!
I was wondering if you could please post
While things are being fixed, it might be better to use Apertium, like
ind instead of indef. But that's less important.
--
Jonathan
5 may 2021, Ç. tarixində 09:53 tarixində Daniel Swanson
yazdı:
>
> The forms in question are used in the kok-hin bidix, so that would
> need to be updated too.
>
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
Hi Eduard,
Are you using the translation pair locally or via a website? If the
former, how did you install it? If the latter, which website?
--
Jonathan
9 apr 2021, C. tarixində 02:59 tarixində Eduard Urgell
yazdı:
>
> Hi,
>
> Is there any known issue with machine translation for the
Hi Utku,
Just to follow up on Hèctor's points, for the coding challenge, we'd
want to see a prototype of the transducer. It doesn't have to have
any real level of usefulness, but it should solve some of the types of
problems you expect to encounter. That is, you should be about to
implement a
t;>
>>> Thanks, Jonathan, Daniel has converted the existing work to lexd as he
>>> offered to do it. It is really great this way, I will wait for it to be
>>> merged in order to pull it.
>>>
>>> Creating a morphological analyser is one of my goals, I d
Hi Okonkwo,
Thank you for your continued interest in Apertium!
My main comment on this latest version of your proposal is that you
don't mention morphology. This should be a main focus of your
work—not just expanding the lexicon, but making it productive.
Also, given the range of
Hi Subham,
I should note there are other ways to contribute to Apertium besides
through language pairs:
https://wiki.apertium.org/wiki/Contributing
You can also check out open issues on any Apertium github repo, and offer
your assistance in fixing the issur:
https://github.com/apertium/
--
Hi Christian,
We're certainly open to collaborations, and would be happy to receive your
application for GSoC if we become a mentoring organisation this year.
Many of the potential Apertium GSoC mentors generally prefer to devote
resources (including mentoring time and GSoC slots) to supporting
Dear colleagues (apologies for cross-posting),
Sevilay (CCed) and I have submitted an application to the ISO 639-3
registrar for a new three-letter code for Sevilay's native language,
Iraqi Türkman, to be added to the standard:
https://iso639-3.sil.org/request/2020-039
The registration authority
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?
--
Jonathan
On Mon, Sep 21, 2020, 10:15 Francis Tyers wrote:
> El 2020-09-21 15:07, Tino Didriksen escribió:
> > On Mon, 21
I ran into this recently too:
https://pytwolc.readthedocs.io/en/latest/index.html
I haven't looked at who wrote it, or looked closely at the whole thing, but
it looks fairly thorough.
--
Jonathan
On Tue, Sep 15, 2020, 10:57 Francis Tyers wrote:
> El 2020-09-14 07:27, Flammie A Pirinen
Apertiumers,
See the following information about a workshop of relevance.
--
Jonathan
=
Dear ALL,
We are organizing RESOURCEFUL-2020 (RESOURCEs and Representations For
Under-resourced Languages and Domains) which will be collocated with the
Eighth Swedish Language Technology Conference
Hi Zanga,
Given the highly agglutinative nature of Yao morphology, using dix to model
it is probably not a great option. Also, as you and Hèctor have concluded,
the morphophonology will be much easier to model using twol.
Given the extent to which the morphology involves prefixes, lexc (what we
s you find a work-around.
--
Jonathan
On Sun, Aug 16, 2020, 01:52 Medina, Gabriel wrote:
> When I pick a language, it only highlights specific ones I can only
> choose, which depends on the language you pick, which makes translating
> languages very limited.
>
> On Sat, Aug 15,
Gabriel,
Could you clarify what you mean by "language barriers"?
--
Jonathan
On Sat, Aug 15, 2020, 13:40 Medina, Gabriel wrote:
> Does this have something to do with the language barriers for all
> languages on the online translator?
>
> On Sat, Aug 15, 2020 at 1:03 PM Marc Riera Irigoyen <
>
Dear Apertium community,
Here are some upcoming courses/workshops that might be of interest to
some of you. (Also, the programme is hosted by my alma mater!)
--
Jonathan
-- Forwarded message -
From: Rikker Dockum
Date: Fri, Jun 26, 2020 at 4:42 PM
Subject: An interesting
> On Sun, Jun 14, 2020, 04:01 Francis Tyers wrote:
>
>> El 2020-06-14 11:51, Hèctor Alòs i Font escribió:
>> > Missatge de Francis Tyers del dia dg., 14 de
>> > juny 2020 a les 10:32:
>> >
>> >> El 2020-06-13 23:18, Jonathan Washington escribió
loud.
--
Jonathan
14 iyn 2020, B. tarixində 13:45 tarixində Francis Tyers
yazdı:
>
> El 2020-06-14 11:51, Hèctor Alòs i Font escribió:
> > Missatge de Francis Tyers del dia dg., 14 de
> > juny 2020 a les 10:32:
> >
> >> El 2020-06-13 23:18, Jonathan Washingt
On Sat, Jun 13, 2020, 16:05 Francis Tyers wrote:
> El 2020-06-13 19:31, Xavi Ivars escribió:
> > Before anything, let me say that I like the proposal to enhance the
> > pipeline with more data (including, but not limited to the surface
> > forms), to be able to do properly do things that
13 iyn 2020, Ş. tarixində 13:15 tarixində yazdı:
>
> Tino Didriksen wrote:
> > 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
> > >
On Sat, Jun 13, 2020, 11:50 Francis Tyers wrote:
> El 2020-06-13 15:20, Tino Didriksen escribió:
> > I would like everyone to read and seriously consider this thread and
> > give your opinion. This meanders a bit, so please read it all.
> >
>
> Here is a non-exhaustive list of potential pitfalls
On Sat, Jun 13, 2020, 10:20 Tino Didriksen wrote:
>
> Yes, inline secondary data is linguistically impure. I recognize this. I
> still think it's worth it, and is the best way to do it.
>
This is the main point against secondary tags that Tino provided. As
someone who cares deeply about
Fran,
Could you restate your objections and concerns for the benefit of this
thread?
--
Jonathan
On Sat, Jun 13, 2020, 10:43 Francis Tyers wrote:
> El 2020-06-13 15:20, Tino Didriksen escribió:
> > I would like everyone to read and seriously consider this thread and
> > give your opinion.
Dear Apertium contributors,
Now that https://beta.apertium.org/ is up, we find that there are a
lot of languages that do not have a "fallback" for most localisations.
By "fallback", I just mean the names of the languages in the languages
themselves. This is what will be seen by most users in
Hi Mansur,
I believe turkic.apertium.org is up to date with Tino's latest
additions to Apertium nightly packaging. Tatar-English also ~works
(to the extent that it's been developed). Tatar-Turkish I do not
believe is an available pair. Is this pair that has received some
RBMT attention?
--
Hi Mansur,
If you're looking to use bleeding-edge Tatar tools from Apertium, you
can also try http://turkic.apertium.org . I just brought it
up-to-date with nightly packaging.
Note that there are a few Turkic modules that haven't made it into
nightly packaging yet, and there are a few issues
29 may 2020, C. tarixində 15:47 tarixində Tino Didriksen
yazdı:
>
> Good question. I don't know.
>
> But going by
> https://github.com/apertium/apertium-all/commit/5764549df9f0d550cdcae56541cc5a1585742b9a
> the updater picks and propagates force-pushes correctly. apertium-ain was
> thoroughly
Hi all,
After having read through and thought some on this thread, I have some
responses.
First of all, I don't care what the "default" is (i.e., whatever
apertium-init creates without flags), as long as there remains choice. A
lot of pairs already have things set up in different ways, and I
On Tue, May 26, 2020, 08:48 Francis Tyers wrote:
> El 2020-05-26 12:27, Kevin Brubeck Unhammer escribió:
> > Xavi Ivars čálii:
> >
> >> * In the trimming disadvantages number 1, we're stating that we're OK
> >> having crappy monodixes because we *fix* that later on with trimming.
> >> I'm
> >>
Speaking as a language developer,¹ I prefer concise, textual tags.
E.g., I don't think is good—it clogs the stream
with verbosity, as Fran points out.
On the other hand, I don't mind symbols here and there, like <§agent>.
But I don't think this is a good secondary tag, unless we make it very
If you don't like the diff that GitHub offers, you can clone the repos and
use whatever diff tool you prefer. The git executable itself has several
diff modes too, including a word diff (which sounds like what you're
after?).
--
Jonathan
On Wed, Apr 22, 2020, 01:14 Tino Didriksen wrote:
> On
the US Constitution.
>
> On Tue, Apr 21, 2020, 08:56 Jonathan Washington <
> jonathan.n.washing...@gmail.com> wrote:
>
>>
>>
>> On Mon, Apr 20, 2020, 17:57 Samuel Sloniker
>> wrote:
>>
>>> 1. I oppose allowing the Secretary and T
Btw, dpkg -L shows the following on my Debian system:
/usr/share/apertium/apertium-swe/apertium-swe.swe.dix
It could probably work for what you want.
--
Jonathan
On Tue, Apr 21, 2020, 12:29 Jonathan Washington <
jonathan.n.washing...@gmail.com> wrote:
> Hi Per,
>
> To add to w
Hi Per,
To add to what Daniel said, language data installed from apt is put in
system directories as root, and is not good for doing dev work.
As a fairly up-to-date Apertium language data developer, I don't know the
path of system-installed language data off the top of my head (you can
always
The main thing I worry about here is lrx rules.
Currently a lot of pairs have rules that match e.g. tags="adj", but not
necessarily tags="adj.*". So something that's normally hargle might
now be hargle, and that means the lrx rule won't match.
Since we want this to be backwards-compatible
On Mon, Apr 20, 2020, 17:57 Samuel Sloniker wrote:
> 1. I oppose allowing the Secretary and Treasurer to be the same person.
>
What's your reasoning for this?
--
Jonathan
2. Using additional criteria for tiebreaking could easily turn into a
> rigged election.
> 3. I believe there should be a
I believe the multitrans script in lex-tools (
https://github.com/apertium/apertium-lex-tools) makes it possible to get
all versions of the translation by expanding the dictionary and skipping
lexical selection. So you'd get two sentences output for this particular
example:
- The season is more
tarixində Samuel Sloniker
yazdı:
>
> I added some more pros as well as a few cons.
> http://wiki.apertium.org/wiki/PMC_proposals/Use_Material_Design#In_detail
>
> On Thu, Apr 9, 2020 at 10:52 AM Jonathan Washington
> wrote:
>>
>> That's not a good reason to choose so
n, it just seems fairly popular.
>
> On Thu, Apr 9, 2020, 10:45 Jonathan Washington
> wrote:
>>
>> Why Material and not some other standard?
>>
>> --
>> Jonathan
>>
>> 8 apr 2020, Ç. tarixində 16:02 tarixində Samuel Sloniker
>> yazdı:
>&
7 apr 2020, Ç.a. tarixində 05:44 tarixində Tino Didriksen <
m...@tinodidriksen.com> yazdı:
> Well, that makes sense from a security point of view. And that is a good
> reason to revive the native port, which I talked about on IRC but never
> wrote about to the mailing list.
>
> IRC logs:
>
>
Why Material and not some other standard?
--
Jonathan
8 apr 2020, Ç. tarixində 16:02 tarixində Samuel Sloniker
yazdı:
>
> (for the next PMC)
> http://wiki.apertium.org/wiki/PMC_proposals/Use_Material_Design
> ___
> Apertium-stuff mailing list
>
> - Sushain K. Cherivirala
> - Tino Didriksen
> - Mikel L. Forcada
> - Xavi Ivars
> - Tanmai Khanna*
> - Jonathan Washington
>
> * Due to participation in GSoC, Tanmai Khanna's appointment will be delayed.
No one has been selected for GSoC yet (we're in the mentor selection
stag
Not everywhere observes the same days as the U.S. Different areas and
peoples have their own traditions, just like they have their own languages.
https://en.wikipedia.org/wiki/Massacre_of_the_Innocents#Feast_day
--
Jonathan
On Thu, Apr 2, 2020, 11:59 Scoop Gracie wrote:
> Huh?
>
> On Thu,
um elections coming up.
> > Pièce(s) jointes(s) probable(s)>
> >
> > So far, these people have indicated they want to run for PMC members:
> > - Jonathan Washington
> > - Francis Tyers
> > - Tino Didriksen
> > - Scoop Gracie (pseudonym)
> > - Tanmai Kh
And since
- Tino's running for president, and
- taking a census like this is technically the election committee's
responsibility (I believe),
The election committee should probably verify Tino's work.
--
Jonathan
пт, 6 мар. 2020 г. в 07:05, Tino Didriksen :
> Combined list of everyone I can
Hi Himanshu,
Apertium generally isn't looking for "some developer" to write MT systems.
The community is usually looking for people who know a language and care
about it.
Also, there are over 150 million speakers of those languages combined, so
I'm not sure how rare it is to find developers who
I just invited you to have write access to the Apertium phenny repo :)
This is an important discussion, and one that's come up before, but it
won't be resolved in time for the election. So, for now, the easiest
work-around is to make sure everyone who thinks and who other
contributors think
> […]
> Giving access rights to new Committers.
>
> Cheers
>
> Mikel
>
>
> El 26/2/20 a les 17:22, Jonathan Washington ha escrit:
>
> That's a good start for a discussion about revising committer status in
> the bylaws, and maybe for use of a definition for the electio
That's a good start for a discussion about revising committer status in the
bylaws, and maybe for use of a definition for the election, but it also
raises a few questions:
- How do we decide who's a member of the GitHub org?
- How do we decide who has write access to an Apertium repo?
These are
lementations for Japanese.
>
> --
> Tomohiro
>
> 2020年2月26日(水) 22:26 Jonathan Washington :
>
>> Hi Tommi, all,
>>
>> A couple years ago, a Swarthmore student implemented an algorithm for
>> tokenisation of spaceless orthographies using morphological t
Thanks for calling the election, Mikel. It was pointed out on IRC during
GCI that it was time to run an election again, but everyone was busy with
GCI so it didn't receive more attention.
+1 to Tino's points.
I'll be running for PMC again, so I'll recuse myself from involvement with
the
Hi Tommi, all,
A couple years ago, a Swarthmore student implemented an algorithm for
tokenisation of spaceless orthographies using morphological transducers.
She used a fork of a prototype Japanese transducer developed by another of
my students to evaluate it.
The work is available at the
Hi Nadia,
The page is still being edited to be up-to-date.
The anaphora resolution project was completed last year, and will need
to be removed from the ideas page.
This year a related project idea might be to integrate anaphora
resolution into several Apertium translation pairs. Another
Hi Mohit,
As with all GSoC projects, the best way to show your interest in the
project and your ability to complete it is to start working on it. In
this case, this would mean starting by tackling a few open issues in
apertium-html-tools
(https://github.com/apertium/apertium-html-tools/issues)
w translation pair of Pahari
> language with other languages. I believe that my work will be beneficial for
> the society and also for the future developments.
> Looking forward for precious feedbacks.
>
> Thanks and regards,
> Arzoo
>
> On Fri, Feb 21, 2020 at 1:48 AM Jon
Other places to check are here:
http://wiki.apertium.org/wiki/Contributing
and here:
http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code
, the latter of which needs some updates.
--
Jonathan
чт, 20 февр. 2020 г. в 14:52, Sevilay Bayatlı :
>
> Hi Arzoo,
>
> Welcome to Apertium, you
at 12:35 PM Tommi A Pirinen
> wrote:
>>
>> On Tue, Feb 04, 2020 at 01:51:38PM -0500, Jonathan Washington wrote:
>>
>> > Everyone else interested in mentoring, please let me know.
>>
>> I can co-mentor this year again but with very randomly varying
recognise
them under a different name or username.
--
Jonathan
вт, 4 февр. 2020 г. в 15:00, James sandy :
>
> Hello Jonathan,
>
> I’m interested to mentor for Gsoc this year with Apertium
>
> On Tuesday, February 4, 2020, Jonathan Washington
> wrote:
>>
>> Hi all,
Hi all,
Thanks to those of you who have offered to help with GSoC.
Everyone else interested in mentoring, please let me know.
Also note the following draft of information for the application:
wiki.apertium.org/wiki/Google_Summer_of_Code/Application_2020
--
Jonathan
пн, 3 февр. 2020 г. в
I've been eyeing the deadline, and it's been on my to-do list to bring
it up. But I've also been busy with other things and kind of waiting
for the last of the GCI admin stuff to be out of the way.
In any case, I'm willing to be an org admin for GSoC—it's a little bit
lower pressure than for GCI
Hi Zanga,
I believe you're running into a know issue with the tagger as apertium-init
sets it up:
https://github.com/apertium/apertium-init/issues/31
The fix is to add -x to the apertium-tagger lines in your bilingual
modes.xml. A work-around is to just remove the apertium-tagger blocks
Hi Sakine,
If I understand right, you'd like to use a web interface to analyse some
Kurmancî data?
If so, you can try this:
https://beta.apertium.org/?choice=kmr#analyzation
If that's not what you're after, could you clarify?
--
Jonathan
On Thu, Dec 19, 2019, 19:31 Sakine Cabuk Balli
wrote:
.
--
Jonathan
вт, 26 нояб. 2019 г. в 08:26, Jonathan Washington
:
>
> I can take care of it in an hour or two. Thanks for the reminder, Ilnar, and
> for the organisational help, Sevilay!
>
> --
> Jonathan
>
> On Tue, Nov 26, 2019, 06:59 Sevilay Bayatlı wrote:
>&g
to submit a title, list of authors, and
> a short description.
>
> Sevilay
>
>
> On Wed, Nov 20, 2019 at 8:05 PM Jonathan Washington <
> jonathan.n.washing...@gmail.com> wrote:
>
>> Hi all,
>>
>> This is just a reminder that the expression
deadline: 25 Feb 2020.
GUEST EDITORS (Listed alphabetically)
• Alina Karakanta (FBK-Fondazione Bruno Kessler)
• Audrey N. Tong (NIST)
• Chao-Hong Liu (ADAPT Centre/Dublin City University)
• Ian Soboroff (NIST)
• Jonathan Washington (Swarthmore College)
• Oleg Aulov (NIST)
• Xiaobing Zhao (Minzu
to submit, then please get in touch.
--
Jonathan
пт, 1 нояб. 2019 г. в 22:21, Jonathan Washington
:
>
> Hi all,
>
> Below please find a revised CFP for the Machine Translation Special
> Issue on MT for Low-Resource Languages.
>
> =
> CALL FOR PAPERS: Machine Translation
Hi Kiran,
Did you try the modes fix that Tino suggested? What are the contents of
your modes.xml file?
--
Jonathan
On Mon, Nov 11, 2019, 21:45 kiran srigiri wrote:
> Not working !
>
> -Kiran srigiri
>
> On Thu, 7 Nov 2019, 22:41 Ngadou Yopa, wrote:
>
>> Hey Srigiri
>>
>> Try this `echo
e.com/archive/2018/task/6465621755691008/
>>
>>
>> On Thu, 7 Nov 2019, 07:21 Jonathan Washington,
>> wrote:
>>>
>>> Hi Kiran,
>>>
>>> A number of us on this list have mentored GSoC before. What's the
>>> question? Feel free to
Hi Kiran,
A number of us on this list have mentored GSoC before. What's the
question? Feel free to ask on #apertium as well.
--
Jonathan
вт, 5 нояб. 2019 г. в 07:39, kiran srigiri :
>
> Any Google summer of code - Gsoc mentor I can talk with?
> ___
> The same with the block diagram.
>>
>> Mikel
>>
>>
>> El 5/11/19 a les 16:53, Jonathan Washington ha escrit:
>> > Hi Mikel,
>> >
>> > I've been thinking recently that we also should put the Apertium SVG
>> > logo i
Hi Mikel,
I've been thinking recently that we also should put the Apertium SVG
logo in the repos somewhere. I wonder if this sort of thing should be
grouped together (maybe in a "promotional materials" repo?) or
separately.
What do other people familiar with Apertium's GitHub organisation
Hi Nebojsa,
First of all, my apologies for not being able to respond in Norwegian. I
would definitely have preferred to.
One reason other languages would be greyed out is because Apertium has a
limited number of released language pairs with English.
To use unreleased translation pairs, you can
Hi Kiran,
Try python3?
--
Jonathan
On Sat, Nov 2, 2019, 21:45 kiran srigiri wrote:
> $~/Desktop/apertium eng-hau prototype$ python apertium-init.py eng-hau
> File "apertium-init.py", line 34
> SyntaxError: Non-ASCII character '\xca' in file apertium-init.py on line
> 34, but no encoding
EDITORS (Listed alphabetically)
• Alina Karakanta (FBK-Fondazione Bruno Kessler)
• Audrey N. Tong (NIST)
• Chao-Hong Liu (ADAPT Centre/Dublin City University)
• Ian Soboroff (NIST)
• Jonathan Washington (Swarthmore College)
• Oleg Aulov (NIST)
• Xiaobing Zhao (Minzu University of China)
Machine
Greetings, Apertiumers!
Our application for Google Code-In is due on Monday (the 28th). If
you'd like to be a mentor, please do the following before then:
1. Add your name to tasks that you can mentor at the Task Ideas page:
http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in
2. If
On Tue, Sep 17, 2019, 14:58 Kevin Brubeck Unhammer
wrote:
>
> The upside is that you can combine words without listing everything
> twice. If you've only got one prefix, the HFST-like method is probably
> better. If you're combining lots, compounding may be worth considering.
>
We can and do
Thanks, Kevin. Yes, that's the approach I use. It's not well-documented,
but it's pretty straightforward.
Do you know anything about the metalrx.py script that Tino mentioned?
--
Jonathan
On Thu, Sep 12, 2019, 13:47 Kevin Brubeck Unhammer
wrote:
> Jonathan Washington
> čálii:
>
I'm curious about metalrx.py. Where is it used? What does it do? Is it
documented anywhere? I've been using an xslt file I found in a Sámi pair
for creating lrx from metalrx.
--
Jonathan
On Thu, Sep 12, 2019, 02:19 Tino Didriksen wrote:
> Maybe I can do it myself, then. 2to3 did most of
Hi Zanga,
Normally we don't use HFST transducers (.hfst) in bilingual modules. Is
there a reason you'd like to use it instead of lttoolbox transducers (.bin)?
If you do want to use it in place of the lttoolbox transducer, as Fran
suggests, Makefile.am is definitely where you'd want to specify
m-pt-ca. So I'll add now the
> old AUTHORS information to the new package.
>
> Hèctor
>
> Missatge de Jonathan Washington del dia
> dj., 29 d’ag. 2019 a les 5:59:
>
>> Hi Hèctor,
>>
>> Do I understand that apertium-por-cat is not a continuation of the code
Hi Hèctor,
Do I understand that apertium-por-cat is not a continuation of the code
from apertium-pt-ca?
I would have expected that the code is a continuation (or branch) of the
old repo. If this were the case, pushing the new code to the
apertium-pt-ca repo and renaming it to apertium-por-cat
Hi Andi,
The main requirement on our side for being a mentor is that you've
contributed before and you're capable of mentoring some subset of tasks.
So there should be no problem :)
Of course this is all contingent on Apertium being accepted this year. If
we're accepted, we'll reach out and
Hi everyone,
The recursive transfer GSoC project is progressing nicely, and it's
anticipated that a release will occur at the end of GSoC. It's very
exciting!
We'd like to add debug mode support to Apertium for recursive transfer, via
the following file:
ode:
>
> var languages = {'af': 'Afrikaans',...
>
> and then you link it to the three-letter one
>
> var iso639Codes = {'afr': 'af',...
>
> I don't know about the others but I've got a pol-szl pair, so I have to do
> it like that. :)
>
> Greg
>
> We niydzie
Shouldn't it work without needing a two-letter code?
--
Jonathan
On Sun, Jul 21, 2019, 09:58 Grzegorz Kulik wrote:
> Hi Sushain,
>
> thank you for your answer, it pointed me in the right direction. Turns out
> Silesian wasn't defined at all in localization.js or in min.js. In 'var
> languages'
Oi Hèctor,
Nós concordamos que as formas anteriores ao AO devem continuar a ser
analisadas pelo analisador.
A escolha entre as duas opções depende de como os falantes de Portugal se
sentem sobre a ortografia pré-AO. Se muitas pessoas ainda antecipam as
formas antigas, faria sentido manter
Hi all,
I understand that -z was added to a number of Apertium and Apertium-related
programs, allowing them to continue to accept input and simply flush
buffers when a null character is encountered.
Question 1. Is it right that Apertium itself does not follow this
behaviour? To use an existing
1 - 100 of 136 matches
Mail list logo
