Re: [Apertium-stuff] Proposal: A Research in Semantic Domains and Arabic Collocations

[Sevilay Bayatlı]

Hi Anas,

I am happy to help you, I am a native Arabic speaker and also working as an
academic.  Let me know more about your work.

Sevilay

On Sat, Jan 29, 2022 at 3:16 PM  wrote:

> Dear sirs,
>
> I'm interested in submitting a doctoral thesis in semantic domains, and
> Arabic collocations, hoping to be a contribution to Apertium project.
>
> I'm looking for an Apertium developer in an academic context that would
> be in a position to be able to supervise my work.
>
> Maybe it's recommended also to be a native Arabic speaker, to evaluate
> the Arabic collocations sub project.
>
> Best regards.
>
> — Anas R.
>
> https://richstyle.org/
>
>
> ___
> 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] Proposal: A Research in Semantic Domains and Arabic Collocations

[anas]

Dear sirs,

I'm interested in submitting a doctoral thesis in semantic domains, and 
Arabic collocations, hoping to be a contribution to Apertium project.


I'm looking for an Apertium developer in an academic context that would 
be in a position to be able to supervise my work.


Maybe it's recommended also to be a native Arabic speaker, to evaluate 
the Arabic collocations sub project.


Best regards.

— Anas R.

https://richstyle.org/


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

Re: [Apertium-stuff] Proposal for Torwali-Urdu translation pair

[Naeemuddin Hadi]

Thanks, I'll check'em out.

On Fri, Apr 5, 2019, 7:05 PM Memduh Gökırmak  wrote:

> Hi Naeem,
>
> A few points that come to mind are:
>
> 1) We need 90% coverage or above for release quality.
>
> 2) We have an Urdu analyzer but not a Torwali one, so you will have to
> develop a Torwali analyzer.
>
> 3) Can Inam or someone else provide a structured file of Torwali-Urdu
> words?
>
> 4) Do we have Torwali-language texts to work with? Newspaper articles?
> Quran or Bible translations?
>
> Memduh
> On 5.04.2019 15:47, Naeemuddin Hadi wrote:
>
> Hi all,
>
> I have just completed my proposal
>  for Torwali-Urdu
> translation pair.
> looking for your feedback.
>
> thanks,
> Naeem Uddin
>
>
> ___
> Apertium-stuff mailing 
> listApertium-stuff@lists.sourceforge.nethttps://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] Proposal for Torwali-Urdu translation pair

[Memduh Gökırmak]

Hi Naeem,

A few points that come to mind are:

1) We need 90% coverage or above for release quality.

2) We have an Urdu analyzer but not a Torwali one, so you will have to 
develop a Torwali analyzer.


3) Can Inam or someone else provide a structured file of Torwali-Urdu words?

4) Do we have Torwali-language texts to work with? Newspaper articles? 
Quran or Bible translations?


Memduh

On 5.04.2019 15:47, Naeemuddin Hadi wrote:

Hi all,

I have just completed my proposal 
 for Torwali-Urdu 
translation pair.

looking for your feedback.

thanks,
Naeem Uddin


___
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] Proposal for Torwali-Urdu translation pair

[Naeemuddin Hadi]

Hi all,

I have just completed my proposal
 for Torwali-Urdu
translation pair.
looking for your feedback.

thanks,
Naeem Uddin
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal

[Ilnar Salimzianov]

via Apertium-stuff wrote:
>     >     > Hi Ilnar, I did not receive any
>     message with a temporary password. Can
>     >     > you please check it one more time?
>     >     Hey Daniyar,
>     >
>     >     Now it should be in your inbox/spam
>     folder.
>     >
>     >     The username is slightly different.
>     >
>     >     Sorry about that.
>     >
>     >     I.
>     >     >
>     >     > username: nariman9119
>     >     >
>     >     > mail: n.dani...@innopolis.ru
>     <mailto:n.dani...@innopolis.ru>
>     <mailto:n.dani...@innopolis.ru
>     <mailto:n.dani...@innopolis.ru>>
>     >     >
>     >     >
>     >   
>     
> 
>     >     > *From:* Ilnar Salimzianov
>     mailto:il...@selimcan.org>
>     >     <mailto:il...@selimcan.org
>     <mailto:il...@selimcan.org>>>
>     >     > *Sent:* Thursday, March 21, 2019
>     9:09:07 PM
>     >     > *To:*
>     apertium-stuff@lists.sourceforge.net
>     <mailto:apertium-stuff@lists.sourceforge.net>
>     >   
>     <mailto:apertium-stuff@lists.sourceforge.net
>     <mailto:apertium-stuff@lists.sourceforge.net>>
>     >     > *Subject:* Re: [Apertium-stuff] Proposal
>     >     >  
>     >     >
>     >     > On 3/21/19 5:15 PM, Mohit Raj wrote:
>     >     > > hi all
>     >     > > could anyone please guide me to
>     create account on Apertium Wiki
>     >     > >
>     >     > Hi Mohit!
>     >     >
>     >     > Which username would you like to
>     have on the wiki?
>     >     >
>     >     > Ilnar (selimcan on IRC)
>     >     > > On Thu, Mar 21, 2019 at 1:13 AM
>     Mohit Raj      <mailto:mohiit...@gmail.com>
>     >     <mailto:mohiit...@gmail.com
>     <mailto:mohiit...@gmail.com>>
>     >     > > <mailto:mohiit...@gmail.com
>     <mailto:mohiit...@gmail.com>
>     <mailto:mohiit...@gmail.com
>     <mailto:mohiit...@gmail.com>>>> wrote:
>     >     > >
>     >     > >     Hi Hector
>     >     > >
>     >     > >     There are many literature and
>     published magzines are
>     >     available and
>     >     > >     Magahi is introduced at higher
>     secondary level as optional
>     >     subject
>     >     > >     in related education board of
>     state.
>     >     > >
>     >     > >     Thanks
>     >     > >
>     >     > >     On Wed, 20 Mar 2019, 21:03
>     Hèctor Alòs i Font,
>     >          <mailto:hectora...@gmail.com>
>     <mailto:hectora...@gmail.com
>     <mailto:hecto

Re: [Apertium-stuff] Proposal

[Mohit Raj]

Hi Hector,
>I haven't completle coding challenge.
>I have read about the tool HFST and lttoolbox, so i plan to use lttoolbox
for analyser.
>To develop analyser i will need to write programme that can split the
surface form of word to required lexical unit(morpheme).
>There are a lot of text data of magahi are available.
>I will tokenize the data then attach post tag and furthermore i will make
the paradigm that will classify the rule, how the word change according to
number, gender, tense or aspect etc.

Thanks

On Wed, Mar 27, 2019 at 12:31 PM Hèctor Alòs i Font 
wrote:

> Hi Mohit,
>
> Some quick questions:
>
> - Did you completed the coding challenge?
> - What do you plan to use for the analyser: HFST or lttoolbox?
> - What kind of programme do you need to write for developing the analyser?
> - What free language resources are available for Magahi?
> -You will need to include some thousands of words (ideally the most
> frequent) and will need to say not only which is their part of speech, but
> also to which paradigm they belong. How will you deal with this?
>
> Best wishes,
> Hèctor
>
>
> El dc., 27 març 2019, 8.34, Mohit Raj  va escriure:
>
>> Hi Jonathan,
>> Here is required URL of my proposal "
>> http://wiki.apertium.org/wiki/User:Mohitraj";
>> Thanks
>> Mohit
>>
>> On Wed, Mar 27, 2019 at 7:55 AM Jonathan Washington <
>> jonathan.n.washing...@gmail.com> wrote:
>>
>>> Hi Mohit,
>>>
>>> Could you give the URL to your application draft on the wiki?  That
>>> would help us mentors a lot :)
>>>
>>> --
>>> Jonathan
>>>
>>> пн, 25 мар. 2019 г. в 16:30, Mohit Raj :
>>>
>>>> hi all
>>>> I have submit my proposal on Morphological analyzer of Magahi
>>>> User name - Mohitraj
>>>> Please give your valuable feedback
>>>> Thanks
>>>>
>>>> On Fri, Mar 22, 2019 at 9:41 AM Mohit Raj  wrote:
>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, 22 Mar 2019, 02:07 shashank tiwari, 
>>>>> wrote:
>>>>>
>>>>>> Thanks :)
>>>>>>
>>>>>> On Fri, Mar 22, 2019 at 2:01 AM Ilnar Salimzianov 
>>>>>> wrote:
>>>>>>
>>>>>>> Done for both.
>>>>>>>
>>>>>>> Ilnar
>>>>>>>
>>>>>>> On 3/21/19 10:11 PM, shashank tiwari wrote:
>>>>>>> > I also need username and password for the wiki. username:picklerick
>>>>>>> >
>>>>>>> > On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov, >>>>>> > <mailto:il...@selimcan.org>> wrote:
>>>>>>> >
>>>>>>> >
>>>>>>> > On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
>>>>>>> > > Hi Ilnar, I did not receive any message with a temporary
>>>>>>> password. Can
>>>>>>> > > you please check it one more time?
>>>>>>> > Hey Daniyar,
>>>>>>> >
>>>>>>> > Now it should be in your inbox/spam folder.
>>>>>>> >
>>>>>>> > The username is slightly different.
>>>>>>> >
>>>>>>> > Sorry about that.
>>>>>>> >
>>>>>>> > I.
>>>>>>> > >
>>>>>>> > > username: nariman9119
>>>>>>> > >
>>>>>>> > > mail: n.dani...@innopolis.ru <mailto:n.dani...@innopolis.ru>
>>>>>>> > >
>>>>>>> > >
>>>>>>> >
>>>>>>> 
>>>>>>> > > *From:* Ilnar Salimzianov >>>>>> > <mailto:il...@selimcan.org>>
>>>>>>> > > *Sent:* Thursday, March 21, 2019 9:09:07 PM
>>>>>>> > > *To:* apertium-stuff@lists.sourceforge.net
>>>>>>> > <mailto:apertium-stuff@lists.sourceforge.net>
>>>>>>> > > *Subject:* Re: [Apertium-stuff] Proposal
>>>>>>> > >
>>>>>>> > >
>>>>>>> > >

Re: [Apertium-stuff] Proposal

[Hèctor Alòs i Font]

Hi Mohit,

Some quick questions:

- Did you completed the coding challenge?
- What do you plan to use for the analyser: HFST or lttoolbox?
- What kind of programme do you need to write for developing the analyser?
- What free language resources are available for Magahi?
-You will need to include some thousands of words (ideally the most
frequent) and will need to say not only which is their part of speech, but
also to which paradigm they belong. How will you deal with this?

Best wishes,
Hèctor


El dc., 27 març 2019, 8.34, Mohit Raj  va escriure:

> Hi Jonathan,
> Here is required URL of my proposal "
> http://wiki.apertium.org/wiki/User:Mohitraj";
> Thanks
> Mohit
>
> On Wed, Mar 27, 2019 at 7:55 AM Jonathan Washington <
> jonathan.n.washing...@gmail.com> wrote:
>
>> Hi Mohit,
>>
>> Could you give the URL to your application draft on the wiki?  That would
>> help us mentors a lot :)
>>
>> --
>> Jonathan
>>
>> пн, 25 мар. 2019 г. в 16:30, Mohit Raj :
>>
>>> hi all
>>> I have submit my proposal on Morphological analyzer of Magahi
>>> User name - Mohitraj
>>> Please give your valuable feedback
>>> Thanks
>>>
>>> On Fri, Mar 22, 2019 at 9:41 AM Mohit Raj  wrote:
>>>
>>>> Thanks
>>>>
>>>> On Fri, 22 Mar 2019, 02:07 shashank tiwari, 
>>>> wrote:
>>>>
>>>>> Thanks :)
>>>>>
>>>>> On Fri, Mar 22, 2019 at 2:01 AM Ilnar Salimzianov 
>>>>> wrote:
>>>>>
>>>>>> Done for both.
>>>>>>
>>>>>> Ilnar
>>>>>>
>>>>>> On 3/21/19 10:11 PM, shashank tiwari wrote:
>>>>>> > I also need username and password for the wiki. username:picklerick
>>>>>> >
>>>>>> > On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov, >>>>> > <mailto:il...@selimcan.org>> wrote:
>>>>>> >
>>>>>> >
>>>>>> > On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
>>>>>> > > Hi Ilnar, I did not receive any message with a temporary
>>>>>> password. Can
>>>>>> > > you please check it one more time?
>>>>>> > Hey Daniyar,
>>>>>> >
>>>>>> > Now it should be in your inbox/spam folder.
>>>>>> >
>>>>>> > The username is slightly different.
>>>>>> >
>>>>>> > Sorry about that.
>>>>>> >
>>>>>> > I.
>>>>>> > >
>>>>>> > > username: nariman9119
>>>>>> > >
>>>>>> > > mail: n.dani...@innopolis.ru <mailto:n.dani...@innopolis.ru>
>>>>>> > >
>>>>>> > >
>>>>>> >
>>>>>> 
>>>>>> > > *From:* Ilnar Salimzianov >>>>> > <mailto:il...@selimcan.org>>
>>>>>> > > *Sent:* Thursday, March 21, 2019 9:09:07 PM
>>>>>> > > *To:* apertium-stuff@lists.sourceforge.net
>>>>>> > <mailto:apertium-stuff@lists.sourceforge.net>
>>>>>> > > *Subject:* Re: [Apertium-stuff] Proposal
>>>>>> > >
>>>>>> > >
>>>>>> > > On 3/21/19 5:15 PM, Mohit Raj wrote:
>>>>>> > > > hi all
>>>>>> > > > could anyone please guide me to create account on Apertium
>>>>>> Wiki
>>>>>> > > >
>>>>>> > > Hi Mohit!
>>>>>> > >
>>>>>> > > Which username would you like to have on the wiki?
>>>>>> > >
>>>>>> > > Ilnar (selimcan on IRC)
>>>>>> > > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj <
>>>>>> mohiit...@gmail.com
>>>>>> > <mailto:mohiit...@gmail.com>
>>>>>> > > > <mailto:mohiit...@gmail.com <mailto:mohiit...@gmail.com>>>
>>>>>> wrote:
>>>>>> > > >
>>>>>> > > > Hi Hector
>>>>>> > 

Re: [Apertium-stuff] Proposal

[Mohit Raj]

Hi Jonathan,
Here is required URL of my proposal "
http://wiki.apertium.org/wiki/User:Mohitraj";
Thanks
Mohit

On Wed, Mar 27, 2019 at 7:55 AM Jonathan Washington <
jonathan.n.washing...@gmail.com> wrote:

> Hi Mohit,
>
> Could you give the URL to your application draft on the wiki?  That would
> help us mentors a lot :)
>
> --
> Jonathan
>
> пн, 25 мар. 2019 г. в 16:30, Mohit Raj :
>
>> hi all
>> I have submit my proposal on Morphological analyzer of Magahi
>> User name - Mohitraj
>> Please give your valuable feedback
>> Thanks
>>
>> On Fri, Mar 22, 2019 at 9:41 AM Mohit Raj  wrote:
>>
>>> Thanks
>>>
>>> On Fri, 22 Mar 2019, 02:07 shashank tiwari, 
>>> wrote:
>>>
>>>> Thanks :)
>>>>
>>>> On Fri, Mar 22, 2019 at 2:01 AM Ilnar Salimzianov 
>>>> wrote:
>>>>
>>>>> Done for both.
>>>>>
>>>>> Ilnar
>>>>>
>>>>> On 3/21/19 10:11 PM, shashank tiwari wrote:
>>>>> > I also need username and password for the wiki. username:picklerick
>>>>> >
>>>>> > On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov, >>>> > <mailto:il...@selimcan.org>> wrote:
>>>>> >
>>>>> >
>>>>> > On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
>>>>> > > Hi Ilnar, I did not receive any message with a temporary
>>>>> password. Can
>>>>> > > you please check it one more time?
>>>>> > Hey Daniyar,
>>>>> >
>>>>> > Now it should be in your inbox/spam folder.
>>>>> >
>>>>> > The username is slightly different.
>>>>> >
>>>>> >     Sorry about that.
>>>>> >
>>>>> > I.
>>>>> > >
>>>>> > > username: nariman9119
>>>>> > >
>>>>> > > mail: n.dani...@innopolis.ru <mailto:n.dani...@innopolis.ru>
>>>>> > >
>>>>> > >
>>>>> >
>>>>> 
>>>>> > > *From:* Ilnar Salimzianov >>>> > <mailto:il...@selimcan.org>>
>>>>> > > *Sent:* Thursday, March 21, 2019 9:09:07 PM
>>>>> > > *To:* apertium-stuff@lists.sourceforge.net
>>>>> > <mailto:apertium-stuff@lists.sourceforge.net>
>>>>> > > *Subject:* Re: [Apertium-stuff] Proposal
>>>>> > >
>>>>> > >
>>>>> > > On 3/21/19 5:15 PM, Mohit Raj wrote:
>>>>> > > > hi all
>>>>> > > > could anyone please guide me to create account on Apertium
>>>>> Wiki
>>>>> > > >
>>>>> > > Hi Mohit!
>>>>> > >
>>>>> > > Which username would you like to have on the wiki?
>>>>> > >
>>>>> > > Ilnar (selimcan on IRC)
>>>>> > > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj <
>>>>> mohiit...@gmail.com
>>>>> > <mailto:mohiit...@gmail.com>
>>>>> > > > <mailto:mohiit...@gmail.com <mailto:mohiit...@gmail.com>>>
>>>>> wrote:
>>>>> > > >
>>>>> > > > Hi Hector
>>>>> > > >
>>>>> > > > There are many literature and published magzines are
>>>>> > available and
>>>>> > > > Magahi is introduced at higher secondary level as
>>>>> optional
>>>>> > subject
>>>>> > > > in related education board of state.
>>>>> > > >
>>>>> > > > Thanks
>>>>> > > >
>>>>> > > > On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,
>>>>> > mailto:hectora...@gmail.com>
>>>>> > > > <mailto:hectora...@gmail.com >>>> hectora...@gmail.com>>>
>>>>> > wrote:
>>>>> > > >
>>>>> > > > Hi Mohit,
>>>>> &g

Re: [Apertium-stuff] Proposal

[Jonathan Washington]

Hi Mohit,

Could you give the URL to your application draft on the wiki?  That would
help us mentors a lot :)

--
Jonathan

пн, 25 мар. 2019 г. в 16:30, Mohit Raj :

> hi all
> I have submit my proposal on Morphological analyzer of Magahi
> User name - Mohitraj
> Please give your valuable feedback
> Thanks
>
> On Fri, Mar 22, 2019 at 9:41 AM Mohit Raj  wrote:
>
>> Thanks
>>
>> On Fri, 22 Mar 2019, 02:07 shashank tiwari, 
>> wrote:
>>
>>> Thanks :)
>>>
>>> On Fri, Mar 22, 2019 at 2:01 AM Ilnar Salimzianov 
>>> wrote:
>>>
>>>> Done for both.
>>>>
>>>> Ilnar
>>>>
>>>> On 3/21/19 10:11 PM, shashank tiwari wrote:
>>>> > I also need username and password for the wiki. username:picklerick
>>>> >
>>>> > On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov, >>> > <mailto:il...@selimcan.org>> wrote:
>>>> >
>>>> >
>>>> > On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
>>>> > > Hi Ilnar, I did not receive any message with a temporary
>>>> password. Can
>>>> > > you please check it one more time?
>>>> > Hey Daniyar,
>>>> >
>>>> > Now it should be in your inbox/spam folder.
>>>> >
>>>> > The username is slightly different.
>>>> >
>>>> > Sorry about that.
>>>> >
>>>> > I.
>>>> > >
>>>> > > username: nariman9119
>>>> > >
>>>> > > mail: n.dani...@innopolis.ru <mailto:n.dani...@innopolis.ru>
>>>> > >
>>>> > >
>>>> >
>>>> 
>>>> > > *From:* Ilnar Salimzianov >>> > <mailto:il...@selimcan.org>>
>>>> > > *Sent:* Thursday, March 21, 2019 9:09:07 PM
>>>> > > *To:* apertium-stuff@lists.sourceforge.net
>>>> > <mailto:apertium-stuff@lists.sourceforge.net>
>>>> > > *Subject:* Re: [Apertium-stuff] Proposal
>>>> > >
>>>> > >
>>>> > > On 3/21/19 5:15 PM, Mohit Raj wrote:
>>>> > > > hi all
>>>> > > > could anyone please guide me to create account on Apertium
>>>> Wiki
>>>> > > >
>>>> > > Hi Mohit!
>>>> > >
>>>> > > Which username would you like to have on the wiki?
>>>> > >
>>>> > > Ilnar (selimcan on IRC)
>>>> > > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj <
>>>> mohiit...@gmail.com
>>>> > <mailto:mohiit...@gmail.com>
>>>> > > > <mailto:mohiit...@gmail.com <mailto:mohiit...@gmail.com>>>
>>>> wrote:
>>>> > > >
>>>> > > > Hi Hector
>>>> > > >
>>>> > > > There are many literature and published magzines are
>>>> > available and
>>>> > > > Magahi is introduced at higher secondary level as optional
>>>> > subject
>>>> > > > in related education board of state.
>>>> > > >
>>>> > > > Thanks
>>>> > > >
>>>> > > > On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,
>>>> > mailto:hectora...@gmail.com>
>>>> > > > <mailto:hectora...@gmail.com <mailto:hectora...@gmail.com
>>>> >>>
>>>> > wrote:
>>>> > > >
>>>> > > > Hi Mohit,
>>>> > > > Magahi seems an excellent choice for Apertium, as an
>>>> > > > under-resourced language, but I wonder only about how
>>>> > much is
>>>> > > > it standardised. Could you clarify?
>>>> > > > Hèctor
>>>> > > >
>>>> > > >
>>>> > > > El dc., 20 març 2019, 17.20, Mohit Raj
>>>> > mailto:mohiit...@gmail.com>
>>>> > > > <mailto

Re: [Apertium-stuff] Proposal

[Mohit Raj]

hi all
I have submit my proposal on Morphological analyzer of Magahi
User name - Mohitraj
Please give your valuable feedback
Thanks

On Fri, Mar 22, 2019 at 9:41 AM Mohit Raj  wrote:

> Thanks
>
> On Fri, 22 Mar 2019, 02:07 shashank tiwari, 
> wrote:
>
>> Thanks :)
>>
>> On Fri, Mar 22, 2019 at 2:01 AM Ilnar Salimzianov 
>> wrote:
>>
>>> Done for both.
>>>
>>> Ilnar
>>>
>>> On 3/21/19 10:11 PM, shashank tiwari wrote:
>>> > I also need username and password for the wiki. username:picklerick
>>> >
>>> > On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov, >> > <mailto:il...@selimcan.org>> wrote:
>>> >
>>> >
>>> > On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
>>> > > Hi Ilnar, I did not receive any message with a temporary
>>> password. Can
>>> > > you please check it one more time?
>>> > Hey Daniyar,
>>> >
>>> > Now it should be in your inbox/spam folder.
>>> >
>>> > The username is slightly different.
>>> >
>>> > Sorry about that.
>>> >
>>> > I.
>>> > >
>>> > > username: nariman9119
>>> > >
>>> > > mail: n.dani...@innopolis.ru <mailto:n.dani...@innopolis.ru>
>>> > >
>>> > >
>>> >
>>> 
>>> > > *From:* Ilnar Salimzianov >> > <mailto:il...@selimcan.org>>
>>> > > *Sent:* Thursday, March 21, 2019 9:09:07 PM
>>> > > *To:* apertium-stuff@lists.sourceforge.net
>>> > <mailto:apertium-stuff@lists.sourceforge.net>
>>> > > *Subject:* Re: [Apertium-stuff] Proposal
>>> > >
>>> > >
>>> > > On 3/21/19 5:15 PM, Mohit Raj wrote:
>>> > > > hi all
>>> > > > could anyone please guide me to create account on Apertium Wiki
>>> > > >
>>> > > Hi Mohit!
>>> > >
>>> > > Which username would you like to have on the wiki?
>>> > >
>>> > > Ilnar (selimcan on IRC)
>>> > > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj >> > <mailto:mohiit...@gmail.com>
>>> > > > <mailto:mohiit...@gmail.com <mailto:mohiit...@gmail.com>>>
>>> wrote:
>>> > > >
>>> > > > Hi Hector
>>> > > >
>>> > > > There are many literature and published magzines are
>>> > available and
>>> > > > Magahi is introduced at higher secondary level as optional
>>> > subject
>>> > > > in related education board of state.
>>> > > >
>>> > > > Thanks
>>> > > >
>>> > > > On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,
>>> > mailto:hectora...@gmail.com>
>>> > > > <mailto:hectora...@gmail.com <mailto:hectora...@gmail.com
>>> >>>
>>> > wrote:
>>> > > >
>>> > > > Hi Mohit,
>>> > > > Magahi seems an excellent choice for Apertium, as an
>>> > > > under-resourced language, but I wonder only about how
>>> > much is
>>> > > > it standardised. Could you clarify?
>>> > > > Hèctor
>>> > > >
>>> > > >
>>> > > > El dc., 20 març 2019, 17.20, Mohit Raj
>>> > mailto:mohiit...@gmail.com>
>>> > > > <mailto:mohiit...@gmail.com
>>> > <mailto:mohiit...@gmail.com>>> va escriure:
>>> > > >
>>> > > > Got it
>>> > > >
>>> > > > On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
>>> > > > >> > <mailto:sevilaybaya...@gmail.com> <mailto:sevilaybaya...@gmail.com
>>> > <mailto:sevilaybaya...@gmail.com>>>
>>> > > > wrote:
>>> > > >
>>> > > >   

Re: [Apertium-stuff] Proposal

[Mohit Raj]

Thanks

On Fri, 22 Mar 2019, 02:07 shashank tiwari, 
wrote:

> Thanks :)
>
> On Fri, Mar 22, 2019 at 2:01 AM Ilnar Salimzianov 
> wrote:
>
>> Done for both.
>>
>> Ilnar
>>
>> On 3/21/19 10:11 PM, shashank tiwari wrote:
>> > I also need username and password for the wiki. username:picklerick
>> >
>> > On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov, > > <mailto:il...@selimcan.org>> wrote:
>> >
>> >
>> > On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
>> > > Hi Ilnar, I did not receive any message with a temporary
>> password. Can
>> > > you please check it one more time?
>> > Hey Daniyar,
>> >
>> > Now it should be in your inbox/spam folder.
>> >
>> > The username is slightly different.
>> >
>> > Sorry about that.
>> >
>> > I.
>> > >
>> > > username: nariman9119
>> > >
>> > > mail: n.dani...@innopolis.ru <mailto:n.dani...@innopolis.ru>
>> > >
>> > >
>> >
>> ----
>> > > *From:* Ilnar Salimzianov > > <mailto:il...@selimcan.org>>
>> > > *Sent:* Thursday, March 21, 2019 9:09:07 PM
>> > > *To:* apertium-stuff@lists.sourceforge.net
>> > <mailto:apertium-stuff@lists.sourceforge.net>
>> > > *Subject:* Re: [Apertium-stuff] Proposal
>> > >
>> > >
>> > > On 3/21/19 5:15 PM, Mohit Raj wrote:
>> > > > hi all
>> > > > could anyone please guide me to create account on Apertium Wiki
>> > > >
>> > > Hi Mohit!
>> > >
>> > > Which username would you like to have on the wiki?
>> > >
>> > > Ilnar (selimcan on IRC)
>> > > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj > > <mailto:mohiit...@gmail.com>
>> > > > <mailto:mohiit...@gmail.com <mailto:mohiit...@gmail.com>>>
>> wrote:
>> > > >
>> > > > Hi Hector
>> > > >
>> > > > There are many literature and published magzines are
>> > available and
>> > > > Magahi is introduced at higher secondary level as optional
>> > subject
>> > > > in related education board of state.
>> > > >
>> > > > Thanks
>> > > >
>> > > > On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,
>> > mailto:hectora...@gmail.com>
>> > > > <mailto:hectora...@gmail.com <mailto:hectora...@gmail.com
>> >>>
>> > wrote:
>> > > >
>> > > > Hi Mohit,
>> > > > Magahi seems an excellent choice for Apertium, as an
>> > > > under-resourced language, but I wonder only about how
>> > much is
>> > > > it standardised. Could you clarify?
>> > > > Hèctor
>> > > >
>> > > >
>> > > > El dc., 20 març 2019, 17.20, Mohit Raj
>> > mailto:mohiit...@gmail.com>
>> > > > <mailto:mohiit...@gmail.com
>> > <mailto:mohiit...@gmail.com>>> va escriure:
>> > > >
>> > > > Got it
>> > > >
>> > > > On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
>> > > > > > <mailto:sevilaybaya...@gmail.com> <mailto:sevilaybaya...@gmail.com
>> > <mailto:sevilaybaya...@gmail.com>>>
>> > > > wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > here how to
>> > > >
>> > start
>> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
>> > > > also you have to get Apertium wiki account to
>> > write your
>> > > > proposal.
>> > > >
>> > > > best,
>> > > >
>> > > > Sevilay
>> > > >
>> > > >
>>

Re: [Apertium-stuff] Proposal

[shashank tiwari]

Thanks :)

On Fri, Mar 22, 2019 at 2:01 AM Ilnar Salimzianov 
wrote:

> Done for both.
>
> Ilnar
>
> On 3/21/19 10:11 PM, shashank tiwari wrote:
> > I also need username and password for the wiki. username:picklerick
> >
> > On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov,  > <mailto:il...@selimcan.org>> wrote:
> >
> >
> > On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
> > > Hi Ilnar, I did not receive any message with a temporary password.
> Can
> > > you please check it one more time?
> > Hey Daniyar,
> >
> > Now it should be in your inbox/spam folder.
> >
> > The username is slightly different.
> >
> > Sorry about that.
> >
> > I.
> > >
> > > username: nariman9119
> > >
> > > mail: n.dani...@innopolis.ru <mailto:n.dani...@innopolis.ru>
> > >
> > >
> >
> 
> > > *From:* Ilnar Salimzianov  >     <mailto:il...@selimcan.org>>
> > > *Sent:* Thursday, March 21, 2019 9:09:07 PM
> > > *To:* apertium-stuff@lists.sourceforge.net
> > <mailto:apertium-stuff@lists.sourceforge.net>
> > > *Subject:* Re: [Apertium-stuff] Proposal
> > >
> > >
> > > On 3/21/19 5:15 PM, Mohit Raj wrote:
> > > > hi all
> > > > could anyone please guide me to create account on Apertium Wiki
> > > >
> > > Hi Mohit!
> > >
> > > Which username would you like to have on the wiki?
> > >
> > > Ilnar (selimcan on IRC)
> > > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj  > <mailto:mohiit...@gmail.com>
> > > > <mailto:mohiit...@gmail.com <mailto:mohiit...@gmail.com>>>
> wrote:
> > > >
> > > > Hi Hector
> > > >
> > > > There are many literature and published magzines are
> > available and
> > > > Magahi is introduced at higher secondary level as optional
> > subject
> > > > in related education board of state.
> > > >
> > > > Thanks
> > > >
> > > > On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,
> > mailto:hectora...@gmail.com>
> > > > <mailto:hectora...@gmail.com <mailto:hectora...@gmail.com>>>
> > wrote:
> > > >
> > > > Hi Mohit,
> > > > Magahi seems an excellent choice for Apertium, as an
> > > > under-resourced language, but I wonder only about how
> > much is
> > > > it standardised. Could you clarify?
> > > > Hèctor
> > > >
> > > >
> > > > El dc., 20 març 2019, 17.20, Mohit Raj
> > mailto:mohiit...@gmail.com>
> > > > <mailto:mohiit...@gmail.com
> > <mailto:mohiit...@gmail.com>>> va escriure:
> > > >
> > > > Got it
> > > >
> > > > On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
> > > >  > <mailto:sevilaybaya...@gmail.com> <mailto:sevilaybaya...@gmail.com
> > <mailto:sevilaybaya...@gmail.com>>>
> > > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > here how to
> > > >
> > start
> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
> > > > also you have to get Apertium wiki account to
> > write your
> > > > proposal.
> > > >
> > > > best,
> > > >
> > > > Sevilay
> > > >
> > > >
> > > > On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj
> > > >  > <mailto:mohiit...@gmail.com> <mailto:mohiit...@gmail.com
> > <mailto:mohiit...@gmail.com>>> wrote:
> > > >
> > > > Hi all,
> > > > Here is my proposal for GSOC.
> > > >
> > > > I am Mohit 

Re: [Apertium-stuff] Proposal

[Ilnar Salimzianov]

Done for both.

Ilnar

On 3/21/19 10:11 PM, shashank tiwari wrote:
> I also need username and password for the wiki. username:picklerick
>
> On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov,  <mailto:il...@selimcan.org>> wrote:
>
>
>     On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
>     > Hi Ilnar, I did not receive any message with a temporary password. Can
>     > you please check it one more time?
>     Hey Daniyar,
>
>     Now it should be in your inbox/spam folder.
>
>     The username is slightly different.
>
>     Sorry about that.
>
>     I.
>     >
>     > username: nariman9119
>     >
>     > mail: n.dani...@innopolis.ru <mailto:n.dani...@innopolis.ru>
>     >
>     >
>     
>     > *From:* Ilnar Salimzianov      <mailto:il...@selimcan.org>>
>     > *Sent:* Thursday, March 21, 2019 9:09:07 PM
>     > *To:* apertium-stuff@lists.sourceforge.net
>     <mailto:apertium-stuff@lists.sourceforge.net>
>     > *Subject:* Re: [Apertium-stuff] Proposal
>     >  
>     >
>     > On 3/21/19 5:15 PM, Mohit Raj wrote:
>     > > hi all
>     > > could anyone please guide me to create account on Apertium Wiki
>     > >
>     > Hi Mohit!
>     >
>     > Which username would you like to have on the wiki?
>     >
>     > Ilnar (selimcan on IRC)
>     > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj      <mailto:mohiit...@gmail.com>
>     > > <mailto:mohiit...@gmail.com <mailto:mohiit...@gmail.com>>> wrote:
>     > >
>     > >     Hi Hector
>     > >
>     > >     There are many literature and published magzines are
>     available and
>     > >     Magahi is introduced at higher secondary level as optional
>     subject
>     > >     in related education board of state.
>     > >
>     > >     Thanks
>     > >
>     > >     On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,
>     mailto:hectora...@gmail.com>
>     > >     <mailto:hectora...@gmail.com <mailto:hectora...@gmail.com>>>
>     wrote:
>     > >
>     > >     Hi Mohit,
>     > >     Magahi seems an excellent choice for Apertium, as an
>     > >     under-resourced language, but I wonder only about how
>     much is
>     > >     it standardised. Could you clarify?
>     > >     Hèctor
>     > >
>     > >
>     > >     El dc., 20 març 2019, 17.20, Mohit Raj
>     mailto:mohiit...@gmail.com>
>     > >     <mailto:mohiit...@gmail.com
>     <mailto:mohiit...@gmail.com>>> va escriure:
>     > >
>     > >     Got it
>     > >
>     > >     On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
>     > >          <mailto:sevilaybaya...@gmail.com> <mailto:sevilaybaya...@gmail.com
>     <mailto:sevilaybaya...@gmail.com>>>
>     > >     wrote:
>     > >
>     > >     Hi,
>     > >
>     > >     here how to
>     > >   
>     start http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
>     > >     also you have to get Apertium wiki account to
>     write your
>     > >     proposal.
>     > >
>     > >     best,
>     > >
>     > >     Sevilay
>     > >
>     > >
>     > >     On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj
>     > >          <mailto:mohiit...@gmail.com> <mailto:mohiit...@gmail.com
>     <mailto:mohiit...@gmail.com>>> wrote:
>     > >
>     > >     Hi all,
>     > >     Here is my proposal for GSOC.
>     > >
>     > >     I am Mohit Raj, doing my post graduation
>     (4^th sem)
>     > >     in linguistics from Dr. B.R. Ambedkar
>     University ,
>     > >     K.M.I, Agra.
>     > >
>     > >
>     > >     My area of interest is Machine Translation and
>     > >     Natural Language Processing. Previously i have
>     > >     completed courses on XML, Python programming,
>     > >     Language Technologies and Machine Translation. I
>     > >     have work

Re: [Apertium-stuff] Proposal

[shashank tiwari]

I also need username and password for the wiki. username:picklerick

On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov,  wrote:

>
> On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
> > Hi Ilnar, I did not receive any message with a temporary password. Can
> > you please check it one more time?
> Hey Daniyar,
>
> Now it should be in your inbox/spam folder.
>
> The username is slightly different.
>
> Sorry about that.
>
> I.
> >
> > username: nariman9119
> >
> > mail: n.dani...@innopolis.ru
> >
> > 
> > *From:* Ilnar Salimzianov 
> > *Sent:* Thursday, March 21, 2019 9:09:07 PM
> > *To:* apertium-stuff@lists.sourceforge.net
> > *Subject:* Re: [Apertium-stuff] Proposal
> >
> >
> > On 3/21/19 5:15 PM, Mohit Raj wrote:
> > > hi all
> > > could anyone please guide me to create account on Apertium Wiki
> > >
> > Hi Mohit!
> >
> > Which username would you like to have on the wiki?
> >
> > Ilnar (selimcan on IRC)
> > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj  > > <mailto:mohiit...@gmail.com>> wrote:
> > >
> > > Hi Hector
> > >
> > > There are many literature and published magzines are available and
> > > Magahi is introduced at higher secondary level as optional subject
> > > in related education board of state.
> > >
> > > Thanks
> > >
> > > On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font, <
> hectora...@gmail.com
> > > <mailto:hectora...@gmail.com>> wrote:
> > >
> > > Hi Mohit,
> > > Magahi seems an excellent choice for Apertium, as an
> > > under-resourced language, but I wonder only about how  much is
> > > it standardised. Could you clarify?
> > > Hèctor
> > >
> > >
> > > El dc., 20 març 2019, 17.20, Mohit Raj  > > <mailto:mohiit...@gmail.com>> va escriure:
> > >
> > > Got it
> > >
> > > On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
> > > mailto:sevilaybaya...@gmail.com
> >>
> > > wrote:
> > >
> > > Hi,
> > >
> > > here how to
> > > start
> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
> > > also you have to get Apertium wiki account to write
> your
> > > proposal.
> > >
> > > best,
> > >
> > > Sevilay
> > >
> > >
> > > On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj
> > > mailto:mohiit...@gmail.com>>
> wrote:
> > >
> > > Hi all,
> > > Here is my proposal for GSOC.
> > >
> > > I am Mohit Raj, doing my post graduation (4^th sem)
> > > in linguistics from Dr. B.R. Ambedkar University ,
> > > K.M.I, Agra.
> > >
> > >
> > > My area of interest is Machine Translation and
> > > Natural Language Processing. Previously i have
> > > completed courses on XML, Python programming,
> > > Language Technologies and Machine Translation. I
> > > have worked towards the development of parser for
> > > Magahi, in collaboration with my classmate Neerav
> > > Mathur, for course projects. I took participation
> in
> > > following workshop :-
> > >
> > >
> > > 1. 9^th IASNLP-2018: IIIT-Hyderabad Advanced School
> > > on Natural Language Processing
> > >
> > > 2. SOIL-Tech: Towards Digital India at JNU, New
> Delhi
> > >
> > > 3. Hands on workshop on Statistical Machine
> > > Translation with Moses at K.M.I, Agra
> > >
> > >
> > > During the Machine Translation Workshop, Atul Kumar
> > > Ojha introduced us Rule Based Machine Translation
> > > system Apertium and in this period he als

Re: [Apertium-stuff] Proposal

[Mohit Raj]

Hi Ilnar

I would like my username be "Mohit Raj"

Thanks


On Fri, 22 Mar 2019, 00:07 Ilnar Salimzianov,  wrote:

>
> On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
> > Hi Ilnar, I did not receive any message with a temporary password. Can
> > you please check it one more time?
> Hey Daniyar,
>
> Now it should be in your inbox/spam folder.
>
> The username is slightly different.
>
> Sorry about that.
>
> I.
> >
> > username: nariman9119
> >
> > mail: n.dani...@innopolis.ru
> >
> > 
> > *From:* Ilnar Salimzianov 
> > *Sent:* Thursday, March 21, 2019 9:09:07 PM
> > *To:* apertium-stuff@lists.sourceforge.net
> > *Subject:* Re: [Apertium-stuff] Proposal
> >
> >
> > On 3/21/19 5:15 PM, Mohit Raj wrote:
> > > hi all
> > > could anyone please guide me to create account on Apertium Wiki
> > >
> > Hi Mohit!
> >
> > Which username would you like to have on the wiki?
> >
> > Ilnar (selimcan on IRC)
> > > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj  > > <mailto:mohiit...@gmail.com>> wrote:
> > >
> > > Hi Hector
> > >
> > > There are many literature and published magzines are available and
> > > Magahi is introduced at higher secondary level as optional subject
> > > in related education board of state.
> > >
> > > Thanks
> > >
> > > On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font, <
> hectora...@gmail.com
> > > <mailto:hectora...@gmail.com>> wrote:
> > >
> > > Hi Mohit,
> > > Magahi seems an excellent choice for Apertium, as an
> > > under-resourced language, but I wonder only about how  much is
> > > it standardised. Could you clarify?
> > > Hèctor
> > >
> > >
> > > El dc., 20 març 2019, 17.20, Mohit Raj  > > <mailto:mohiit...@gmail.com>> va escriure:
> > >
> > > Got it
> > >
> > > On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
> > > mailto:sevilaybaya...@gmail.com
> >>
> > > wrote:
> > >
> > > Hi,
> > >
> > > here how to
> > > start
> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
> > > also you have to get Apertium wiki account to write
> your
> > > proposal.
> > >
> > > best,
> > >
> > > Sevilay
> > >
> > >
> > > On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj
> > > mailto:mohiit...@gmail.com>>
> wrote:
> > >
> > > Hi all,
> > > Here is my proposal for GSOC.
> > >
> > > I am Mohit Raj, doing my post graduation (4^th sem)
> > > in linguistics from Dr. B.R. Ambedkar University ,
> > > K.M.I, Agra.
> > >
> > >
> > > My area of interest is Machine Translation and
> > > Natural Language Processing. Previously i have
> > > completed courses on XML, Python programming,
> > > Language Technologies and Machine Translation. I
> > > have worked towards the development of parser for
> > > Magahi, in collaboration with my classmate Neerav
> > > Mathur, for course projects. I took participation
> in
> > > following workshop :-
> > >
> > >
> > > 1. 9^th IASNLP-2018: IIIT-Hyderabad Advanced School
> > > on Natural Language Processing
> > >
> > > 2. SOIL-Tech: Towards Digital India at JNU, New
> Delhi
> > >
> > > 3. Hands on workshop on Statistical Machine
> > > Translation with Moses at K.M.I, Agra
> > >
> > >
> > > During the Machine Translation Workshop, Atul Kumar
> > > Ojha introduced us Rule Based Machine Translation
> > > system Apertium and in this per

Re: [Apertium-stuff] Proposal

[Ilnar Salimzianov]

On 3/21/19 9:22 PM, Daniyar Nariman via Apertium-stuff wrote:
> Hi Ilnar, I did not receive any message with a temporary password. Can
> you please check it one more time?
Hey Daniyar,

Now it should be in your inbox/spam folder.

The username is slightly different.

Sorry about that.

I.
>
> username: nariman9119
>
> mail: n.dani...@innopolis.ru
>
> 
> *From:* Ilnar Salimzianov 
> *Sent:* Thursday, March 21, 2019 9:09:07 PM
> *To:* apertium-stuff@lists.sourceforge.net
> *Subject:* Re: [Apertium-stuff] Proposal
>  
>
> On 3/21/19 5:15 PM, Mohit Raj wrote:
> > hi all
> > could anyone please guide me to create account on Apertium Wiki
> >
> Hi Mohit!
>
> Which username would you like to have on the wiki?
>
> Ilnar (selimcan on IRC)
> > On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj  > <mailto:mohiit...@gmail.com>> wrote:
> >
> >     Hi Hector
> >
> >     There are many literature and published magzines are available and
> >     Magahi is introduced at higher secondary level as optional subject
> >     in related education board of state.
> >
> >     Thanks
> >
> >     On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,  >     <mailto:hectora...@gmail.com>> wrote:
> >
> >     Hi Mohit,
> >     Magahi seems an excellent choice for Apertium, as an
> >     under-resourced language, but I wonder only about how  much is
> >     it standardised. Could you clarify?
> >     Hèctor
> >
> >
> >     El dc., 20 març 2019, 17.20, Mohit Raj  >     <mailto:mohiit...@gmail.com>> va escriure:
> >
> >     Got it
> >
> >     On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
> >     mailto:sevilaybaya...@gmail.com>>
> >     wrote:
> >
> >     Hi,
> >
> >     here how to
> >     start 
> > http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
> >     also you have to get Apertium wiki account to write your
> >     proposal.
> >
> >     best,
> >
> >     Sevilay
> >
> >
> >     On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj
> >     mailto:mohiit...@gmail.com>> wrote:
> >
> >     Hi all,
> >     Here is my proposal for GSOC.
> >
> >     I am Mohit Raj, doing my post graduation (4^th sem)
> >     in linguistics from Dr. B.R. Ambedkar University ,
> >     K.M.I, Agra.
> >
> >
> >     My area of interest is Machine Translation and
> >     Natural Language Processing. Previously i have
> >     completed courses on XML, Python programming,
> >     Language Technologies and Machine Translation. I
> >     have worked towards the development of parser for
> >     Magahi, in collaboration with my classmate Neerav
> >     Mathur, for course projects. I took participation in
> >     following workshop :-
> >
> >
> >     1. 9^th IASNLP-2018: IIIT-Hyderabad Advanced School
> >     on Natural Language Processing
> >
> >     2. SOIL-Tech: Towards Digital India at JNU, New Delhi
> >
> >     3. Hands on workshop on Statistical Machine
> >     Translation with Moses at K.M.I, Agra
> >
> >
> >     During the Machine Translation Workshop, Atul Kumar
> >     Ojha introduced us Rule Based Machine Translation
> >     system Apertium and in this period he also informed
> >     us about GSOC.
> >
> >
> >     I am interested in working on English-Magahi
> >     language pair for Machine Translation. Magahi
> >     belongs to Indo-Aryan language family and it is alos
> >     my native language. I have been suggested that in
> >     Machine Translation, Morphological Analyzer plays an
> >     important role in improving the system’s performance
> >     for morphologically rich language like Magahi. So I
> >     am interested in developing morph analyzer of Magahi.
> >
> >
> >   

Re: [Apertium-stuff] Proposal

[Daniyar Nariman via Apertium-stuff]

Hi Ilnar, I did not receive any message with a temporary password. Can you 
please check it one more time?

username: nariman9119

mail: n.dani...@innopolis.ru


From: Ilnar Salimzianov 
Sent: Thursday, March 21, 2019 9:09:07 PM
To: apertium-stuff@lists.sourceforge.net
Subject: Re: [Apertium-stuff] Proposal


On 3/21/19 5:15 PM, Mohit Raj wrote:
> hi all
> could anyone please guide me to create account on Apertium Wiki
>
Hi Mohit!

Which username would you like to have on the wiki?

Ilnar (selimcan on IRC)
> On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj  <mailto:mohiit...@gmail.com>> wrote:
>
> Hi Hector
>
> There are many literature and published magzines are available and
> Magahi is introduced at higher secondary level as optional subject
> in related education board of state.
>
> Thanks
>
> On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,  <mailto:hectora...@gmail.com>> wrote:
>
> Hi Mohit,
> Magahi seems an excellent choice for Apertium, as an
> under-resourced language, but I wonder only about how  much is
> it standardised. Could you clarify?
> Hèctor
>
>
> El dc., 20 març 2019, 17.20, Mohit Raj  <mailto:mohiit...@gmail.com>> va escriure:
>
> Got it
>
> On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
> mailto:sevilaybaya...@gmail.com>>
> wrote:
>
> Hi,
>
> here how to
> start 
> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
> also you have to get Apertium wiki account to write your
> proposal.
>
> best,
>
> Sevilay
>
>
> On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj
> mailto:mohiit...@gmail.com>> wrote:
>
> Hi all,
> Here is my proposal for GSOC.
>
> I am Mohit Raj, doing my post graduation (4^th sem)
> in linguistics from Dr. B.R. Ambedkar University ,
> K.M.I, Agra.
>
>
> My area of interest is Machine Translation and
> Natural Language Processing. Previously i have
> completed courses on XML, Python programming,
> Language Technologies and Machine Translation. I
> have worked towards the development of parser for
> Magahi, in collaboration with my classmate Neerav
> Mathur, for course projects. I took participation in
> following workshop :-
>
>
> 1. 9^th IASNLP-2018: IIIT-Hyderabad Advanced School
> on Natural Language Processing
>
> 2. SOIL-Tech: Towards Digital India at JNU, New Delhi
>
> 3. Hands on workshop on Statistical Machine
> Translation with Moses at K.M.I, Agra
>
>
> During the Machine Translation Workshop, Atul Kumar
> Ojha introduced us Rule Based Machine Translation
> system Apertium and in this period he also informed
> us about GSOC.
>
>
> I am interested in working on English-Magahi
> language pair for Machine Translation. Magahi
> belongs to Indo-Aryan language family and it is alos
> my native language. I have been suggested that in
> Machine Translation, Morphological Analyzer plays an
> important role in improving the system’s performance
> for morphologically rich language like Magahi. So I
> am interested in developing morph analyzer of Magahi.
>
>
> So, please give your feedback, Your feedback is
> greatly appreciated.
>
>
> Thanks,
>
>
> Mohit Raj
>
>
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> <mailto:Apertium-stuff@lists.sourceforge.net>
> 
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> <mailto:Apertium-stuff@lists.sourcef

Re: [Apertium-stuff] Proposal

[Ilnar Salimzianov]

On 3/21/19 5:15 PM, Mohit Raj wrote:
> hi all
> could anyone please guide me to create account on Apertium Wiki
>
Hi Mohit!

Which username would you like to have on the wiki?

Ilnar (selimcan on IRC)
> On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj  > wrote:
>
>     Hi Hector
>
>     There are many literature and published magzines are available and
>     Magahi is introduced at higher secondary level as optional subject
>     in related education board of state.
>
>     Thanks
>
>     On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,      > wrote:
>
>     Hi Mohit,
>     Magahi seems an excellent choice for Apertium, as an
>     under-resourced language, but I wonder only about how  much is
>     it standardised. Could you clarify?
>     Hèctor
>
>
>     El dc., 20 març 2019, 17.20, Mohit Raj      > va escriure:
>
>     Got it
>
>     On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı,
>     mailto:sevilaybaya...@gmail.com>>
>     wrote:
>
>     Hi,
>
>     here how to
>     start 
> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
>     also you have to get Apertium wiki account to write your
>     proposal.
>
>     best,
>
>     Sevilay
>
>
>     On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj
>     mailto:mohiit...@gmail.com>> wrote:
>
>     Hi all,
>     Here is my proposal for GSOC.
>
>     I am Mohit Raj, doing my post graduation (4^th sem)
>     in linguistics from Dr. B.R. Ambedkar University ,
>     K.M.I, Agra.
>
>
>     My area of interest is Machine Translation and
>     Natural Language Processing. Previously i have
>     completed courses on XML, Python programming,
>     Language Technologies and Machine Translation. I
>     have worked towards the development of parser for
>     Magahi, in collaboration with my classmate Neerav
>     Mathur, for course projects. I took participation in
>     following workshop :-
>
>
>     1. 9^th IASNLP-2018: IIIT-Hyderabad Advanced School
>     on Natural Language Processing
>
>     2. SOIL-Tech: Towards Digital India at JNU, New Delhi
>
>     3. Hands on workshop on Statistical Machine
>     Translation with Moses at K.M.I, Agra
>
>
>     During the Machine Translation Workshop, Atul Kumar
>     Ojha introduced us Rule Based Machine Translation
>     system Apertium and in this period he also informed
>     us about GSOC.
>
>
>     I am interested in working on English-Magahi
>     language pair for Machine Translation. Magahi
>     belongs to Indo-Aryan language family and it is alos
>     my native language. I have been suggested that in
>     Machine Translation, Morphological Analyzer plays an
>     important role in improving the system’s performance
>     for morphologically rich language like Magahi. So I
>     am interested in developing morph analyzer of Magahi.
>
>
>     So, please give your feedback, Your feedback is
>     greatly appreciated.
>
>
>     Thanks,
>
>
>     Mohit Raj
>
>
>     ___
>     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
>
>     ___
>     Apertium-stuff mailing list
>     Apertium-stuff@lists.sourceforge.net
>     
>     https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
>
>
> ___
> Apertium-stuff mailing list
> Apertium

Re: [Apertium-stuff] Proposal

[Mohit Raj]

hi all
could anyone please guide me to create account on Apertium Wiki

On Thu, Mar 21, 2019 at 1:13 AM Mohit Raj  wrote:

> Hi Hector
>
> There are many literature and published magzines are available and Magahi
> is introduced at higher secondary level as optional subject in related
> education board of state.
>
> Thanks
>
> On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font, 
> wrote:
>
>> Hi Mohit,
>> Magahi seems an excellent choice for Apertium, as an under-resourced
>> language, but I wonder only about how  much is it standardised. Could you
>> clarify?
>> Hèctor
>>
>>
>> El dc., 20 març 2019, 17.20, Mohit Raj  va escriure:
>>
>>> Got it
>>>
>>> On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı, 
>>> wrote:
>>>
 Hi,

 here how to start
 http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
 also you have to get Apertium wiki account to write your proposal.

 best,

 Sevilay


 On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj  wrote:

> Hi all,
> Here is my proposal for GSOC.
>
> I am Mohit Raj, doing my post graduation (4th sem) in linguistics
> from Dr. B.R. Ambedkar University , K.M.I, Agra.
>
>
> My area of interest is Machine Translation and Natural Language
> Processing. Previously i have completed courses on XML, Python 
> programming,
> Language Technologies and Machine Translation. I have worked towards the
> development of parser for Magahi, in collaboration with my classmate 
> Neerav
> Mathur, for course projects. I took participation in following workshop :-
>
>
> 1. 9th IASNLP-2018: IIIT-Hyderabad Advanced School on Natural
> Language Processing
>
> 2. SOIL-Tech: Towards Digital India at JNU, New Delhi
>
> 3. Hands on workshop on Statistical Machine Translation with Moses at
> K.M.I, Agra
>
>
> During the Machine Translation Workshop, Atul Kumar Ojha introduced us
> Rule Based Machine Translation system Apertium and in this period he also
> informed us about GSOC.
>
>
> I am interested in working on English-Magahi language pair for Machine
> Translation. Magahi belongs to Indo-Aryan language family and it is alos 
> my
> native language. I have been suggested that in Machine Translation,
> Morphological Analyzer plays an important role in improving the system’s
> performance for morphologically rich language like Magahi. So I am
> interested in developing morph analyzer of Magahi.
>
>
> So, please give your feedback, Your feedback is greatly appreciated.
>
>
> Thanks,
>
>
> Mohit Raj
>
> ___
> 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
>>>
>> ___
>> 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] Proposal

[Mohit Raj]

Hi Hector

There are many literature and published magzines are available and Magahi
is introduced at higher secondary level as optional subject in related
education board of state.

Thanks

On Wed, 20 Mar 2019, 21:03 Hèctor Alòs i Font,  wrote:

> Hi Mohit,
> Magahi seems an excellent choice for Apertium, as an under-resourced
> language, but I wonder only about how  much is it standardised. Could you
> clarify?
> Hèctor
>
>
> El dc., 20 març 2019, 17.20, Mohit Raj  va escriure:
>
>> Got it
>>
>> On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı, 
>> wrote:
>>
>>> Hi,
>>>
>>> here how to start
>>> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools,
>>> also you have to get Apertium wiki account to write your proposal.
>>>
>>> best,
>>>
>>> Sevilay
>>>
>>>
>>> On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj  wrote:
>>>
 Hi all,
 Here is my proposal for GSOC.

 I am Mohit Raj, doing my post graduation (4th sem) in linguistics from
 Dr. B.R. Ambedkar University , K.M.I, Agra.


 My area of interest is Machine Translation and Natural Language
 Processing. Previously i have completed courses on XML, Python programming,
 Language Technologies and Machine Translation. I have worked towards the
 development of parser for Magahi, in collaboration with my classmate Neerav
 Mathur, for course projects. I took participation in following workshop :-


 1. 9th IASNLP-2018: IIIT-Hyderabad Advanced School on Natural Language
 Processing

 2. SOIL-Tech: Towards Digital India at JNU, New Delhi

 3. Hands on workshop on Statistical Machine Translation with Moses at
 K.M.I, Agra


 During the Machine Translation Workshop, Atul Kumar Ojha introduced us
 Rule Based Machine Translation system Apertium and in this period he also
 informed us about GSOC.


 I am interested in working on English-Magahi language pair for Machine
 Translation. Magahi belongs to Indo-Aryan language family and it is alos my
 native language. I have been suggested that in Machine Translation,
 Morphological Analyzer plays an important role in improving the system’s
 performance for morphologically rich language like Magahi. So I am
 interested in developing morph analyzer of Magahi.


 So, please give your feedback, Your feedback is greatly appreciated.


 Thanks,


 Mohit Raj

 ___
 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
>>
> ___
> 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] Proposal

[Hèctor Alòs i Font]

Hi Mohit,
Magahi seems an excellent choice for Apertium, as an under-resourced
language, but I wonder only about how  much is it standardised. Could you
clarify?
Hèctor


El dc., 20 març 2019, 17.20, Mohit Raj  va escriure:

> Got it
>
> On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı, 
> wrote:
>
>> Hi,
>>
>> here how to start
>> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools, also
>> you have to get Apertium wiki account to write your proposal.
>>
>> best,
>>
>> Sevilay
>>
>>
>> On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj  wrote:
>>
>>> Hi all,
>>> Here is my proposal for GSOC.
>>>
>>> I am Mohit Raj, doing my post graduation (4th sem) in linguistics from
>>> Dr. B.R. Ambedkar University , K.M.I, Agra.
>>>
>>>
>>> My area of interest is Machine Translation and Natural Language
>>> Processing. Previously i have completed courses on XML, Python programming,
>>> Language Technologies and Machine Translation. I have worked towards the
>>> development of parser for Magahi, in collaboration with my classmate Neerav
>>> Mathur, for course projects. I took participation in following workshop :-
>>>
>>>
>>> 1. 9th IASNLP-2018: IIIT-Hyderabad Advanced School on Natural Language
>>> Processing
>>>
>>> 2. SOIL-Tech: Towards Digital India at JNU, New Delhi
>>>
>>> 3. Hands on workshop on Statistical Machine Translation with Moses at
>>> K.M.I, Agra
>>>
>>>
>>> During the Machine Translation Workshop, Atul Kumar Ojha introduced us
>>> Rule Based Machine Translation system Apertium and in this period he also
>>> informed us about GSOC.
>>>
>>>
>>> I am interested in working on English-Magahi language pair for Machine
>>> Translation. Magahi belongs to Indo-Aryan language family and it is alos my
>>> native language. I have been suggested that in Machine Translation,
>>> Morphological Analyzer plays an important role in improving the system’s
>>> performance for morphologically rich language like Magahi. So I am
>>> interested in developing morph analyzer of Magahi.
>>>
>>>
>>> So, please give your feedback, Your feedback is greatly appreciated.
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Mohit Raj
>>>
>>> ___
>>> 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
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal

[Mohit Raj]

Got it

On Wed, 20 Mar 2019, 16:52 Sevilay Bayatlı, 
wrote:

> Hi,
>
> here how to start
> http://wiki.apertium.org/wiki/Getting_started_with_induction_tools, also
> you have to get Apertium wiki account to write your proposal.
>
> best,
>
> Sevilay
>
>
> On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj  wrote:
>
>> Hi all,
>> Here is my proposal for GSOC.
>>
>> I am Mohit Raj, doing my post graduation (4th sem) in linguistics from
>> Dr. B.R. Ambedkar University , K.M.I, Agra.
>>
>>
>> My area of interest is Machine Translation and Natural Language
>> Processing. Previously i have completed courses on XML, Python programming,
>> Language Technologies and Machine Translation. I have worked towards the
>> development of parser for Magahi, in collaboration with my classmate Neerav
>> Mathur, for course projects. I took participation in following workshop :-
>>
>>
>> 1. 9th IASNLP-2018: IIIT-Hyderabad Advanced School on Natural Language
>> Processing
>>
>> 2. SOIL-Tech: Towards Digital India at JNU, New Delhi
>>
>> 3. Hands on workshop on Statistical Machine Translation with Moses at
>> K.M.I, Agra
>>
>>
>> During the Machine Translation Workshop, Atul Kumar Ojha introduced us
>> Rule Based Machine Translation system Apertium and in this period he also
>> informed us about GSOC.
>>
>>
>> I am interested in working on English-Magahi language pair for Machine
>> Translation. Magahi belongs to Indo-Aryan language family and it is alos my
>> native language. I have been suggested that in Machine Translation,
>> Morphological Analyzer plays an important role in improving the system’s
>> performance for morphologically rich language like Magahi. So I am
>> interested in developing morph analyzer of Magahi.
>>
>>
>> So, please give your feedback, Your feedback is greatly appreciated.
>>
>>
>> Thanks,
>>
>>
>> Mohit Raj
>>
>> ___
>> 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] Proposal

[Sevilay Bayatlı]

Hi,

here how to start
http://wiki.apertium.org/wiki/Getting_started_with_induction_tools, also
you have to get Apertium wiki account to write your proposal.

best,

Sevilay


On Wed, Mar 20, 2019 at 12:52 PM Mohit Raj  wrote:

> Hi all,
> Here is my proposal for GSOC.
>
> I am Mohit Raj, doing my post graduation (4th sem) in linguistics from
> Dr. B.R. Ambedkar University , K.M.I, Agra.
>
>
> My area of interest is Machine Translation and Natural Language
> Processing. Previously i have completed courses on XML, Python programming,
> Language Technologies and Machine Translation. I have worked towards the
> development of parser for Magahi, in collaboration with my classmate Neerav
> Mathur, for course projects. I took participation in following workshop :-
>
>
> 1. 9th IASNLP-2018: IIIT-Hyderabad Advanced School on Natural Language
> Processing
>
> 2. SOIL-Tech: Towards Digital India at JNU, New Delhi
>
> 3. Hands on workshop on Statistical Machine Translation with Moses at
> K.M.I, Agra
>
>
> During the Machine Translation Workshop, Atul Kumar Ojha introduced us
> Rule Based Machine Translation system Apertium and in this period he also
> informed us about GSOC.
>
>
> I am interested in working on English-Magahi language pair for Machine
> Translation. Magahi belongs to Indo-Aryan language family and it is alos my
> native language. I have been suggested that in Machine Translation,
> Morphological Analyzer plays an important role in improving the system’s
> performance for morphologically rich language like Magahi. So I am
> interested in developing morph analyzer of Magahi.
>
>
> So, please give your feedback, Your feedback is greatly appreciated.
>
>
> Thanks,
>
>
> Mohit Raj
>
> ___
> 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] Proposal

[Mohit Raj]

Hi all,
Here is my proposal for GSOC.

I am Mohit Raj, doing my post graduation (4th sem) in linguistics from Dr.
B.R. Ambedkar University , K.M.I, Agra.


My area of interest is Machine Translation and Natural Language Processing.
Previously i have completed courses on XML, Python programming, Language
Technologies and Machine Translation. I have worked towards the development
of parser for Magahi, in collaboration with my classmate Neerav Mathur, for
course projects. I took participation in following workshop :-


1. 9th IASNLP-2018: IIIT-Hyderabad Advanced School on Natural Language
Processing

2. SOIL-Tech: Towards Digital India at JNU, New Delhi

3. Hands on workshop on Statistical Machine Translation with Moses at
K.M.I, Agra


During the Machine Translation Workshop, Atul Kumar Ojha introduced us Rule
Based Machine Translation system Apertium and in this period he also
informed us about GSOC.


I am interested in working on English-Magahi language pair for Machine
Translation. Magahi belongs to Indo-Aryan language family and it is alos my
native language. I have been suggested that in Machine Translation,
Morphological Analyzer plays an important role in improving the system’s
performance for morphologically rich language like Magahi. So I am
interested in developing morph analyzer of Magahi.


So, please give your feedback, Your feedback is greatly appreciated.


Thanks,


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

[Apertium-stuff] Proposal for morphological analyzer for Braj Language using the Apertium platform

[neerav mathur]

Hello Sir,

My name is Neerav Mathur. I am 4th semester post graduate student at
K.M.Institute of Hindi and Linguistics, Dr. Bhimrao Ambedkar University
Agra, Uttar Pradesh, India. I am studying Linguistics and during my
pervious semesters I have learnt Python, Machine Translation, XML. As part
of my previous semester course project, I trainer and tested MALT Parser
for Magahi Language. In order to do it, me and my classmate Mohit also
developed a small treebank for the language. In the current semester, we
are further expanding the treebank and we plan to implement the first
full-fledged parser for the language. I am also working on the development
of a machine translation system for English-Magahi language pair. As you
would notice, I am more generally interested in developing resources and
technologies for under-resourced Indian languages. As part of this, I am
interested in building a morphological analyzer for Braj Language (spoken
in Braj Region of Agra, Mathura, Alighar, Bharatpur, etc in Uttar Pradesh
and Rajasthan, India) using the Apertium platform.

I got information about GSOC and Apertium (rule-based platform for MT
and also morph analysers) during hands-on workshop on Machine Translation
by Atul Kumar Ojha, JNU. He suggested me Apertium for developing MT systems
for underresourced language and also suggested how Morphological Analyzers
help in increasing the performance of Machine translation in rule based
system, especially for morphologically rich languages. I want to work on
this project to make morphological analyzer for developing English - Braj
MT system.

I am planning to apply in Google Summer Code this year and work on this
Apertium project. Can you please suggest me if it will be a feasible plan
and if it is possible to complete this project in three months ?

Thank you !

*Neerav Mathur*
*M.A Linguistics *
*Department of Linguistics*
*K.M. Institute of Hindi and Linguistics*
*Dr. Bhim Rao Ambedkar University*

*Agra, Uttar Pradesh, India*
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Sushain Cherivirala]

Hi folks,

I have invited all non-SourceForge emails on record who have committed
to Apertium on SourceForge to the GitHub Apertium organization as members.
Please note that until we really migrate, repository creation is *disabled*.

For some technical reasons, this process needs to be done prior to an
actual migration.
If you are already in the organization and received an invitation, my
apologies.
It's a technical limitation of the platform and I figured it would not
bother too many
people if I did not clean up the list by hand.

If you are a member of Apertium on SF, would like to continue being a member
of Apertium on GitHub and *did not receive the invitation*, send me or any
member
of the PMC your GitHub username and we can add you (probably the former is
simpler).

Thanks for bearing with this necessary step. To reiterate, *no data has
been moved yet*.
*Keep using SF/SVN. *The only difference is that now the GitHub Apertium
organization
has more members.

--
Sushain K. Cherivirala

On Mon, Feb 19, 2018 at 8:32 AM, Sushain Cherivirala 
wrote:

> Hi Hector (and any others who would like to continue using SVN commands),
>
> I've touched on this previously on this list but I think it's quite
> important so I'll mention it again.
>
> GitHub's SVN bridge (which neither GitLab nor Bitbucket have a free
> equivalent for),
> lets you continue using SVN for working with any of the language
> pairs/modules/tools (not
> the GitHub equivalents of /languages, /incubator, /trunk though).
>
> For example:
>
> $ svn co https://github.com/mock-apertium/apertium-cat.git/trunk
> apertium-cat
> Aapertium-cat/.gitattributes
> Aapertium-cat/AUTHORS
> Aapertium-cat/COPYING
> Aapertium-cat/ChangeLog
> Aapertium-cat/Jenkinsfile
> Aapertium-cat/Makefile.am
> [...]
> Checked out revision 598.
> $ cd apertium-cat/
> $ ls
> AUTHORS   Makefile.am   apertium-cat.cat.dix
> apertium-cat.post-cat.dix genvdix.py
> COPYING   NEWS  apertium-cat.cat.rlx
> autogen.shmodes.xml
> ChangeLog READMEapertium-cat.cat.tsx
> cat.prob  texts
> Jenkinsfile   apertium-cat.cat.acx  apertium-cat.pc.in
> configure.ac
> $ echo 'who needs a dictionary' > apertium-cat.cat.dix
> $ svn status
> M   apertium-cat.cat.dix
> $ svn ci -m "We don't need this file"
> Sendingapertium-cat.cat.dix
> Transmitting file data .done
> Committing transaction...
> Committed revision 599.
>
> Tada: https://github.com/mock-apertium/apertium-cat/blob/mas
> ter/apertium-cat.cat.dix
>
> In this light, fully "deprecating" the Using SVN page isn't necessary.
> Just a big warning
> describing the limitation I mentioned above and what's actually happening
> should suffice.
> Specifically, the SVN bridge does not support Git submodules.
>
> Of course, there will also be a Git for SVN users guide, probably
> borrowing something
> someone has already made that works well.
>
> So, your daily workflow does not need to change. You will need a GitHub
> account which
> I hope isn't too much to ask :-)
>
> Happy to answer any further questions.
>
> --
> Sushain K. Cherivirala
>
> On Sun, Feb 18, 2018 at 4:11 AM, Hèctor Alòs i Font 
> wrote:
>
>> 2018-02-16 9:13 GMT+03:00 Francis Tyers :
>>
>>> El 2018-02-14 01:38, Shardul Chiplunkar escribió:
>>>
 Thanks for your comments.

 Felipe, I have tried to respond to your comment on the proposal page.
 Please let us know if you have further questions.

 It seems that making the repository read-only and later deleting it is
 the best option then. As Fran and Xavi said, we would go through the
 wiki pages, READMEs, Virtualbox/Docker configs, etc. to replace
 SourceForge links with GitHub links in the meantime.

 Shardul C.

>>>
>>> Note, this will not just be replacing links, but also commands. It's no
>>> good
>>> replacing a link "svn co http://"; with the github one, and then leave a
>>> "svn commit". The documentation should be updated wholesale as a result of
>>> the move.
>>>
>>> This includes rewriting the contents of the Using_SVN page and
>>> deprecating it.
>>
>>
>> Yes, indeed. As a simple user of svn, and knowing nothing about git, I'll
>> be glad to have a "git for dummies" similar to the  Using_SVN page, so
>> that I'll be able to continue the work with my usual language pairs.
>>
>> Hèctor
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Apertium-stuff mailing list
>> Apertium-stuff@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>>
>>
>
--
Check out the vibrant 

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Sushain Cherivirala]

Hi Hector (and any others who would like to continue using SVN commands),

I've touched on this previously on this list but I think it's quite
important so I'll mention it again.

GitHub's SVN bridge (which neither GitLab nor Bitbucket have a free
equivalent for),
lets you continue using SVN for working with any of the language
pairs/modules/tools (not
the GitHub equivalents of /languages, /incubator, /trunk though).

For example:

$ svn co https://github.com/mock-apertium/apertium-cat.git/trunk
apertium-cat
Aapertium-cat/.gitattributes
Aapertium-cat/AUTHORS
Aapertium-cat/COPYING
Aapertium-cat/ChangeLog
Aapertium-cat/Jenkinsfile
Aapertium-cat/Makefile.am
[...]
Checked out revision 598.
$ cd apertium-cat/
$ ls
AUTHORS   Makefile.am   apertium-cat.cat.dix
  apertium-cat.post-cat.dix genvdix.py
COPYING   NEWS  apertium-cat.cat.rlx
  autogen.shmodes.xml
ChangeLog READMEapertium-cat.cat.tsx
  cat.prob  texts
Jenkinsfile   apertium-cat.cat.acx  apertium-cat.pc.in
  configure.ac
$ echo 'who needs a dictionary' > apertium-cat.cat.dix
$ svn status
M   apertium-cat.cat.dix
$ svn ci -m "We don't need this file"
Sendingapertium-cat.cat.dix
Transmitting file data .done
Committing transaction...
Committed revision 599.

Tada: https://github.com/mock-apertium/apertium-cat/blob/
master/apertium-cat.cat.dix

In this light, fully "deprecating" the Using SVN page isn't necessary. Just
a big warning
describing the limitation I mentioned above and what's actually happening
should suffice.
Specifically, the SVN bridge does not support Git submodules.

Of course, there will also be a Git for SVN users guide, probably borrowing
something
someone has already made that works well.

So, your daily workflow does not need to change. You will need a GitHub
account which
I hope isn't too much to ask :-)

Happy to answer any further questions.

--
Sushain K. Cherivirala

On Sun, Feb 18, 2018 at 4:11 AM, Hèctor Alòs i Font 
wrote:

> 2018-02-16 9:13 GMT+03:00 Francis Tyers :
>
>> El 2018-02-14 01:38, Shardul Chiplunkar escribió:
>>
>>> Thanks for your comments.
>>>
>>> Felipe, I have tried to respond to your comment on the proposal page.
>>> Please let us know if you have further questions.
>>>
>>> It seems that making the repository read-only and later deleting it is
>>> the best option then. As Fran and Xavi said, we would go through the
>>> wiki pages, READMEs, Virtualbox/Docker configs, etc. to replace
>>> SourceForge links with GitHub links in the meantime.
>>>
>>> Shardul C.
>>>
>>
>> Note, this will not just be replacing links, but also commands. It's no
>> good
>> replacing a link "svn co http://"; with the github one, and then leave a
>> "svn commit". The documentation should be updated wholesale as a result of
>> the move.
>>
>> This includes rewriting the contents of the Using_SVN page and
>> deprecating it.
>
>
> Yes, indeed. As a simple user of svn, and knowing nothing about git, I'll
> be glad to have a "git for dummies" similar to the  Using_SVN page, so
> that I'll be able to continue the work with my usual language pairs.
>
> Hèctor
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Hèctor Alòs i Font]

2018-02-16 9:13 GMT+03:00 Francis Tyers :

> El 2018-02-14 01:38, Shardul Chiplunkar escribió:
>
>> Thanks for your comments.
>>
>> Felipe, I have tried to respond to your comment on the proposal page.
>> Please let us know if you have further questions.
>>
>> It seems that making the repository read-only and later deleting it is
>> the best option then. As Fran and Xavi said, we would go through the
>> wiki pages, READMEs, Virtualbox/Docker configs, etc. to replace
>> SourceForge links with GitHub links in the meantime.
>>
>> Shardul C.
>>
>
> Note, this will not just be replacing links, but also commands. It's no
> good
> replacing a link "svn co http://"; with the github one, and then leave a
> "svn commit". The documentation should be updated wholesale as a result of
> the move.
>
> This includes rewriting the contents of the Using_SVN page and deprecating
> it.


Yes, indeed. As a simple user of svn, and knowing nothing about git, I'll
be glad to have a "git for dummies" similar to the  Using_SVN page, so that
I'll be able to continue the work with my usual language pairs.

Hèctor
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Suraj Tamgale]

Hi folks
this is suraj tamgale.
i am second year computer science student.
i would like to work on a project
in Gsoc18.can somebody help me finding an issue so i can start contributing
for apertium.
or i would love to work for the proposal of moving apertium to github.

On Sun, Feb 4, 2018 at 5:33 AM, Shardul Chiplunkar <
shardul.chiplun...@gmail.com> wrote:

> To the President and members of the PMC and Apertium contributors,
>
> There is a new proposal to the PMC to move Apertium to Github:
> http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
>
> Both previous proposals of a similar topic had shortcomings which this
> proposal tries to address.
>
> If you are not a member of the PMC but would like to express your support
> for this proposal, please add your name to the "Non-PMC signatories"
> section at the bottom of the page.
>
> Thank you,
> Shardul C.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Francis Tyers]

El 2018-02-14 01:38, Shardul Chiplunkar escribió:

Thanks for your comments.

Felipe, I have tried to respond to your comment on the proposal page.
Please let us know if you have further questions.

It seems that making the repository read-only and later deleting it is
the best option then. As Fran and Xavi said, we would go through the
wiki pages, READMEs, Virtualbox/Docker configs, etc. to replace
SourceForge links with GitHub links in the meantime.

Shardul C.


Note, this will not just be replacing links, but also commands. It's no 
good
replacing a link "svn co http://"; with the github one, and then leave a 
"svn commit". The documentation should be updated wholesale as a result 
of the move.


This includes rewriting the contents of the Using_SVN page and 
deprecating it.



Fran

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

Thanks for your comments.

Felipe, I have tried to respond to your comment on the proposal page.
Please let us know if you have further questions.

It seems that making the repository read-only and later deleting it is the
best option then. As Fran and Xavi said, we would go through the wiki
pages, READMEs, Virtualbox/Docker configs, etc. to replace SourceForge
links with GitHub links in the meantime.


Shardul C.

On Tue, Feb 13, 2018 at 2:29 AM, Francis Tyers  wrote:

> El 2018-02-13 11:23, Francis Tyers escribió:
>
>> El 2018-02-13 10:40, Xavi Ivars escribió:
>>
>>> 2018-02-13 10:16 GMT+01:00 Francis Tyers :
>>>
>>>
>
 Both of these are horrible. So I propose that we just make it
 read-only for a year and then delete it.

 In the meantime the migration crew (you, Sushain, others) will have
 the responsibility of fixing the ~1000 links on the Wiki so that
 they point to the right place and people don't get 404s or outdated
 links by clicking in the documentation.

>>>
>>> I agree. I would make it read-only for a while (or deleting the
>>> content), adding READMEs in all folders pointing to the new URLs.
>>>
>>>
> Note that there are _far more_ than 7 links to the SVN code on the Wiki.
> I suggest using Google and not the (broken) Wiki search:
>
> https://www.google.ru/search?q=svn.code.sf.net+site%3Awiki.a
> pertium.org&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&dcr
> =0&ei=g72CWobnBMfBsAGP3oagDA
>
>
> Fran
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Francis Tyers]

El 2018-02-13 11:23, Francis Tyers escribió:

El 2018-02-13 10:40, Xavi Ivars escribió:

2018-02-13 10:16 GMT+01:00 Francis Tyers :





Both of these are horrible. So I propose that we just make it
read-only for a year and then delete it.

In the meantime the migration crew (you, Sushain, others) will have
the responsibility of fixing the ~1000 links on the Wiki so that
they point to the right place and people don't get 404s or outdated
links by clicking in the documentation.


I agree. I would make it read-only for a while (or deleting the
content), adding READMEs in all folders pointing to the new URLs.



Note that there are _far more_ than 7 links to the SVN code on the Wiki.
I suggest using Google and not the (broken) Wiki search:

https://www.google.ru/search?q=svn.code.sf.net+site%3Awiki.apertium.org&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&dcr=0&ei=g72CWobnBMfBsAGP3oagDA

Fran

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Francis Tyers]

El 2018-02-13 10:40, Xavi Ivars escribió:

2018-02-13 10:16 GMT+01:00 Francis Tyers :





Both of these are horrible. So I propose that we just make it
read-only for a year and then delete it.

In the meantime the migration crew (you, Sushain, others) will have
the responsibility of fixing the ~1000 links on the Wiki so that
they point to the right place and people don't get 404s or outdated
links by clicking in the documentation.


I agree. I would make it read-only for a while (or deleting the
content), adding READMEs in all folders pointing to the new URLs.


​(P.S. As Apertium has been selected for GSoC this year
(hooray!),
we hope this goes through as soon as possible before March 12.)​


I agree. Basically this goes through now or we have to wait another
six months.


Also, agree :)

I think it's a matter of the PMC to give a clear answer to the
proposal.


There are currently 4 votes in favour and one abstention, so it looks
like this goes through, but we'd really like input from Felipe and
Sergio too.

Fran

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Xavi Ivars]

2018-02-13 10:16 GMT+01:00 Francis Tyers :

>
>>
> Both of these are horrible. So I propose that we just make it read-only
> for a year and then delete it.
>
> In the meantime the migration crew (you, Sushain, others) will have the
> responsibility of fixing the ~1000 links on the Wiki so that they point to
> the right place and people don't get 404s or outdated links by clicking in
> the documentation.


I agree. I would make it read-only for a while (or deleting the content),
adding READMEs in all folders pointing to the new URLs.



>
>
> ​(P.S. As Apertium has been selected for GSoC this year (hooray!),
>> we hope this goes through as soon as possible before March 12.)​
>>
>
> I agree. Basically this goes through now or we have to wait another six
> months.
>

Also, agree :)

I think it's a matter of the PMC to give a clear answer to the proposal.



-- 
< Xavi Ivars >
< http://xavi.ivars.me >
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Francis Tyers]

El 2018-02-13 03:54, Shardul Chiplunkar escribió:

Hi everyone,

We've now written all the scripts required for the migration. The
scripts and documentation are available here:
https://github.com/sushain97/apertium-on-github

The only issue remaining is of backwards compatibility with the
SourceForge repository. Due to the technical details of SVN, we have
two options:

1. Using 'propset': (as an example) When a user checks out the top
directory or the 'incubator' directory from SVN, all the
subdirectories will actually be external pointers to the GitHub SVN
bridges for the corresponding directories, automatically using the
latest code from the GitHub repositories. However, when a user checks
out just the 'apertium-eng' directory from SVN, either the directory
will be empty or it will have yet another subdirectory called
'apertium-eng' pointing to the appropriate GitHub repository,
depending on what we choose to do. It is unfortunately not possible to
directly check out an external pointer in SVN. (Note: if we go with
this option, the HTTP interface at
https://svn.code.sf.net/p/apertium/svn/ would be effectively blank.)

2. If the above option is undesirable, we would simply not have
backwards compatibility and would need a clear, not-easily-missed
message wherever required that the SourceForge repository is not
updated anymore. It could be marked read-only or deleted altogether.


Both of these are horrible. So I propose that we just make it read-only 
for a year and then delete it.


In the meantime the migration crew (you, Sushain, others) will have the 
responsibility of fixing the ~1000 links on the Wiki so that they point 
to the right place and people don't get 404s or outdated links by 
clicking in the documentation.



​(P.S. As Apertium has been selected for GSoC this year (hooray!),
we hope this goes through as soon as possible before March 12.)​


I agree. Basically this goes through now or we have to wait another six 
months.


Fran

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

 Github because of its superior interface. As a recent
> example, you can see
> the interaction between me and Sushain in these two links:
> https://github.com/sushain97/apertium-on-github/issues/7
> https://github.com/sushain97/apertium-on-github/pull/11(click on
> "show outdated")
>
> More benefits/concerns are mentioned on the wiki page and I have also
> replied to your
> comments there. Hope this helps!
>
>
> Shardul C.
>
> On Wed, Feb 7, 2018 at 9:54 AM, Bernard Chardonneau 
> wrote:
>
>> > Date: Sat, 3 Feb 2018 16:03:48 -0800
>> > From: Shardul Chiplunkar 
>> > To: apertium-stuff@lists.sourceforge.net,
>> >  apertium-pmc 
>> > Reply-To: apertium-stuff@lists.sourceforge.net
>> > Subject: [Apertium-stuff] Proposal: Move Apertium to Github
>> > Pièce(s) jointes(s) probable(s)>
>> > To the President and members of the PMC and Apertium contributors,
>> >
>> > There is a new proposal to the PMC to move Apertium to Github:
>> > http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
>> >
>> > Both previous proposals of a similar topic had shortcomings which this
>> > proposal tries to address.
>> >
>> > If you are not a member of the PMC but would like to express your
>> support
>> > for this proposal, please add your name to the "Non-PMC signatories"
>> > section at the bottom of the page.
>> >
>> > Thank you,
>> > Shardul C.
>> >
>>
>> Well, I preferred watching information about git before taking part of
>> this debate.
>>
>> First, your proposal, as previous ones about it includes 2 changes in
>> the same package :
>> 1) leaving sourceforge.net to go to github.com
>> 2) leaving subversion to use git
>>
>> According to what we need, these 2 changes can be examined separately.
>>
>> Do we have a reason to leave sourceforge.net ? (I heard about problems
>> with this provider during the last years). if yes, we can move to another
>> provider supporting subversion.
>>
>> Do we have a reason to leave subversion and to use git instead ?
>> If yes, we can move to git while staying on sourceforge.net .
>>
>> About using git instead of subversion :
>>
>> For downloading the last version of an Apertium tool or a language pair,
>> there is a simple command line both with subversion and git. And this
>> command does not need any password. So this minimal requirement is reached
>> for the two software.
>>
>> I hope sending changes with git will be as simple as a svn commit , but
>> I am really not sure.
>> According what I saw about git, it promotes the creation of different
>> forks where apertium tendency is to use the same reference files in
>> different language pairs.
>>
>> For a 6 months period, there is generally one or two commiters working
>> on a particular language pair + eventually PMC members doing the same
>> changes on any pairs, (but these changes are not on dictionaries or
>> transfer rules), so, this is not a problem if the commiter just create
>> a new reference development version using a svn commit.
>>
>> When apertium project started, the first language pairs included any
>> requested file. And if a new language pair was created, several files
>> of other language pairs like monodices were just copied. After that,
>> each version of a monodix of the same language could evolve separately
>> by adding word inside.
>>
>> After, it was decided to do common file for languages. A good idea, but
>> it seem these reference files were done just by taking the file of one
>> of the possible pair.
>>
>> So, for French, the epo-fra French monodix has a really wider word
>> coverage than the official French monodix. And I also added several
>> words in fra-por pair. I also added RL definitions in paradigms giving
>> mf or sp attributes for analysis. It simplifies transfer and generation.
>>
>> In the future, when it will be time to release one of these pairs,
>> another reference file for French monodix will have to be done including
>> the present reference and the specific adds which are inside epo-fra
>> and fra-por French monodices. (I was asked not to prepare this file
>> from now). And then, language pairs using now the present reference
>> file will have to be tested with the new one to prevent regression.
>> So, after that, my new reference monodix will become the new reference
>> French monodix working with 2 more language pairs.
>>
>> But what would be a trans

Re: [Apertium-stuff] Proposal: Move Apertium to Github (listing a git repository)

[Sushain Cherivirala]

Hi Bernard,

Thanks for your reply.

Indeed, git ls-files is for use with a cloned git repository, i.e. one you
already have
on your filesystem. That is why it did not work:


Not as simple :
> git ls-files https://github.com/hfst/hfst.git
> fatal: Not a git repository (or any parent up to mount point /home)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).


Fortunately, GitHub's SVN bridge which Shardul mentioned previously lets
you do
what you're looking for without learning any new commands:

$ svn ls https://github.com/hfst/hfst.git/trunk
.gitignore
.travis.yml
AUTHORS
BUGS.old
COPYING
ChangeLog
ChangeLog.old
HACKING
INSTALL
Makefile.am
...

You can effectively treat the Git repo as an SVN repo.

--
Sushain K. Cherivirala

On Sat, Feb 10, 2018 at 9:54 AM, Bernard Chardonneau 
wrote:

> > Date: Thu, 8 Feb 2018 00:35:17 +0100
> > From: Xavi Ivars 
> > To: apertium-stuff 
> > Reply-To: apertium-stuff@lists.sourceforge.net
> > Subject: Re: [Apertium-stuff] Proposal: Move Apertium to Github
> > Pièce(s) jointes(s) probable(s)>
> > Hi Bernard
> >
> > I'll try to summarize the answers for your main concerns. If I'm not
> > answering an specific question, please let me know and I'll try to make
> > sure it gets covered.
> >
> > (...)
> >
> > If you want to do a "svn list", you just need to do "git ls-files": you
> get
> > exactly the same output. It has nothing to do with git branch.
>
> Not as simple :
>
> git ls-files https://github.com/hfst/hfst.git
> fatal: Not a git repository (or any parent up to mount point /home)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
>
> > In any case,
> > with git you can do many things that you cant with SVN, like doing
> commits
> > when you have no internet access, etc.
> >
>
> During holidays, I often spend about 2 weeks without internet and I often
> have more time to work on Apertium. My mailer also works mainly off-line.
>
> But sending the results when comming back to internet is enough for me and
> a local git on his computer instead of 2 directories (last original version
> from server and devel directory for changes) is safe enough I thing.
>
> Thank you for your longs answers.
>
>
> 
> Bernard Chardonneau (France)
> Phone : [33] 9 72 36 32 90
> GSM phone : [33] 7 69 46 16 31
>
> Multilingual websites for my free softwares :
> http://libremail.free.fr and http://libremail.tuxfamily.org
> http://cyloop.tuxfamily.org (mainly translated with Apertium)
>
> My general website (in french only)
> http://bech.free.fr
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github (listing a git repository)

[Bernard Chardonneau]

> Date: Thu, 8 Feb 2018 00:35:17 +0100
> From: Xavi Ivars 
> To: apertium-stuff 
> Reply-To: apertium-stuff@lists.sourceforge.net
> Subject: Re: [Apertium-stuff] Proposal: Move Apertium to Github
> Pièce(s) jointes(s) probable(s)>
> Hi Bernard
>
> I'll try to summarize the answers for your main concerns. If I'm not
> answering an specific question, please let me know and I'll try to make
> sure it gets covered.
>
> (...)
>
> If you want to do a "svn list", you just need to do "git ls-files": you get
> exactly the same output. It has nothing to do with git branch.

Not as simple :

git ls-files https://github.com/hfst/hfst.git
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

> In any case,
> with git you can do many things that you cant with SVN, like doing commits
> when you have no internet access, etc.
>

During holidays, I often spend about 2 weeks without internet and I often
have more time to work on Apertium. My mailer also works mainly off-line.

But sending the results when comming back to internet is enough for me and
a local git on his computer instead of 2 directories (last original version
from server and devel directory for changes) is safe enough I thing.

Thank you for your longs answers.



Bernard Chardonneau (France)
Phone : [33] 9 72 36 32 90
GSM phone : [33] 7 69 46 16 31

Multilingual websites for my free softwares :
http://libremail.free.fr and http://libremail.tuxfamily.org
http://cyloop.tuxfamily.org (mainly translated with Apertium)

My general website (in french only)
http://bech.free.fr

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

Hi Bernard,

Xavi has covered a lot of points that you were asking about. I'd just like
to add a few more.

First: Github offers an SVN bridge. This means that if we shift to Github,
developers who
want to continue using SVN can use all the same SVN commands and workflows
as before.
The only difference will be, when running svn checkout, the URL will be
github.com and not
sourceforge.net. After that checkout the developers will not even need to
be aware that they
are using Github, and SVN will work exactly as before.

Second: Here is how pull requests work. (As Xavi mentioned, this is an
optional thing which
may be used by only some packages, but I think it is important.)

1. A group of users called 'apertium' is the owner of all the repositories.
For example, 'apertium/apertium-fra'.

2. Any developer can create a personal copy of any repository, called a
'fork'. The developer
is the owner of the fork but 'apertium' is still the owner of the original
repository.
For example, 'shardulc' creates the fork 'shardulc/apertium-fra'.

3. The developer makes some changes on the fork.
For example, 'shardulc' adds some commits to 'shardulc/apertium-fra'. This
does not change
'apertium/apertium-fra' because it is a separate repository.

4. The developer submits a pull request to the original repository.
Basically, this means the
developer is saying to the original repository, "please look at the changes
I have made and
add them to the original repository". 'apertium/apertium-fra' is still not
changed, but whoever
is in charge of the package is informed that a developer wants to add some
changes.

5. The changes are reviewed. If they are acceptable, they are added, and now
'apertium/apertium-fra' and 'shardulc/apertium-fra' have the same code. If
they are not
acceptable, the reviewer can tell 'shardulc' what he should change and it
goes back to step 3.

Some benefits of using this model:
1. It is very easy to make personal changes to Apertium. To make a fork,
the developer just
needs to click a button on Github. The developer does not even need to be
related to Apertium.
The developer can do whatever they want with the code for personal use and
Apertium's code
will be unchanged.
2. If the developer wants to add the changes to Apertium, there can be pull
requests, and most
importantly, there can be reviews. Of course new developers will not
produce high quality code
all at once, and tips from experienced developers will be very useful; even
experienced
developers can review each other's code (everyone makes mistakes) and this
will improve code
quality.
3. Reviewing pull requests, creating and resolving issues, assigning who
should work on what,
etc. is very easy on Github because of its superior interface. As a recent
example, you can see
the interaction between me and Sushain in these two links:
https://github.com/sushain97/apertium-on-github/issues/7
https://github.com/sushain97/apertium-on-github/pull/11(click on "show
outdated")

More benefits/concerns are mentioned on the wiki page and I have also
replied to your
comments there. Hope this helps!


Shardul C.

On Wed, Feb 7, 2018 at 9:54 AM, Bernard Chardonneau 
wrote:

> > Date: Sat, 3 Feb 2018 16:03:48 -0800
> > From: Shardul Chiplunkar 
> > To: apertium-stuff@lists.sourceforge.net,
> >  apertium-pmc 
> > Reply-To: apertium-stuff@lists.sourceforge.net
> > Subject: [Apertium-stuff] Proposal: Move Apertium to Github
> > Pièce(s) jointes(s) probable(s)>
> > To the President and members of the PMC and Apertium contributors,
> >
> > There is a new proposal to the PMC to move Apertium to Github:
> > http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
> >
> > Both previous proposals of a similar topic had shortcomings which this
> > proposal tries to address.
> >
> > If you are not a member of the PMC but would like to express your support
> > for this proposal, please add your name to the "Non-PMC signatories"
> > section at the bottom of the page.
> >
> > Thank you,
> > Shardul C.
> >
>
> Well, I preferred watching information about git before taking part of
> this debate.
>
> First, your proposal, as previous ones about it includes 2 changes in
> the same package :
> 1) leaving sourceforge.net to go to github.com
> 2) leaving subversion to use git
>
> According to what we need, these 2 changes can be examined separately.
>
> Do we have a reason to leave sourceforge.net ? (I heard about problems
> with this provider during the last years). if yes, we can move to another
> provider supporting subversion.
>
> Do we have a reason to leave subversion and to use git instead ?
> If yes, we ca

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Xavi Ivars]

Hi Bernard

I'll try to summarize the answers for your main concerns. If I'm not
answering an specific question, please let me know and I'll try to make
sure it gets covered.

The proposal is to move both to GitHub and git, for several reasons
explained in the wiki page.

Regarding your concerns with git itself, git allows for more complex
workflows, but that doesn't mean those workflows have to be done. We may
probably want to follow different approaches for tools (where I can easily
foresee people using many branches, creating pull requests,... using
"advanced git") while, at the same time, just using "git commit && git
push" (very similar to "svn commit") for language pairs where there is only
one or two developers. And I'm sure you won't need a month to learn the git
basics. In any case, no need to involve the PMC to review any change
happening on any of the modules.

If you want to do a "svn list", you just need to do "git ls-files": you get
exactly the same output. It has nothing to do with git branch. In any case,
with git you can do many things that you cant with SVN, like doing commits
when you have no internet access, etc.

Regarding the monolingual packages (i.e. apertium-fra) vs old packages with
monolingual dictionaries included, there will be no change: the
current goal is to slowly move to packages with the monolingual data
outside the translation pair, and that won't change when moving to git. At
the same time, there won't be any requirement to "force" anyone the change
the existing language pairs to use monolingual packages because of the
transition to git. There's no implicit disorder/order regarding how we
structure our language pairs that comes with git or SVN. So, everything
will remain the same in this case.

Regarding "official versions", they will be in repositories under the
Apertium organization, so there is no risk of losing any "official" package
because someone changed their email. But it will allow us to handle
permissions in a fine grain mode: some committers may only want/need access
for a specific language, or a set of language pairs, or a set of tools, and
that will be possible to manage. But, again, that's doesn't prevent that
full permissions are given to some committers that need access everywhere
in the code.

And regarding "github" or a different provider, Github has something good:
the community effect. But that doesn't mean that it has to be the "only"
source. In fact, with git is much easier to have multiple repositories than
with SVN, and we may want to have a full copy of all Apertium repositories
in another server (i.e. in apertium.org) to act as a backup, or even change
in the future to a hosted GitLab instance (like framagit, the one you
share).

I hope this helps!

2018-02-07 18:54 GMT+01:00 Bernard Chardonneau :

>
> Well, I preferred watching information about git before taking part of
> this debate.
>
> First, your proposal, as previous ones about it includes 2 changes in
> the same package :
> 1) leaving sourceforge.net to go to github.com
> 2) leaving subversion to use git
>
> According to what we need, these 2 changes can be examined separately.
>
> Do we have a reason to leave sourceforge.net ? (I heard about problems
> with this provider during the last years). if yes, we can move to another
> provider supporting subversion.
>
> Do we have a reason to leave subversion and to use git instead ?
> If yes, we can move to git while staying on sourceforge.net .
>
> About using git instead of subversion :
>
> For downloading the last version of an Apertium tool or a language pair,
> there is a simple command line both with subversion and git. And this
> command does not need any password. So this minimal requirement is reached
> for the two software.
>
> I hope sending changes with git will be as simple as a svn commit , but
> I am really not sure.
> According what I saw about git, it promotes the creation of different
> forks where apertium tendency is to use the same reference files in
> different language pairs.
>
> For a 6 months period, there is generally one or two commiters working
> on a particular language pair + eventually PMC members doing the same
> changes on any pairs, (but these changes are not on dictionaries or
> transfer rules), so, this is not a problem if the commiter just create
> a new reference development version using a svn commit.
>
> When apertium project started, the first language pairs included any
> requested file. And if a new language pair was created, several files
> of other language pairs like monodices were just copied. After that,
> each version of a monodix of the same language could evolve separately
> by adding word inside.
>
> After, it was decided to do common file for languages. A good idea, but
> it seem these reference files were done just by taking the file of one
> of the possible pair.
>
> So, for French, the epo-fra French monodix has a really wider word
> coverage than the official French monodix. And I also

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Bernard Chardonneau]

> Date: Sat, 3 Feb 2018 16:03:48 -0800
> From: Shardul Chiplunkar 
> To: apertium-stuff@lists.sourceforge.net, 
>  apertium-pmc 
> Reply-To: apertium-stuff@lists.sourceforge.net
> Subject: [Apertium-stuff] Proposal: Move Apertium to Github
> Pièce(s) jointes(s) probable(s)>
> To the President and members of the PMC and Apertium contributors,
>
> There is a new proposal to the PMC to move Apertium to Github:
> http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
>
> Both previous proposals of a similar topic had shortcomings which this
> proposal tries to address.
>
> If you are not a member of the PMC but would like to express your support
> for this proposal, please add your name to the "Non-PMC signatories"
> section at the bottom of the page.
>
> Thank you,
> Shardul C.
>

Well, I preferred watching information about git before taking part of
this debate.

First, your proposal, as previous ones about it includes 2 changes in
the same package :
1) leaving sourceforge.net to go to github.com
2) leaving subversion to use git

According to what we need, these 2 changes can be examined separately.

Do we have a reason to leave sourceforge.net ? (I heard about problems
with this provider during the last years). if yes, we can move to another
provider supporting subversion.

Do we have a reason to leave subversion and to use git instead ?
If yes, we can move to git while staying on sourceforge.net .

About using git instead of subversion :

For downloading the last version of an Apertium tool or a language pair,
there is a simple command line both with subversion and git. And this
command does not need any password. So this minimal requirement is reached
for the two software.

I hope sending changes with git will be as simple as a svn commit , but
I am really not sure.
According what I saw about git, it promotes the creation of different
forks where apertium tendency is to use the same reference files in
different language pairs.

For a 6 months period, there is generally one or two commiters working
on a particular language pair + eventually PMC members doing the same
changes on any pairs, (but these changes are not on dictionaries or
transfer rules), so, this is not a problem if the commiter just create
a new reference development version using a svn commit.

When apertium project started, the first language pairs included any
requested file. And if a new language pair was created, several files
of other language pairs like monodices were just copied. After that,
each version of a monodix of the same language could evolve separately
by adding word inside.

After, it was decided to do common file for languages. A good idea, but
it seem these reference files were done just by taking the file of one
of the possible pair.

So, for French, the epo-fra French monodix has a really wider word
coverage than the official French monodix. And I also added several
words in fra-por pair. I also added RL definitions in paradigms giving
mf or sp attributes for analysis. It simplifies transfer and generation.

In the future, when it will be time to release one of these pairs,
another reference file for French monodix will have to be done including
the present reference and the specific adds which are inside epo-fra
and fra-por French monodices. (I was asked not to prepare this file
from now). And then, language pairs using now the present reference
file will have to be tested with the new one to prevent regression.
So, after that, my new reference monodix will become the new reference
French monodix working with 2 more language pairs.

But what would be a transitional step with subversion (2 reference
files) for a as shortest as possible amount of time, could be the
general behavior if we move to git. Git seems to allow very easily
disorder.

About broadcasting a change to the world. You seem to see as a problem
to a student to ask for a commit access that would get valid, if
accepted, for the whole Apertium project.

But how will it work with git ?
If we give to anybody the right to do other official versions without
even been known by anybody of Apertium project, that will be the most
simple way to work for the regular and serious apertium commiters, but
that's not safe.
If we give only this right to chosen Apertium commiters, how will they
be chosen ? I think when somebody creates a new language pair, it's
normal to give him these right for it. But what will happen if several
years after, another person makes changes ? Will it be always possible
to reach the first commiter who may have left Apertium project without
telling it, and who may have even lost his email address if it was a
university email ?

Another possibility would be to ask PMC member to verify the validity
of a change in a pair without even knowing any language of this pair !
That would give a lot of extra work for PMC members actually not needed
with s

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Aboobacker MK]

If the licence of hosting platform is a big concern, then we can host the
code in gitlab and set an autosync with GitHub for the visibility reasons

Personally I don't think it is a big concern since current host sourceforge
isn't open source

On Tuesday, February 6, 2018, Shardul Chiplunkar <
shardul.chiplun...@gmail.com> wrote:

> Hi everyone,
>
> Thanks for your inputs.
>
> Sergio:
>
>> move all the existing user base with minimal impact (how to announce, how
>> to contact
>
> users, how to switch off the old repos, etc.)
>
> This is a very valid concern. We have updated the wiki page for the
> proposal with a brief
> outline of how we would handle this.
>
> Regarding Gitlab, I also believe that it is theoretically superior to
> GitHub (because the
> interface does not use proprietary JS, among other things) but the reason
> for choosing
> GitHub is the visibility of a very popular hosting service, and the ease
> of use for newcomers
> who are often already familiar with GitHub. These and other reasons are
> detailed in the
> proposal.
>
> Tommi:
>
>> all the continuous integrations, continuous deployment and github pages
>> (generated
>>
> from dixes via xslt and bahs hacks!) experimented out a bit
>
> Thanks! We'll surely take a look and see what can be generalized to other
> packages.
>
> Fran: Thanks for pointing out the GSoC schedule. If all goes well, I
> believe March 12
> is not an unreasonable deadline to finish the technical parts of the
> migration.
>
> Thanks,
>
> Shardul C.
>
> On Tue, Feb 6, 2018 at 3:34 AM, Benedikt Freisen 
> wrote:
>
>> Alright.  Thanks for pointing me at it.  I must have scrolled right past
>> that "authors.txt", assuming that it was the AUTHORS file of the
>> repository.
>>
>> My suggestion for added clarity would be:
>> - create an AUTHORS file with your names in it
>> - rename authors.txt to apertium_svn_authors.txt or something like that
>>
>> The ...@users.sourceforge.net addresses do indeed make more sense than
>> pure dummy addresses, since they are at least theoretically valid
>> addresses of the respective authors.
>>
>> Regards
>> Benedikt
>>
>> Am 06.02.2018 um 03:38 schrieb Sushain Cherivirala:
>> > Hi Benedikt,
>> >
>> > Thank you for your reply. You raise a good question regarding the
>> > preservation
>> > of emails in a transition to Git.
>> >
>> > Fortunately, in managing the Apertium packages for various platforms,
>> > Tino has also
>> > has put together a correspondence between SVN users and emails. The
>> import
>> > scripts that I have written use this correspondence. The current version
>> > can be
>> > found here:
>> > https://github.com/sushain97/apertium-on-github/blob/master/authors.txt
>> > > /authors.txt>.
>> >
>> > Here is some documentation for the scripts I mention:
>> > https://github.com/sushain97/apertium-on-github#scripts
>> > .
>> >
>> > If your proper email is missing, you could email Tino and I. If your
>> > email in the file
>> > does not correspond to the email you use from GitHub, it can be changed.
>> > However, it might be easiest to just add the email to your GitHub
>> > account (you
>> > can ensure that it is private). Of course, a repo's authors can always
>> > be modified
>> > after the fact with a re-import or filter-branch operation if necessary.
>> >
>> > I will leave you with an example of what the import script does when
>> used on
>> > apertium-cat: https://github.com/mock-apertium/apertium-cat/
>> graphs/contributors
>> > .
>> >
>> > I am happy to answer any further questions.
>> >
>> > --
>> > Sushain K. Cherivirala
>> >
>> > On Mon, Feb 5, 2018 at 5:06 AM, Benedikt Freisen > > > wrote:
>> >
>> > One not so unimportant issue that I do not see mentioned anywhere is
>> > E-mail addresses.
>> > While svn only maintains a simple user name, git requires user name
>> +
>> > E-mail address.  Tools like git-svn will only create a dummy address
>> > (user@repository-hash or something like that).
>> >
>> > When reactos moved to github in October, a list of svn committer
>> names
>> > plus full (real) names and E-mail addresses was compiled and
>> supplied to
>> > the conversion tool, with more meaningful dummy addresses for
>> previous
>> > committers without a known valid E-mail address.
>> > Apertium could use something like
>> > svnnameofcommitterwhol...@svn.apertium.org
>> >  in that case.
>> >
>> > My suggestion is therefore to scan all AUTHORS files for E-mail
>> > addresses and names corresponding to the respective committers.
>> > This has the additional benefit, that if those authors have a github
>> > account and use the same name+address combination with their github
>> > repositories, gi

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

Hi everyone,

Thanks for your inputs.

Sergio:

> move all the existing user base with minimal impact (how to announce, how
> to contact

users, how to switch off the old repos, etc.)

This is a very valid concern. We have updated the wiki page for the
proposal with a brief
outline of how we would handle this.

Regarding Gitlab, I also believe that it is theoretically superior to
GitHub (because the
interface does not use proprietary JS, among other things) but the reason
for choosing
GitHub is the visibility of a very popular hosting service, and the ease of
use for newcomers
who are often already familiar with GitHub. These and other reasons are
detailed in the
proposal.

Tommi:

> all the continuous integrations, continuous deployment and github pages
> (generated
>
from dixes via xslt and bahs hacks!) experimented out a bit

Thanks! We'll surely take a look and see what can be generalized to other
packages.

Fran: Thanks for pointing out the GSoC schedule. If all goes well, I
believe March 12
is not an unreasonable deadline to finish the technical parts of the
migration.

Thanks,

Shardul C.

On Tue, Feb 6, 2018 at 3:34 AM, Benedikt Freisen  wrote:

> Alright.  Thanks for pointing me at it.  I must have scrolled right past
> that "authors.txt", assuming that it was the AUTHORS file of the
> repository.
>
> My suggestion for added clarity would be:
> - create an AUTHORS file with your names in it
> - rename authors.txt to apertium_svn_authors.txt or something like that
>
> The ...@users.sourceforge.net addresses do indeed make more sense than
> pure dummy addresses, since they are at least theoretically valid
> addresses of the respective authors.
>
> Regards
> Benedikt
>
> Am 06.02.2018 um 03:38 schrieb Sushain Cherivirala:
> > Hi Benedikt,
> >
> > Thank you for your reply. You raise a good question regarding the
> > preservation
> > of emails in a transition to Git.
> >
> > Fortunately, in managing the Apertium packages for various platforms,
> > Tino has also
> > has put together a correspondence between SVN users and emails. The
> import
> > scripts that I have written use this correspondence. The current version
> > can be
> > found here:
> > https://github.com/sushain97/apertium-on-github/blob/master/authors.txt
> >  >.
> >
> > Here is some documentation for the scripts I mention:
> > https://github.com/sushain97/apertium-on-github#scripts
> > .
> >
> > If your proper email is missing, you could email Tino and I. If your
> > email in the file
> > does not correspond to the email you use from GitHub, it can be changed.
> > However, it might be easiest to just add the email to your GitHub
> > account (you
> > can ensure that it is private). Of course, a repo's authors can always
> > be modified
> > after the fact with a re-import or filter-branch operation if necessary.
> >
> > I will leave you with an example of what the import script does when
> used on
> > apertium-cat: https://github.com/mock-apertium/apertium-
> cat/graphs/contributors
> > .
> >
> > I am happy to answer any further questions.
> >
> > --
> > Sushain K. Cherivirala
> >
> > On Mon, Feb 5, 2018 at 5:06 AM, Benedikt Freisen  > > wrote:
> >
> > One not so unimportant issue that I do not see mentioned anywhere is
> > E-mail addresses.
> > While svn only maintains a simple user name, git requires user name +
> > E-mail address.  Tools like git-svn will only create a dummy address
> > (user@repository-hash or something like that).
> >
> > When reactos moved to github in October, a list of svn committer
> names
> > plus full (real) names and E-mail addresses was compiled and
> supplied to
> > the conversion tool, with more meaningful dummy addresses for
> previous
> > committers without a known valid E-mail address.
> > Apertium could use something like
> > svnnameofcommitterwhol...@svn.apertium.org
> >  in that case.
> >
> > My suggestion is therefore to scan all AUTHORS files for E-mail
> > addresses and names corresponding to the respective committers.
> > This has the additional benefit, that if those authors have a github
> > account and use the same name+address combination with their github
> > repositories, github will automatically recognize their commits as
> > theirs.
> >
> > Regards
> > Benedikt
> >
> > Am 04.02.2018 um 01:03 schrieb Shardul Chiplunkar:
> > > To the President and members of the PMC and Apertium contributors,
> > >
> > > There is a new proposal to the PMC to move Apertium to Github:
> > >
> > http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
> >  >

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Benedikt Freisen]

Alright.  Thanks for pointing me at it.  I must have scrolled right past
that "authors.txt", assuming that it was the AUTHORS file of the repository.

My suggestion for added clarity would be:
- create an AUTHORS file with your names in it
- rename authors.txt to apertium_svn_authors.txt or something like that

The ...@users.sourceforge.net addresses do indeed make more sense than
pure dummy addresses, since they are at least theoretically valid
addresses of the respective authors.

Regards
Benedikt

Am 06.02.2018 um 03:38 schrieb Sushain Cherivirala:
> Hi Benedikt,
> 
> Thank you for your reply. You raise a good question regarding the
> preservation
> of emails in a transition to Git.
> 
> Fortunately, in managing the Apertium packages for various platforms,
> Tino has also
> has put together a correspondence between SVN users and emails. The import
> scripts that I have written use this correspondence. The current version
> can be
> found here:
> https://github.com/sushain97/apertium-on-github/blob/master/authors.txt
> .
> 
> Here is some documentation for the scripts I mention:
> https://github.com/sushain97/apertium-on-github#scripts
> .
> 
> If your proper email is missing, you could email Tino and I. If your
> email in the file
> does not correspond to the email you use from GitHub, it can be changed.
> However, it might be easiest to just add the email to your GitHub
> account (you
> can ensure that it is private). Of course, a repo's authors can always
> be modified 
> after the fact with a re-import or filter-branch operation if necessary.
> 
> I will leave you with an example of what the import script does when used on
> apertium-cat: 
> https://github.com/mock-apertium/apertium-cat/graphs/contributors
> .
> 
> I am happy to answer any further questions.
> 
> --
> Sushain K. Cherivirala
> 
> On Mon, Feb 5, 2018 at 5:06 AM, Benedikt Freisen  > wrote:
> 
> One not so unimportant issue that I do not see mentioned anywhere is
> E-mail addresses.
> While svn only maintains a simple user name, git requires user name +
> E-mail address.  Tools like git-svn will only create a dummy address
> (user@repository-hash or something like that).
> 
> When reactos moved to github in October, a list of svn committer names
> plus full (real) names and E-mail addresses was compiled and supplied to
> the conversion tool, with more meaningful dummy addresses for previous
> committers without a known valid E-mail address.
> Apertium could use something like
> svnnameofcommitterwhol...@svn.apertium.org
>  in that case.
> 
> My suggestion is therefore to scan all AUTHORS files for E-mail
> addresses and names corresponding to the respective committers.
> This has the additional benefit, that if those authors have a github
> account and use the same name+address combination with their github
> repositories, github will automatically recognize their commits as
> theirs.
> 
> Regards
> Benedikt
> 
> Am 04.02.2018 um 01:03 schrieb Shardul Chiplunkar:
> > To the President and members of the PMC and Apertium contributors,
> >
> > There is a new proposal to the PMC to move Apertium to Github:
> >
> http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
> 
> >
> > Both previous proposals of a similar topic had shortcomings which this
> > proposal tries to address.
> >
> > If you are not a member of the PMC but would like to express your
> > support for this proposal, please add your name to the "Non-PMC
> > signatories" section at the bottom of the page.
> >
> > Thank you,
> > Shardul C.
> >
> >
> >
> 
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >
> >
> >
> > ___
> > Apertium-stuff mailing list
> > Apertium-stuff@lists.sourceforge.net
> 
> > https://lists.sourceforge.net/lists/listinfo/apertium-stuff
> 
> >
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.ne

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Francis Tyers]

I'd like to add something to the general comments:

The change should take into account the GSOC timetable:

---
February 12 List of accepted mentoring organisations published
February 12 - March 12 	Potential student participants discuss 
application ideas with mentoring organisations

March 12 16:00 UTC  Student application period begins
March 27 16:00 UTC  Student application deadline
April 23 16:00 UTC  Accepted student proposals announced
---

The ideal thing would for it to be done before the 12th March so that
students can get used to it early on. But otherwise it should be 
definitely
done before the 23rd April so that changes aren't made during the 
bonding period.


(This is of course if Apertium gets accepted, otherwise it won't 
matter).


Fran

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Sushain Cherivirala]

Hi Benedikt,

Thank you for your reply. You raise a good question regarding the
preservation
of emails in a transition to Git.

Fortunately, in managing the Apertium packages for various platforms, Tino
has also
has put together a correspondence between SVN users and emails. The import
scripts that I have written use this correspondence. The current version
can be
found here: https://github.com/sushain97/apertium-on-github/blob/
master/authors.txt.

Here is some documentation for the scripts I mention:
https://github.com/sushain97/apertium-on-github#scripts.

If your proper email is missing, you could email Tino and I. If your email
in the file
does not correspond to the email you use from GitHub, it can be changed.
However, it might be easiest to just add the email to your GitHub account
(you
can ensure that it is private). Of course, a repo's authors can always be
modified
after the fact with a re-import or filter-branch operation if necessary.

I will leave you with an example of what the import script does when used on
apertium-cat: https://github.com/mock-apertium/apertium-
cat/graphs/contributors.

I am happy to answer any further questions.

--
Sushain K. Cherivirala

On Mon, Feb 5, 2018 at 5:06 AM, Benedikt Freisen  wrote:

> One not so unimportant issue that I do not see mentioned anywhere is
> E-mail addresses.
> While svn only maintains a simple user name, git requires user name +
> E-mail address.  Tools like git-svn will only create a dummy address
> (user@repository-hash or something like that).
>
> When reactos moved to github in October, a list of svn committer names
> plus full (real) names and E-mail addresses was compiled and supplied to
> the conversion tool, with more meaningful dummy addresses for previous
> committers without a known valid E-mail address.
> Apertium could use something like
> svnnameofcommitterwhol...@svn.apertium.org in that case.
>
> My suggestion is therefore to scan all AUTHORS files for E-mail
> addresses and names corresponding to the respective committers.
> This has the additional benefit, that if those authors have a github
> account and use the same name+address combination with their github
> repositories, github will automatically recognize their commits as theirs.
>
> Regards
> Benedikt
>
> Am 04.02.2018 um 01:03 schrieb Shardul Chiplunkar:
> > To the President and members of the PMC and Apertium contributors,
> >
> > There is a new proposal to the PMC to move Apertium to Github:
> > http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
> >
> > Both previous proposals of a similar topic had shortcomings which this
> > proposal tries to address.
> >
> > If you are not a member of the PMC but would like to express your
> > support for this proposal, please add your name to the "Non-PMC
> > signatories" section at the bottom of the page.
> >
> > Thank you,
> > Shardul C.
> >
> >
> > 
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >
> >
> >
> > ___
> > Apertium-stuff mailing list
> > Apertium-stuff@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/apertium-stuff
> >
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Benedikt Freisen]

One not so unimportant issue that I do not see mentioned anywhere is
E-mail addresses.
While svn only maintains a simple user name, git requires user name +
E-mail address.  Tools like git-svn will only create a dummy address
(user@repository-hash or something like that).

When reactos moved to github in October, a list of svn committer names
plus full (real) names and E-mail addresses was compiled and supplied to
the conversion tool, with more meaningful dummy addresses for previous
committers without a known valid E-mail address.
Apertium could use something like
svnnameofcommitterwhol...@svn.apertium.org in that case.

My suggestion is therefore to scan all AUTHORS files for E-mail
addresses and names corresponding to the respective committers.
This has the additional benefit, that if those authors have a github
account and use the same name+address combination with their github
repositories, github will automatically recognize their commits as theirs.

Regards
Benedikt

Am 04.02.2018 um 01:03 schrieb Shardul Chiplunkar:
> To the President and members of the PMC and Apertium contributors,
> 
> There is a new proposal to the PMC to move Apertium to Github:
> http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
> 
> Both previous proposals of a similar topic had shortcomings which this
> proposal tries to address.
> 
> If you are not a member of the PMC but would like to express your
> support for this proposal, please add your name to the "Non-PMC
> signatories" section at the bottom of the page.
> 
> Thank you,
> Shardul C.
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> 
> 
> 
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
> 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Tommi A Pirinen]

[Replies inline]
On Sat, 3 Feb 2018 16:03:48 -0800
Shardul Chiplunkar
 wrote:


> There is a new proposal to the PMC to move Apertium to Github:
> http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github

Yay, thanks :-)

As some of you probably know, I've moved my own apertium-fin{,-*} to
github some years ago. There are some shiny new stuff on github that I
liked and if you want to adapt them to mainline apertiums things
stuffs, I can probably help or you can just view e.g. apertium-fin-deu
in my githubs that has all the continuous integrations, continuous
deployment and github pages (generated from dixes via xslt and bahs
hacks!) experimented out a bit.

It will be good to see this done, like, I'm as opposed to jumping at
shiny new things as any grumpy old developer but git has well taken
over and showing SVN to e.g. gci kids this year already gets a reaction
of like CVS would've got ten years ago :-D

[0] 

-- 
Doktor Tommi A Pirinen, Computational Linguist,
, Universität
Hamburg, Hamburger Zentrum für Sprachkorpora . CLARIN-D
Entwickler.  President of ACL SIGUR SIG for Uralic languages
.
I tend to follow inline-posting style in desktop e-mail messages.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Sergio Ortiz Rojas]

I’m a recent (3 months) user of Gitlab (we switched from Redmine + subversion) 
and I must say that we are quite happy. I like it even more than Github.

But to vote in favour of either option I would like to read about how to move 
all the existing user base with minimal impact (how to announce, how to contact 
users, how to switch off the old repos, etc.)

> El 4 feb 2018, a las 13:41, Tino Didriksen  
> escribió:
> 
> On 4 February 2018 at 01:03, Shardul Chiplunkar  > wrote:
> There is a new proposal to the PMC to move Apertium to Github:
> http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github 
> 
> 
> 
> I'm in favour.
> 
> If we move to git (Github, Gitlab, whatever), we should do it in a way that's 
> natural for git - which means 1 repo per package. And git has definitely won 
> the hearts and minds of the VCS world.
> 
> I personally strongly dislike git for other reasons, but using Github as a 
> git host side-steps many of those issues thanks to the Subversion channel.
> 
> -- Tino Didriksen
> 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Sushain Cherivirala]

Hi folks,

Thanks for your input both via email and on the proposal page.

Shardul and I have responded to a number of questions on the proposal
including Mikel's.
We're happy to field any remaining questions and are particularly curious
to hear from
the remainder of the PMC. Thank you to those who have already cast their
votes.

Finally, I'll mention that we're developing the scripts to transition and
maintain an Apertium
on GitHub in this repository:
https://github.com/sushain97/apertium-on-github. The corresponding
documentation as well as the outstanding items are in the issue tracker,
for those interested.

--
Sushain K. Cherivirala

On Sun, Feb 4, 2018 at 6:56 AM, Francis Tyers  wrote:

> El 2018-02-04 13:41, Tino Didriksen escribió:
>
>> On 4 February 2018 at 01:03, Shardul Chiplunkar
>>  wrote:
>>
>> There is a new proposal to the PMC to move Apertium to Github:
>>>
>>> http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
>>> [1]
>>>
>>
>> I'm in favour.
>>
>> If we move to git (Github, Gitlab, whatever), we should do it in a way
>> that's natural for git - which means 1 repo per package. And git has
>> definitely won the hearts and minds of the VCS world.
>>
>> I personally strongly dislike git for other reasons, but using Github
>> as a git host side-steps many of those issues thanks to the Subversion
>> channel.
>>
>>
> At this point I am resigned to do whatever other people want, providing
> other people are going to take the load of supporting it. I don't like
> git at all and I can't help people use it or set it up, but the GitHub
> issue system is nice and SourceForge is really awful. So for me,
> "abstain, whatever". :)
>
> Fran
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Francis Tyers]

El 2018-02-04 13:41, Tino Didriksen escribió:

On 4 February 2018 at 01:03, Shardul Chiplunkar
 wrote:


There is a new proposal to the PMC to move Apertium to Github:

http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
[1]


I'm in favour.

If we move to git (Github, Gitlab, whatever), we should do it in a way
that's natural for git - which means 1 repo per package. And git has
definitely won the hearts and minds of the VCS world.

I personally strongly dislike git for other reasons, but using Github
as a git host side-steps many of those issues thanks to the Subversion
channel.



At this point I am resigned to do whatever other people want, providing
other people are going to take the load of supporting it. I don't like
git at all and I can't help people use it or set it up, but the GitHub
issue system is nice and SourceForge is really awful. So for me,
"abstain, whatever". :)

Fran

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Tino Didriksen]

On 4 February 2018 at 01:03, Shardul Chiplunkar <
shardul.chiplun...@gmail.com> wrote:

> There is a new proposal to the PMC to move Apertium to Github:
> http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
>


I'm in favour.

If we move to git (Github, Gitlab, whatever), we should do it in a way
that's natural for git - which means 1 repo per package. And git has
definitely won the hearts and minds of the VCS world.

I personally strongly dislike git for other reasons, but using Github as a
git host side-steps many of those issues thanks to the Subversion channel.

-- Tino Didriksen
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

To the President and members of the PMC and Apertium contributors,

There is a new proposal to the PMC to move Apertium to Github:
http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github

Both previous proposals of a similar topic had shortcomings which this
proposal tries to address.

If you are not a member of the PMC but would like to express your support
for this proposal, please add your name to the "Non-PMC signatories"
section at the bottom of the page.

Thank you,
Shardul C.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] proposal feedback?

[Mikel L. Forcada]

Irene, I have made a few comments on the Google Doc attached to your 
proposal in the Google Summer of Code site. Please check them there.


Mikel


El 02/04/17 a les 19:24, Irene Tang ha escrit:

hi,

could i get some feedback on my project proposal / work plan?

http://wiki.apertium.org/wiki/User:Irene/proposal 



thanks for your time
irene


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


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


--
Mikel L. Forcada  http://www.dlsi.ua.es/~mlf/
Departament de Llenguatges i Sistemes Informàtics
Universitat d'Alacant
E-03690 Sant Vicent del Raspeig
Spain
Office: +34 96 590 9776

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] proposal feedback?

[Irene Tang]

hi,

could i get some feedback on my project proposal / work plan?

http://wiki.apertium.org/wiki/User:Irene/proposal

thanks for your time
irene
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal for structured mentoring: feedback welcome

[robert]

http://wiki.apertium.org/wiki/User:Rcrowther/project_proposal

Soon as I thought of it, I thought, 'I'd like to do that'. But do tell
me if it fits wider Apertium project needs,

Rob


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal draft: Constraint-grammar aware unsupervised training of the part-of-speech tagger

[Frankie Robertson]

Hello Apertiumers,

I have submitted a proposal draft (very last minute I know) for the
task: Constraint-grammar aware unsupervised training of the
part-of-speech tagger. Any feedback any of the mentors can give me to
improve my application would be highly appreciated.

Would it also be possible to get a wiki account and Sourceforge SVN
access? In both cases the username is frankier.

Regards,
Frankie

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal for GSoC: Weighted transfer rules on the wiki

[Nikita Medyankin]

Dear Apertium mentors!

I have posted my proposal for Google Summer of Code at Apertium wiki 
(http://wiki.apertium.org/wiki/User:Nikita_Medyankin/GSoC_2016_WTR_Proposal). 
The task chosen is Weighted transfer rules. Please, kindly take a look 
at it when you have the time and send me any comments you might have.

I also shared a google docs draft in GSoC system in case you prefer 
commenting it there.

Regards,
Nikita

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal Submitted for Apertium assimilation evaluation toolkit Project

[Binay Neekhra]

Hi everyone,
I have submitted the proposal for Apertium assimilation evaluation toolkit
Project on Google melange.

The proposal is also posted on Apertium wiki:
http://wiki.apertium.org/wiki/User:Niks/Application

If possible, please take a look. Your feedbacks are welcome.

Thanks,
Binay
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal for Fuzzy-match repair from Translation Memory

[Mikel Forcada]

Al 03/21/2014 06:46 PM, En/na Pankaj Kumar Sharma ha escrit:
> Any feedback anyone ?
Dozens of proposals and many coming in right now before the deadline and 
a handful of mentors struggling to deal with them. Please understand if 
they cannot make it...

Mikel

-- 
Mikel L. Forcada (http://www.dlsi.ua.es/~mlf/)
Departament de Llenguatges i Sistemes Informàtics
Universitat d'Alacant
E-03071 Alacant, Spain
Phone: +34 96 590 9776
Fax: +34 96 590 9326


--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal for Fuzzy-match repair from Translation Memory

[Pankaj Kumar Sharma]

Any feedback anyone ?


On Fri, Mar 21, 2014 at 4:56 AM, Pankaj Kumar Sharma <
sharmapankaj1...@gmail.com> wrote:

> Hello everyone,
>
> After discussions with Mikel and some other community members, I've
> created a proposal for above mentioned topic.
>
> The proposal could be found here:
> http://wiki.apertium.org/wiki/User:Pankajksharma/Application
>
> I request everyone to please have a look and provide your feedback so that
> I could improve over this.
>
> Thanks,
>
> Pankaj
>
> --
> Pankaj Kumar Sharma | पंकज कुमार शर्मा
>  Jamia Millia Islamia
>



-- 
Pankaj Kumar Sharma | पंकज कुमार शर्मा
 Jamia Millia Islamia
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal for Google Summer Of Code 2014

[Mikel Forcada]

Divya,
you have to submit it through Google Melange!

Cheers

Mikel

Al 03/21/2014 06:33 PM, En/na Divya Upadhyay ha escrit:


*Name:* Divya Upadhyay

*E-mail address:* divyaupadhya...@gmail.com 



*Other information that may be useful to contact you: *

*E-mail address(other): *angel...@gmail.com 

*Contact No. :* +91-8102302880

*Freenode irc Nickname:* phoenix_du


*Title:*/ Etymology support using machine translation/



--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech


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



--
Mikel L. Forcada (http://www.dlsi.ua.es/~mlf/)
Departament de Llenguatges i Sistemes Informàtics
Universitat d'Alacant
E-03071 Alacant, Spain
Phone: +34 96 590 9776
Fax: +34 96 590 9326

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal for Google Summer Of Code 2014

[Divya Upadhyay]

*Name:* Divya Upadhyay

*E-mail address:* divyaupadhya...@gmail.com

*Other information that may be useful to contact you: *

*E-mail address(other): *angel...@gmail.com

*Contact No. :* +91-8102302880

*Freenode irc Nickname:* phoenix_du


*Title:** Etymology support using machine translation*


Proposal for Google Summer Of Code 2014.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal for Fuzzy-match repair from Translation Memory

[Pankaj Kumar Sharma]

Hello everyone,

After discussions with Mikel and some other community members, I've created
a proposal for above mentioned topic.

The proposal could be found here:
http://wiki.apertium.org/wiki/User:Pankajksharma/Application

I request everyone to please have a look and provide your feedback so that
I could improve over this.

Thanks,

Pankaj

-- 
Pankaj Kumar Sharma | पंकज कुमार शर्मा
 Jamia Millia Islamia
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] proposal page of sphinx

[Jimmy O'Regan]

On 28 April 2013 08:37, sphinx jiang  wrote:
> Hi,
> This is my original proposal page of GSOC, maybe something need to be
> modified, so publish now to get some advise~~
>
> http://wiki.apertium.org/wiki/User:Sphinx/GSoC_2013_Application:_%22Chinese(simple)-Chinese(traditional)_language_pair%22

You should replace the screenshots with text (use ) and maybe
rename your github repo to include the language names.

-- 
 Are any of the mentors around?
 yes, they're the ones trolling you

--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] proposal page of sphinx

[Mikel Forcada]

Sphinx,
add it to this page: 
http://wiki.apertium.org/wiki/Category:GSoC_2013_Student_proposals where 
the other proposals are.


Apertiumers: I can't find it. What would be a suitable "coding 
challenge" for a new, but related language pair?


Mikel

Al 04/28/2013 09:37 AM, En/na sphinx jiang ha escrit:

Hi,
This is my original proposal page of GSOC, maybe something need to be 
modified, so publish now to get some advise~~


http://wiki.apertium.org/wiki/User:Sphinx/GSoC_2013_Application:_%22Chinese(simple)-Chinese(traditional)_language_pair%22 



Thank you~~

All the best
Sphinx



--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr


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



--
Mikel L. Forcada (http://www.dlsi.ua.es/~mlf/)
Departament de Llenguatges i Sistemes Informàtics
Universitat d'Alacant
E-03071 Alacant, Spain
Phone: +34 96 590 9776
Fax: +34 96 590 9326

--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] proposal page of sphinx

[sphinx jiang]

Hi,
This is my original proposal page of GSOC, maybe something need to be
modified, so publish now to get some advise~~

http://wiki.apertium.org/wiki/User:Sphinx/GSoC_2013_Application:_%22Chinese(simple)-Chinese(traditional)_language_pair%22

Thank you~~

All the best
Sphinx
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] proposal for change to .lrx format

[Francis Tyers]

El dl 08 de 10 de 2012 a les 07:50 +0200, en/na Kevin Brubeck Unhammer
va escriure:
> Mikel Forcada  writes:
> 
> > Fran,
> >
> >>
> >> I'd like to include the possibility for lists in the LRX format. This
> >> would involve adding a couple of new tags,
> > That should not be a problem as long as the old format works in the new 
> > definition
> >> and changing the root tag,
> > You would have to give a good reason for it.
> >> the idea is to have something like:
> >>
> >> http://pastebin.com/GGzfM5qc
> > OK. I would have appreciated comments in the .lrx file...
> >>
> >> Calling a  would just involve putting it's contents in the rule.
> >> So with  it would work like an OR, but without, it would work like a
> >> sequence.
> > I don't like this at all. This is very opaque. I would not use the tag 
> > . If it is a set from where you choose, call it  or 
> > ... if it is a  define it as a sequence. But don't 
> > overload something called a  that really isn't.
> >
> > Another option would be to have a named macro that can contain anything 
> > that a rule can contain. Then you would use  for lists, etc. But 
> > ... does not read well.
> 
>  sounds more correct =P
> 
> Since CG uses 'list' only for the disjunction, I think CG-ers would be
> confused too, if that matters. (CG uses 'template' for the sequence,
> though those templates can be a bit more involved.)

Yes, I think it would be too confusing ... :/ And for template, I think
we should go with Mikel's  idea, but at a later stage...

Fran


--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] proposal for change to .lrx format

[Francis Tyers]

El dl 08 de 10 de 2012 a les 07:04 +0200, en/na Mikel Forcada va
escriure:
> Fran,
> 
> >
> > I'd like to include the possibility for lists in the LRX format. This
> > would involve adding a couple of new tags,
> That should not be a problem as long as the old format works in the new 
> definition
> > and changing the root tag,
> You would have to give a good reason for it.

Unfortunately the current root tag is  ... :/

> > the idea is to have something like:
> >
> > http://pastebin.com/GGzfM5qc
> OK. I would have appreciated comments in the .lrx file...

Sorry, next time I'll add some!

> > Calling a  would just involve putting it's contents in the rule.
> > So with  it would work like an OR, but without, it would work like a
> > sequence.
> I don't like this at all. This is very opaque. I would not use the tag 
> . If it is a set from where you choose, call it  or 
> ... if it is a  define it as a sequence. But don't 
> overload something called a  that really isn't.
> 
> Another option would be to have a named macro that can contain anything 
> that a rule can contain. Then you would use  for lists, etc. But 
> ... does not read well.
> 
> Hope this helps.

Yep thanks! I think it deserves further thought before being
implemented, so I'll leave it to an XSL for now. 

Fran


--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] proposal for change to .lrx format

[Jacob Nordfalk]

2012/10/8 Mikel Forcada 

>
> > http://pastebin.com/GGzfM5qc
> >
> > Calling a  would just involve putting it's contents in the rule.
> > So with  it would work like an OR, but without, it would work like a
> > sequence.
> I don't like this at all. This is very opaque. I would not use the tag
> . If it is a set from where you choose, call it  or
> ... if it is a  define it as a sequence. But don't
> overload something called a  that really isn't.
>

I was also confused about the

   1. 
   2. 
   3.   


I understand the simple copy-paste philosophy that you propose, but how
often would you ever need to re-use a sequence of more than, say 4 words,
making it actually worthwile to put it into a list for re-use? I'd guess:
Never.

I'd say that lists have an implicit  so the rule could be written


   1.
   
   2.   
   3.   
   4.   
   5. 



I imagine that its much more common that you need to mix lists of words
with lemmas like this


   1. 
   2.   
   3.   
   4. ...
   5. 

(I just made this up, hope it gives sense)

Note also that if we leave the simple copy-paste philosophy that you
propose it would be better to use the above syntax.


If we keep the simple copy-paste philosophy that you propose, I'd use
another word, like , that clearly indicates that there is no logic
beyound copy-paste
Then it would look like: http://pastebin.com/Mc172B5N



   1.  
   2. 
   3.   
   4.   
   5.   
   6.   
   7. 



...

   1. 
   2.   
   3.   
   4.   
   5. 




-- 
Jacob Nordfalk 
javabog.dk
Androidudvikler og -underviser på
IHKog
Lund&Bendsen 
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] proposal for change to .lrx format

[Kevin Brubeck Unhammer]

Mikel Forcada  writes:

> Fran,
>
>>
>> I'd like to include the possibility for lists in the LRX format. This
>> would involve adding a couple of new tags,
> That should not be a problem as long as the old format works in the new 
> definition
>> and changing the root tag,
> You would have to give a good reason for it.
>> the idea is to have something like:
>>
>> http://pastebin.com/GGzfM5qc
> OK. I would have appreciated comments in the .lrx file...
>>
>> Calling a  would just involve putting it's contents in the rule.
>> So with  it would work like an OR, but without, it would work like a
>> sequence.
> I don't like this at all. This is very opaque. I would not use the tag 
> . If it is a set from where you choose, call it  or 
> ... if it is a  define it as a sequence. But don't 
> overload something called a  that really isn't.
>
> Another option would be to have a named macro that can contain anything 
> that a rule can contain. Then you would use  for lists, etc. But 
> ... does not read well.

 sounds more correct =P

Since CG uses 'list' only for the disjunction, I think CG-ers would be
confused too, if that matters. (CG uses 'template' for the sequence,
though those templates can be a bit more involved.)


-- 
Kevin Brubeck Unhammer

GPG: 0x766AC60C


--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] proposal for change to .lrx format

[Mikel Forcada]

Fran,

>
> I'd like to include the possibility for lists in the LRX format. This
> would involve adding a couple of new tags,
That should not be a problem as long as the old format works in the new 
definition
> and changing the root tag,
You would have to give a good reason for it.
> the idea is to have something like:
>
> http://pastebin.com/GGzfM5qc
OK. I would have appreciated comments in the .lrx file...
>
> Calling a  would just involve putting it's contents in the rule.
> So with  it would work like an OR, but without, it would work like a
> sequence.
I don't like this at all. This is very opaque. I would not use the tag 
. If it is a set from where you choose, call it  or 
... if it is a  define it as a sequence. But don't 
overload something called a  that really isn't.

Another option would be to have a named macro that can contain anything 
that a rule can contain. Then you would use  for lists, etc. But 
... does not read well.

Hope this helps.

Mikel
>
> Any thoughts ?
>
> Fran
>
>
> --
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff


-- 
Mikel L. Forcada (http://www.dlsi.ua.es/~mlf/)
Departament de Llenguatges i Sistemes Informàtics
Universitat d'Alacant
E-03071 Alacant, Spain
Phone: +34 96 590 9776
Fax: +34 96 590 9326


--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] proposal for change to .lrx format

[Francis Tyers]

Hey all,

I'd like to include the possibility for lists in the LRX format. This
would involve adding a couple of new tags, and changing the root tag,
the idea is to have something like:

http://pastebin.com/GGzfM5qc

Calling a  would just involve putting it's contents in the rule.
So with  it would work like an OR, but without, it would work like a
sequence.

Any thoughts ? 

Fran


--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Kevin Brubeck Unhammer]

Jacob Nordfalk 
writes:

> Hi there!
>
> As no objections have been raised I think we can conclude that this proposal 
> has PASSED
> :-)
>
> Unhammer, could apply your patch to the SVN trunk ?
>
> Jacob

Committed revision 38346.


> 2012/3/27 Stephen Tigner 
>
> On Mon, Mar 26, 2012 at 1:04 PM, Jacob Nordfalk
>  wrote:
> >
> >
> > 2012/3/26 Stephen Tigner 
> [snip]
> >> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable?
> >
> >
> > Sorry, it wasnt clear (again - Unhammer, your'e fired as ghost writer 
> :-).
> > APERTIUM_PATH would be the path to the 'apertium binary'
> > In shell language it would be expressed as
> >
> > APERTIUM_PATH="$(dirname $0)"
> >
> > this makes sure that binaries are first searched for in the same 
> directory
> > as the 'apertium' command.
> >
> Ah, okay. That makes more sense then.
>
> On Mon, Mar 26, 2012 at 1:08 PM, Kevin Brubeck Unhammer
>  wrote:
> > Stephen Tigner 
> > writes:
> [snip]
> >> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable? If
> >> so, that should be fairly easy to implement. Just need to tweak a bit
> >> how the UNKNOWN programs are called. I'll try and take a look at it
> >> tonight if I have time. n.n
> >
> > If you install apertium to /usr/local/bin/, the shell script
> > /usr/local/bin/apertium will have
> > APERTIUM_PATH="/usr/local/bin"
> > as the second line.
>
> So basically it just prepends the apertium path to the system path?
> Well, I don't really think any modification of the existing Java code
> would be needed, then. Because the desired behavior is already the
> current behavior, as long as you remove the explicit paths from the
> mode file.
>
> This is because it always checks if it can be done internally first,
> and then it already depends on the host runtime to run the UNKNOWN
> programs, and that of course would reference the system path and any
> conventions the system has for finding executables to run. (Like the
> convention that the current working directory is always considered
> implicitly first on the path in Windows.)
>
> I used the same trick (letting the host runtime handle path searching)
> for trying to run cygpath (since I, AFAIK know, I have no way of
> knowing where cygwin is installed, or at least not an elegant and
> robust way) and javac for run-time compilation of transfer files (for
> instance when running on a JRE instead of a JDK, but the JDK is
> present on the system and in the system path).
>
> Hopeful that he's not just rambling and needing sleep now,  ;)
> -- Stephen


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Jacob Nordfalk]

Hi there!

As no objections have been raised I think we can conclude that this
proposal has PASSED :-)

Unhammer, could apply your patch to the SVN trunk ?

Jacob


2012/3/27 Stephen Tigner 

> On Mon, Mar 26, 2012 at 1:04 PM, Jacob Nordfalk
>  wrote:
> >
> >
> > 2012/3/26 Stephen Tigner 
> [snip]
> >> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable?
> >
> >
> > Sorry, it wasnt clear (again - Unhammer, your'e fired as ghost writer
> :-).
> > APERTIUM_PATH would be the path to the 'apertium binary'
> > In shell language it would be expressed as
> >
> > APERTIUM_PATH="$(dirname $0)"
> >
> > this makes sure that binaries are first searched for in the same
> directory
> > as the 'apertium' command.
> >
> Ah, okay. That makes more sense then.
>
> On Mon, Mar 26, 2012 at 1:08 PM, Kevin Brubeck Unhammer
>  wrote:
> > Stephen Tigner 
> > writes:
> [snip]
> >> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable? If
> >> so, that should be fairly easy to implement. Just need to tweak a bit
> >> how the UNKNOWN programs are called. I'll try and take a look at it
> >> tonight if I have time. n.n
> >
> > If you install apertium to /usr/local/bin/, the shell script
> > /usr/local/bin/apertium will have
> > APERTIUM_PATH="/usr/local/bin"
> > as the second line.
>
> So basically it just prepends the apertium path to the system path?
> Well, I don't really think any modification of the existing Java code
> would be needed, then. Because the desired behavior is already the
> current behavior, as long as you remove the explicit paths from the
> mode file.
>
> This is because it always checks if it can be done internally first,
> and then it already depends on the host runtime to run the UNKNOWN
> programs, and that of course would reference the system path and any
> conventions the system has for finding executables to run. (Like the
> convention that the current working directory is always considered
> implicitly first on the path in Windows.)
>
> I used the same trick (letting the host runtime handle path searching)
> for trying to run cygpath (since I, AFAIK know, I have no way of
> knowing where cygwin is installed, or at least not an elegant and
> robust way) and javac for run-time compilation of transfer files (for
> instance when running on a JRE instead of a JDK, but the JDK is
> present on the system and in the system path).
>
> Hopeful that he's not just rambling and needing sleep now,  ;)
> -- Stephen
>
>
> --
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>



-- 
Jacob Nordfalk 
http://javabog.dk
Android-udvikler og underviser på
IHKog
Lund&Bendsen 
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Stephen Tigner]

On Mon, Mar 26, 2012 at 1:04 PM, Jacob Nordfalk
 wrote:
>
>
> 2012/3/26 Stephen Tigner 
[snip]
>> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable?
>
>
> Sorry, it wasnt clear (again - Unhammer, your'e fired as ghost writer :-).
> APERTIUM_PATH would be the path to the 'apertium binary'
> In shell language it would be expressed as
>
> APERTIUM_PATH="$(dirname $0)"
>
> this makes sure that binaries are first searched for in the same directory
> as the 'apertium' command.
>
Ah, okay. That makes more sense then.

On Mon, Mar 26, 2012 at 1:08 PM, Kevin Brubeck Unhammer
 wrote:
> Stephen Tigner 
> writes:
[snip]
>> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable? If
>> so, that should be fairly easy to implement. Just need to tweak a bit
>> how the UNKNOWN programs are called. I'll try and take a look at it
>> tonight if I have time. n.n
>
> If you install apertium to /usr/local/bin/, the shell script
> /usr/local/bin/apertium will have
> APERTIUM_PATH="/usr/local/bin"
> as the second line.

So basically it just prepends the apertium path to the system path?
Well, I don't really think any modification of the existing Java code
would be needed, then. Because the desired behavior is already the
current behavior, as long as you remove the explicit paths from the
mode file.

This is because it always checks if it can be done internally first,
and then it already depends on the host runtime to run the UNKNOWN
programs, and that of course would reference the system path and any
conventions the system has for finding executables to run. (Like the
convention that the current working directory is always considered
implicitly first on the path in Windows.)

I used the same trick (letting the host runtime handle path searching)
for trying to run cygpath (since I, AFAIK know, I have no way of
knowing where cygwin is installed, or at least not an elegant and
robust way) and javac for run-time compilation of transfer files (for
instance when running on a JRE instead of a JDK, but the JDK is
present on the system and in the system path).

Hopeful that he's not just rambling and needing sleep now,  ;)
-- Stephen

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Kevin Brubeck Unhammer]

Stephen Tigner 
writes:

> On Sun, Mar 25, 2012 at 10:49 AM, Jacob Nordfalk
>  wrote:
>> +1 for the proposal.
>>
>> 2012/3/24 Stephen Tigner 
>>>
>>> I think I'm gonna need to read that again a few times to see if that'd
>>> affect the Java runtime at all,
>>
>>
>> Unhammer is actually writing this as a result of a discussion I started on
>> IRC on the occasion that I didnt like lttoolbox-java to have to cut away
>> these paths.
>>
>> (Unhammer, I want you as my ghost writer :-)
> Ah, I see. makes more sense now, thanks.
>
>>>
>>> but I thought I'd at least pitch in
>>> with an explanation of how the Java runtime currently handles .mode
>>> files.
>>
>>
>> Thanks for a great explanation.
>> Anyone who wants to browse the code he explains can look
>> at http://apertium.svn.sourceforge.net/viewvc/apertium/trunk/lttoolbox-java/src/org/apertium/pipeline/
>>
>>
>>>
>>> A quick fix that uses path could be to check for existence of the
>>> program at the specified path, and if not, try running it w/ just the
>>> command name w/o a full path.
>>
>>
>> Its not that clear from the code diff, but the idea is first to look for the
>> commands in the installation dir, then on the general PATH:
>>
>> PATH="${APERTIUM_PATH}:${PATH}"
>>
>>
>> I think the java port should do the same, but first check if the task can be
>> done by lttoolbox-java itself internally. So, like
>>
>> PATH="can we do it without invoking external
>> stuff?:${APERTIUM_PATH}:${PATH}"
>>
>> :-)
>
> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable? If
> so, that should be fairly easy to implement. Just need to tweak a bit
> how the UNKNOWN programs are called. I'll try and take a look at it
> tonight if I have time. n.n

If you install apertium to /usr/local/bin/, the shell script
/usr/local/bin/apertium will have 
APERTIUM_PATH="/usr/local/bin" 
as the second line.

--
Kevin Brubeck Unhammer


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Jacob Nordfalk]

2012/3/26 Stephen Tigner 

> On Sun, Mar 25, 2012 at 10:49 AM, Jacob Nordfalk
>  wrote:
>
> > Its not that clear from the code diff, but the idea is first to look for
> the
> > commands in the installation dir, then on the general PATH:
> >
> > PATH="${APERTIUM_PATH}:${PATH}"
> >
> >
> > I think the java port should do the same, but first check if the task
> can be
> > done by lttoolbox-java itself internally. So, like
> >
> > PATH="can we do it without invoking external
> > stuff?:${APERTIUM_PATH}:${PATH}"
> >
> > :-)
>
> Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable?


Sorry, it wasnt clear (again - Unhammer, your'e fired as ghost writer :-).
APERTIUM_PATH would be the path to the 'apertium binary'
In shell language it would be expressed as

APERTIUM_PATH="$(dirname $0)"

this makes sure that binaries are first searched for in the same directory
as the 'apertium' command.



-- 
Jacob Nordfalk 
http://javabog.dk
Android-udvikler og underviser på
IHKog
Lund&Bendsen 
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Stephen Tigner]

On Sun, Mar 25, 2012 at 10:49 AM, Jacob Nordfalk
 wrote:
> +1 for the proposal.
>
> 2012/3/24 Stephen Tigner 
>>
>> I think I'm gonna need to read that again a few times to see if that'd
>> affect the Java runtime at all,
>
>
> Unhammer is actually writing this as a result of a discussion I started on
> IRC on the occasion that I didnt like lttoolbox-java to have to cut away
> these paths.
>
> (Unhammer, I want you as my ghost writer :-)
Ah, I see. makes more sense now, thanks.

>>
>> but I thought I'd at least pitch in
>> with an explanation of how the Java runtime currently handles .mode
>> files.
>
>
> Thanks for a great explanation.
> Anyone who wants to browse the code he explains can look
> at http://apertium.svn.sourceforge.net/viewvc/apertium/trunk/lttoolbox-java/src/org/apertium/pipeline/
>
>
>>
>> A quick fix that uses path could be to check for existence of the
>> program at the specified path, and if not, try running it w/ just the
>> command name w/o a full path.
>
>
> Its not that clear from the code diff, but the idea is first to look for the
> commands in the installation dir, then on the general PATH:
>
> PATH="${APERTIUM_PATH}:${PATH}"
>
>
> I think the java port should do the same, but first check if the task can be
> done by lttoolbox-java itself internally. So, like
>
> PATH="can we do it without invoking external
> stuff?:${APERTIUM_PATH}:${PATH}"
>
> :-)

Ah, okay, so I'm assuming APERTIUM_PATH is an environment variable? If
so, that should be fairly easy to implement. Just need to tweak a bit
how the UNKNOWN programs are called. I'll try and take a look at it
tonight if I have time. n.n

-- Stephen

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Jacob Nordfalk]

+1 for the proposal.

2012/3/24 Stephen Tigner 

> I think I'm gonna need to read that again a few times to see if that'd
> affect the Java runtime at all,


Unhammer is actually writing this as a result of a discussion I started on
IRC on the occasion that I didnt like lttoolbox-java to have to cut away
these paths.

(Unhammer, I want you as my ghost writer :-)



> but I thought I'd at least pitch in
> with an explanation of how the Java runtime currently handles .mode
> files.
>

Thanks for a great explanation.
Anyone who wants to browse the code he explains can look at
http://apertium.svn.sourceforge.net/viewvc/apertium/trunk/lttoolbox-java/src/org/apertium/pipeline/



> A quick fix that uses path could be to check for existence of the
> program at the specified path, and if not, try running it w/ just the
> command name w/o a full path.


Its not that clear from the code diff, but the idea is first to look for
the commands in the installation dir, then on the general PATH:

PATH="${APERTIUM_PATH}:${PATH}"


I think the java port should do the same, but first check if the task can
be done by lttoolbox-java itself internally. So, like

PATH="can we do it without invoking external
stuff?:${APERTIUM_PATH}:${PATH}"

:-)


-- 
Jacob Nordfalk 
http://javabog.dk
Android-udvikler og underviser på
IHKog
Lund&Bendsen 
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Francis Tyers]

El dv 23 de 03 de 2012 a les 12:23 +0100, en/na Kevin Brubeck Unhammer
va escriure:
> Currently, a modes file looks like this:
> 
>   /usr/local/bin/lt-proc -w
>   /usr/local/bin/nb-nn.automorf-no-cp.bin|/usr/local/bin/cg-proc -w
>   /usr/local/bin/nb-nn.rlx.bin|/usr/local/bin/apertium-tagger -g $2
>   /usr/local/bin/nb-nn.prob | # etc
> 
> with full paths to each program. This works fine in many cases, but as
> Jacob Nordfalk noted, it gets in the way if you want to e.g. replace
> programs with their Java counterparts, but still use the installed .mode
> files (not every pair installs modes.xml, so that's not reliable).
> 
> Other users have wanted to keep HFST or vislcg3 in one prefix, and
> apertium/lttoolbox in another, for whatever reason. One could also
> imagine user who installs apertium + lttoolbox with their package
> manager (which puts things /usr), but finds no recent enough package for
> vislcg3, and installs that from source with the default options (ie. to
> /usr/local). The user tries the standard Unix way of putting the path to
> cg-proc in $PATH, but since modes files have the path to a non-existant
> program hard-coded, the user has the choice between either installing
> apertium/lttoolbox from svn, or messing up /usr with packages that
> really belong in /usr/local.
> 
> This could be more unixy by simply using $PATH instead. Here's a
> proposal:
> 
> 1) When generating modes files, if the prefix attribute is not set,
>don't set a prefix at all, but assume the program is in path:
> 
> $ svn diff apertium/modes2bash.xsl 
> Index: apertium/modes2bash.xsl
> ===
> --- apertium/modes2bash.xsl (revision 36540)
> +++ apertium/modes2bash.xsl (working copy)
> @@ -48,12 +48,9 @@
>
>  
>
> +  
>  
> -
> -  
> -
>
> -  
>
>  
>  
> 
> 
> 2) We probably want the user (or some third-party program) to be able to
>call /apertium-prefix/bin/apertium even if /apertium-prefix/bin is
>not in PATH, so ensure PATH contains at least /apertium-prefix/bin/
>before running the modes file when starting the apertium script:
> 
> $ svn diff apertium/apertium-header.sh 
> Index: apertium/apertium-header.sh
> ===
> --- apertium/apertium-header.sh (revision 36540)
> +++ apertium/apertium-header.sh (working copy)
> @@ -1,3 +1,4 @@
> +PATH="${APERTIUM_PATH}:${PATH}"
>  PAIR=""
>  INPUT_FILE="/dev/stdin"
>  OUTPUT_FILE="/dev/stdout"
> 
> 
> The change to apertium/apertium-header.sh is backwards compatible with
> old modes files, so no need to recompile all pairs. I don't see how this
> could break anything, but it could mean less trouble for new developers
> who have programs installed to different prefixes and expect that
> setting $PATH should solve their problems. And anyone wanting a Java
> version of the apertium script can use modes files as they are by
> setting some other $PATH.
> 
> (Note: since the apertium script prepends to PATH, it will prefer files
> in APERTIUM_PATH, so you can't put an experimental lt-proc in
> $HOME/foo/bin/lt-proc and do "PATH=$HOME/foo/bin /usr/bin/apertium". But
> you can't do that now either, and if you've installed lt-proc to a
> prefix you're surely able to install apertium to the same prefix.
> Putting APERTIUM_PATH in PATH in the apertium script is necessary if you
> want it to be runnable by other programs that don't have PATH set at
> all, so I think that line should be there.)
> 
> 
> 
> So what do people think?

It sounds ok, gives more functionality without breaking how things are.

+1

Fran


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Stephen Tigner]

I think I'm gonna need to read that again a few times to see if that'd
affect the Java runtime at all, but I thought I'd at least pitch in
with an explanation of how the Java runtime currently handles .mode
files.

When the Java runtime is invoked, it's given a "data directory" as a
command-line parameter. It expects to find the mode files in the
"modes" directory under that data dir. Inside that directory it looks
for a file matching the name of the language pair and direction given
(ex: en-es, es-en, en-eo, eo-en) plus ".mode". (See
org.apertium.pipeline.AperiumMain.java, line 282.)

It then parses that file, splitting on pipes ("|", see
org.aperium.pipeline.Mode.java, line 39), and then parses each
individual program. Then in org.aperium.pipeline.Program.java it
checks to see if the program is one of the components that was ported
to the Java runtime, and if so, sets it up to be run using that.
Otherwise sets it up as an UNKNOWN program. (See lines 67 - 85.)

UNKNOWN programs are run by calling Runtime.getRuntime().exec() and
then trying to execute the full path of the program as specified in
the mode file. (See org.apertium.pipeline.Dispatcher.java, lines 270
and 271.)

A quick fix that uses path could be to check for existence of the
program at the specified path, and if not, try running it w/ just the
command name w/o a full path. I'm not certain at the moment how
fragile that'd be though. ;) Again, AFAIK this only effects language
pairs that use components that aren't in the Java runtime.

Hope this helps add to the discussion. ^_^

-- Stephen

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal: don't prefix paths in apertium-gen-modes (but prefix dirname $0 to PATH in apertium)

[Kevin Brubeck Unhammer]

Currently, a modes file looks like this:

  /usr/local/bin/lt-proc -w
  /usr/local/bin/nb-nn.automorf-no-cp.bin|/usr/local/bin/cg-proc -w
  /usr/local/bin/nb-nn.rlx.bin|/usr/local/bin/apertium-tagger -g $2
  /usr/local/bin/nb-nn.prob | # etc

with full paths to each program. This works fine in many cases, but as
Jacob Nordfalk noted, it gets in the way if you want to e.g. replace
programs with their Java counterparts, but still use the installed .mode
files (not every pair installs modes.xml, so that's not reliable).

Other users have wanted to keep HFST or vislcg3 in one prefix, and
apertium/lttoolbox in another, for whatever reason. One could also
imagine user who installs apertium + lttoolbox with their package
manager (which puts things /usr), but finds no recent enough package for
vislcg3, and installs that from source with the default options (ie. to
/usr/local). The user tries the standard Unix way of putting the path to
cg-proc in $PATH, but since modes files have the path to a non-existant
program hard-coded, the user has the choice between either installing
apertium/lttoolbox from svn, or messing up /usr with packages that
really belong in /usr/local.

This could be more unixy by simply using $PATH instead. Here's a
proposal:

1) When generating modes files, if the prefix attribute is not set,
   don't set a prefix at all, but assume the program is in path:

$ svn diff apertium/modes2bash.xsl 
Index: apertium/modes2bash.xsl
===
--- apertium/modes2bash.xsl (revision 36540)
+++ apertium/modes2bash.xsl (working copy)
@@ -48,12 +48,9 @@
   
 
   
+  
 
-
-  
-
   
-  
   
 
 


2) We probably want the user (or some third-party program) to be able to
   call /apertium-prefix/bin/apertium even if /apertium-prefix/bin is
   not in PATH, so ensure PATH contains at least /apertium-prefix/bin/
   before running the modes file when starting the apertium script:

$ svn diff apertium/apertium-header.sh 
Index: apertium/apertium-header.sh
===
--- apertium/apertium-header.sh (revision 36540)
+++ apertium/apertium-header.sh (working copy)
@@ -1,3 +1,4 @@
+PATH="${APERTIUM_PATH}:${PATH}"
 PAIR=""
 INPUT_FILE="/dev/stdin"
 OUTPUT_FILE="/dev/stdout"


The change to apertium/apertium-header.sh is backwards compatible with
old modes files, so no need to recompile all pairs. I don't see how this
could break anything, but it could mean less trouble for new developers
who have programs installed to different prefixes and expect that
setting $PATH should solve their problems. And anyone wanting a Java
version of the apertium script can use modes files as they are by
setting some other $PATH.

(Note: since the apertium script prepends to PATH, it will prefer files
in APERTIUM_PATH, so you can't put an experimental lt-proc in
$HOME/foo/bin/lt-proc and do "PATH=$HOME/foo/bin /usr/bin/apertium". But
you can't do that now either, and if you've installed lt-proc to a
prefix you're surely able to install apertium to the same prefix.
Putting APERTIUM_PATH in PATH in the apertium script is necessary if you
want it to be runnable by other programs that don't have PATH set at
all, so I think that line should be there.)



So what do people think?


-Kevin


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Jimmy O'Regan]

On 8 February 2011 21:56, Jimmy O'Regan  wrote:
> On 8 February 2011 21:30, Kevin Brubeck Unhammer  wrote:
>> Gema Ramírez-Sánchez  writes:
>>> I like the idea in general, how should we go ahead? making a proposal
>>> and submitting it to the PMC?
>>
>> Agreed. I like the idea too. Having pairs that are a little testvoc away
>> from release in the same place as pairs that have 20 lines of bidix is
>> both confusing and demotivating.
>>
>
> Ok, so unless there are any objections, I'll put it to the PMC.
>

I put the proposals on the wiki:
http://wiki.apertium.org/wiki/PMC_Proposals/Repository_reorganisation
http://wiki.apertium.org/wiki/PMC_Proposals/Pre-releases

Comments are welcome, particularly as
1) This is a new process
2) It seems as though both proposals will need to be revised to move forward.

-- 
 jimregan, that's because deep inside you, you are evil.
 Also not-so-deep inside you.

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Jimmy O'Regan]

On 8 February 2011 21:30, Kevin Brubeck Unhammer  wrote:
> Gema Ramírez-Sánchez  writes:
>> I like the idea in general, how should we go ahead? making a proposal
>> and submitting it to the PMC?
>
> Agreed. I like the idea too. Having pairs that are a little testvoc away
> from release in the same place as pairs that have 20 lines of bidix is
> both confusing and demotivating.
>

Ok, so unless there are any objections, I'll put it to the PMC.

> I'm for doing prereleases too; and not only because the first week after
> a release you remember that all-important bug you forgot to fix...

I was hoping you'd mention that :)

> I
> think it can be motivating to someone who's stuck in testvoc to get
> something out there and hopefully some feedback.  Also, there are very
> few releases compared to the amount of work going on in SVN; if nothing
> else, I think more releases could be good for publicity...  Of course,
> like svn moving, it should be up to the language pair maintainers.

I dunno... I think it could be quite useful if, say, Fran could
threaten me with releasing a -pre version of something.

Also, on the pre vs. alpha thing - maybe we could have both? '-pre'
implies to me that a release will come shortly, while '-alpha' is sort
of the no commitment version - en-it is a 'pre' candidate (just a
testvoc away), while cs-pl is 'alpha', but feedback would be welcome
for both. Plus, they come out the right way in ls:

$ ls|cat
foo-0.1-alpha.txt
foo-0.1-pre.txt
foo-0.1.txt
foo-0.2.txt


-- 
 jimregan, that's because deep inside you, you are evil.
 Also not-so-deep inside you.

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Kevin Brubeck Unhammer]

Gema Ramírez-Sánchez  writes:

> So, correct if wrong...
>
>  TRUNK: would contain pairs in "release" and "[alpha|pre]-release"
> status an no pair without a release.
>
>  STAGING: would contain pairs that builds and have an advanced status
> of all modules (dictionaries with closed cathegories and a decent
> coverage, an "ad hoc" PoS tagset and .prob, good coverage of main
> contrastive phenomena, testvoc clean, and a post-generator if needed).
> There should be a "PROBLEMS" file saying, IMO, status and major
> problems found while reading translations done with this pair (so, not
> a complete evaluation but a general compilation of big problems
> detected at the output). That could be a middle solution between Fran
> and Jim point of view. Would  [Alpha|Pre]-releases also be allowed for
> pairs in staging?
>
> NURSERY: would contain pairs that build but that have not been
> developed deeply or maybe data copied from other pairs that needs work
> or very poor data on some modules, etc.
>
>  INCUBATOR: would contain pairs with pieces of translators
>
> I like the idea in general, how should we go ahead? making a proposal
> and submitting it to the PMC?

Agreed. I like the idea too. Having pairs that are a little testvoc away
from release in the same place as pairs that have 20 lines of bidix is
both confusing and demotivating.

I'm for doing prereleases too; and not only because the first week after
a release you remember that all-important bug you forgot to fix... I
think it can be motivating to someone who's stuck in testvoc to get
something out there and hopefully some feedback.  Also, there are very
few releases compared to the amount of work going on in SVN; if nothing
else, I think more releases could be good for publicity...  Of course,
like svn moving, it should be up to the language pair maintainers.



--
Kevin Brubeck Unhammer


Sent from my emacs.

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Jimmy O'Regan]

2011/2/8 Gema Ramírez-Sánchez :
> So, correct if wrong...
>

Oh. Yeah. I guess we both forgot when we came to a compromise[1] that
we should update the status...

[1] If Fran and I can compromise on something, there's hope for
Palestine and Israel.

>  TRUNK: would contain pairs in "release" and "[alpha|pre]-release"
> status an no pair without a release.
>
>  STAGING: would contain pairs that builds and have an advanced status
> of all modules (dictionaries with closed cathegories and a decent
> coverage, an "ad hoc" PoS tagset and .prob, good coverage of main
> contrastive phenomena, testvoc clean, and a post-generator if needed).
> There should be a "PROBLEMS" file saying, IMO, status and major
> problems found while reading translations done with this pair (so, not
> a complete evaluation but a general compilation of big problems
> detected at the output). That could be a middle solution between Fran
> and Jim point of view. Would  [Alpha|Pre]-releases also be allowed for
> pairs in staging?
>

In this new model, yes, but the [Alpha|Pre]-releases thing is a separate matter.

I would also add the caveats that the move from incubator to
staging/nursery will only be done:
1) at the request of the maintainer
*or*
2) if development has lapsed for a period of not less than two months.

(I'm thinking specifically of trying to not cause problems for eo-fr,
which should probably just transition straight from incubator to
trunk).

> NURSERY: would contain pairs that build but that have not been
> developed deeply or maybe data copied from other pairs that needs work
> or very poor data on some modules, etc.
>

The basic requirements are that it should build without any external
effort, contain all basic elements (rule files, modes) even if they're
'dummies', and function, for a very relaxed meaning of 'function'
(word to word, generation marks allowed).

We want to have a 'safe' area, in which to solicit lexical
contributions. Potential contributors should be able to add words, and
have those words translate, but they should also be aware that we
expect some help in building the rules.

>  INCUBATOR: would contain pairs with pieces of translators
>

Well, just pieces. We have some things that are just analysers, with
no bilingual component.

Hopefully, this will also give a set of clear milestones, so new
contributors will have a better idea of the status of their pair, and
we'll know when a pat on the back is called for.

> I like the idea in general, how should we go ahead? making a proposal
> and submitting it to the PMC?
>
> r.
>
> Gema.
>
>
>
> On Tue, Feb 8, 2011 at 4:47 PM, Francis Tyers  wrote:
>> El dt 08 de 02 de 2011 a les 15:30 +, en/na Jimmy O'Regan va
>> escriure:
>>> On 8 February 2011 15:02, Francis Tyers  wrote:
>>> > El dt 08 de 02 de 2011 a les 14:53 +, en/na Jimmy O'Regan va
>>> > escriure:
>>> >> That's the problem, though. If we want feedback, saying 'get it from
>>> >> SVN' really reduces the amount of people who /can/ give us feedback.
>>> >
>>> > Hmm, I hadn't thought about that. Are there people who are capable of
>>> > installing/compiling Apertium etc. from source .tar.gz, but not from
>>> > source in SVN ?
>>> >
>>>
>>> 'Capable of' is a matter of argument. Certainly, the vast majority of
>>> casual SVN users would balk at following the stock instructions on
>>> sourceforge to find that they'd just pulled down 5 gigs.
>>
>> True.
>>
>>> >> I don't want to go quite to that extreme, but there
>>> >> should be a happy medium between that extreme and yours.
>>> >
>>> > Agree. Overall, I think "staging" should be for things that have the
>>> > prospect of being released after say, a few weeks (rather than a few
>>> > monts) of concerted effort by a newcomer.
>>>
>>> Still not close enough to be worth the effort, IMO, but as we never
>>> agree on any set of details[1], ever, rather than derail the
>>> discussion, we should probably consider either:
>>>
>>> 1) You write a counter-proposal, and we'll handle this like a proper
>>> bur^H^H^Hdemocracy
>>> 2) We prepare a 'scale of preparedness' and get... somebody else's input.
>>
>> I think (2) is a good option. :)
>>
>>> [1] Ok, not quite true: Beer, metal, Free Software FTW!, Macs are
>>> pretty but the OS sucks. Have I missed anything?
>>
>> :D
>>
>> Fran
>>
>>
>> --
>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>> Pinpoint memory and threading errors before they happen.
>> Find and fix more than 250 security defects in the development cycle.
>> Locate bottlenecks in serial and parallel code that limit performance.
>> http://p.sf.net/sfu/intel-dev2devfeb
>> ___
>> Apertium-stuff mailing list
>> Apertium-stuff@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>>
>



-- 
 jimregan, that's because deep inside you, you are evil.
 Also not-so-deep inside

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Francis Tyers]

El dt 08 de 02 de 2011 a les 18:12 +0100, en/na Gema Ramírez-Sánchez va
escriure:
> So, correct if wrong...
> 
>  TRUNK: would contain pairs in "release" and "[alpha|pre]-release"
> status an no pair without a release.

Example: apertium-br-fr

>  STAGING: would contain pairs that builds and have an advanced status
> of all modules (dictionaries with closed cathegories and a decent
> coverage, an "ad hoc" PoS tagset and .prob, good coverage of main
> contrastive phenomena, testvoc clean, and a post-generator if needed).
> There should be a "PROBLEMS" file saying, IMO, status and major
> problems found while reading translations done with this pair (so, not
> a complete evaluation but a general compilation of big problems
> detected at the output). That could be a middle solution between Fran
> and Jim point of view. Would  [Alpha|Pre]-releases also be allowed for
> pairs in staging?

Example: apertium-af-nl

> NURSERY: would contain pairs that build but that have not been
> developed deeply or maybe data copied from other pairs that needs work
> or very poor data on some modules, etc.

Example: apertium-no-en

>  INCUBATOR: would contain pairs with pieces of translators

Example: apertium-br-cy

> I like the idea in general, how should we go ahead? making a proposal
> and submitting it to the PMC?

+1 

Fran


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Gema Ramírez-Sánchez]

So, correct if wrong...

 TRUNK: would contain pairs in "release" and "[alpha|pre]-release"
status an no pair without a release.

 STAGING: would contain pairs that builds and have an advanced status
of all modules (dictionaries with closed cathegories and a decent
coverage, an "ad hoc" PoS tagset and .prob, good coverage of main
contrastive phenomena, testvoc clean, and a post-generator if needed).
There should be a "PROBLEMS" file saying, IMO, status and major
problems found while reading translations done with this pair (so, not
a complete evaluation but a general compilation of big problems
detected at the output). That could be a middle solution between Fran
and Jim point of view. Would  [Alpha|Pre]-releases also be allowed for
pairs in staging?

NURSERY: would contain pairs that build but that have not been
developed deeply or maybe data copied from other pairs that needs work
or very poor data on some modules, etc.

 INCUBATOR: would contain pairs with pieces of translators

I like the idea in general, how should we go ahead? making a proposal
and submitting it to the PMC?

r.

Gema.



On Tue, Feb 8, 2011 at 4:47 PM, Francis Tyers  wrote:
> El dt 08 de 02 de 2011 a les 15:30 +, en/na Jimmy O'Regan va
> escriure:
>> On 8 February 2011 15:02, Francis Tyers  wrote:
>> > El dt 08 de 02 de 2011 a les 14:53 +, en/na Jimmy O'Regan va
>> > escriure:
>> >> That's the problem, though. If we want feedback, saying 'get it from
>> >> SVN' really reduces the amount of people who /can/ give us feedback.
>> >
>> > Hmm, I hadn't thought about that. Are there people who are capable of
>> > installing/compiling Apertium etc. from source .tar.gz, but not from
>> > source in SVN ?
>> >
>>
>> 'Capable of' is a matter of argument. Certainly, the vast majority of
>> casual SVN users would balk at following the stock instructions on
>> sourceforge to find that they'd just pulled down 5 gigs.
>
> True.
>
>> >> I don't want to go quite to that extreme, but there
>> >> should be a happy medium between that extreme and yours.
>> >
>> > Agree. Overall, I think "staging" should be for things that have the
>> > prospect of being released after say, a few weeks (rather than a few
>> > monts) of concerted effort by a newcomer.
>>
>> Still not close enough to be worth the effort, IMO, but as we never
>> agree on any set of details[1], ever, rather than derail the
>> discussion, we should probably consider either:
>>
>> 1) You write a counter-proposal, and we'll handle this like a proper
>> bur^H^H^Hdemocracy
>> 2) We prepare a 'scale of preparedness' and get... somebody else's input.
>
> I think (2) is a good option. :)
>
>> [1] Ok, not quite true: Beer, metal, Free Software FTW!, Macs are
>> pretty but the OS sucks. Have I missed anything?
>
> :D
>
> Fran
>
>
> --
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Francis Tyers]

El dt 08 de 02 de 2011 a les 15:30 +, en/na Jimmy O'Regan va
escriure:
> On 8 February 2011 15:02, Francis Tyers  wrote:
> > El dt 08 de 02 de 2011 a les 14:53 +, en/na Jimmy O'Regan va
> > escriure:
> >> That's the problem, though. If we want feedback, saying 'get it from
> >> SVN' really reduces the amount of people who /can/ give us feedback.
> >
> > Hmm, I hadn't thought about that. Are there people who are capable of
> > installing/compiling Apertium etc. from source .tar.gz, but not from
> > source in SVN ?
> >
> 
> 'Capable of' is a matter of argument. Certainly, the vast majority of
> casual SVN users would balk at following the stock instructions on
> sourceforge to find that they'd just pulled down 5 gigs.

True.

> >> I don't want to go quite to that extreme, but there
> >> should be a happy medium between that extreme and yours.
> >
> > Agree. Overall, I think "staging" should be for things that have the
> > prospect of being released after say, a few weeks (rather than a few
> > monts) of concerted effort by a newcomer.
> 
> Still not close enough to be worth the effort, IMO, but as we never
> agree on any set of details[1], ever, rather than derail the
> discussion, we should probably consider either:
> 
> 1) You write a counter-proposal, and we'll handle this like a proper
> bur^H^H^Hdemocracy
> 2) We prepare a 'scale of preparedness' and get... somebody else's input.

I think (2) is a good option. :)

> [1] Ok, not quite true: Beer, metal, Free Software FTW!, Macs are
> pretty but the OS sucks. Have I missed anything?

:D 

Fran


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Jimmy O'Regan]

On 8 February 2011 15:02, Francis Tyers  wrote:
> El dt 08 de 02 de 2011 a les 14:53 +, en/na Jimmy O'Regan va
> escriure:
>> That's the problem, though. If we want feedback, saying 'get it from
>> SVN' really reduces the amount of people who /can/ give us feedback.
>
> Hmm, I hadn't thought about that. Are there people who are capable of
> installing/compiling Apertium etc. from source .tar.gz, but not from
> source in SVN ?
>

'Capable of' is a matter of argument. Certainly, the vast majority of
casual SVN users would balk at following the stock instructions on
sourceforge to find that they'd just pulled down 5 gigs.

>> > To be eligible for inclusion I would say that aside from the 'PROBLEMS
>> > file, it should also include an preliminary evaluation of translation
>> > quality (af-nl, ca-sc, pl-cs, sme-nob) have this.
>>
>> IMO, that defeats the purpose. It would make sense to have this
>> restriction on 'alpha' releases, though.
>
> I don't think it defeats the purpose so much. Doing a preliminary
> evaluation is less than a day's work, where finishing a testvoc might be
> a couple of weeks. I think things in staging should have some kind of
> eval. Even if it is just 30 sentences -- and even if it is automatic
> (from a parallel corpus or something). If you've got time to write a
> 'PROBLEMS' file, you've got time to do that.
>
>> The primary motivation I had in proposing this was that we have a
>> current need to distinguish between the modules that can be checked
>> out, built, and which can provide a basic word to word translation
>> (i.e., which a newcomer can add vocabulary to and expect to see that
>> vocabulary translate in some manner, regardless of correctness), and
>> those that can't.
>
> Agree. But there are several pairs that fall into this that I wouldn't
> call "staging".  You can get basic word-for-word translations with
> no-en, but it isn't something that I would put in staging yet -- far too
> much testvoquing left to do. And fo-is too, but that lacks coverage.
>

Those are exactly the things I want to consider.

>> I don't want to go quite to that extreme, but there
>> should be a happy medium between that extreme and yours.
>
> Agree. Overall, I think "staging" should be for things that have the
> prospect of being released after say, a few weeks (rather than a few
> monts) of concerted effort by a newcomer.

Still not close enough to be worth the effort, IMO, but as we never
agree on any set of details[1], ever, rather than derail the
discussion, we should probably consider either:

1) You write a counter-proposal, and we'll handle this like a proper
bur^H^H^Hdemocracy
2) We prepare a 'scale of preparedness' and get... somebody else's input.


[1] Ok, not quite true: Beer, metal, Free Software FTW!, Macs are
pretty but the OS sucks. Have I missed anything?

-- 
 jimregan, that's because deep inside you, you are evil.
 Also not-so-deep inside you.

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Francis Tyers]

El dt 08 de 02 de 2011 a les 14:53 +, en/na Jimmy O'Regan va
escriure:
> On 8 February 2011 14:36, Francis Tyers  wrote:
> > I like the idea in general.
> >
> > It gives more motivation for one. "I've done a bit of a dictionary, woo
> > I can get into incubator". But to get from incubator to trunk is a lot
> > of work. And if I stay in incubator i've not accomplished much. But if I
> > have a mostly working translator, but not quite enough coverage to
> > release then I can put it in staging and say "hey guys, this mostly
> > works, just needs some work".
> >
> > Here are the pairs I would move to staging now:
> >
> >  apertium-af-nl, -- basically ready to go, but there are probably some
> >easy errors that could be fixed if we look
> >carefully at the evaluation.
> >  apertium-ca-sc, -- needs linguistic revision of Sardinian,
> >and better coverage, but otherwise testvoc
> >clean and ready to go.
> >  apertium-es-an, -- huge improvement in coverage and linguistic quality
> >over the last version, just needs to be testvoqued.
> >  apertium-fr-pt, -- ready to go, testvoqued, but needs corpus test,
> >and probably some rule fixes.
> >  apertium-pl-cs, -- mostly testvoqued in the direction cs->pl, but
> >needs extensive work on disambiguation before
> >it becomes useful, also improved coverage.
> >  apertium-sme-nob - not possible to testvoc, but some minor corpus
> >errors remain.
> >
> > I'm not sure I like the idea of alpha/pre-releases though. If someone
> > wants a development version, they can use the SVN.
> >
> 
> That's the problem, though. If we want feedback, saying 'get it from
> SVN' really reduces the amount of people who /can/ give us feedback.

Hmm, I hadn't thought about that. Are there people who are capable of
installing/compiling Apertium etc. from source .tar.gz, but not from
source in SVN ?

> > To be eligible for inclusion I would say that aside from the 'PROBLEMS
> > file, it should also include an preliminary evaluation of translation
> > quality (af-nl, ca-sc, pl-cs, sme-nob) have this.
> 
> IMO, that defeats the purpose. It would make sense to have this
> restriction on 'alpha' releases, though.

I don't think it defeats the purpose so much. Doing a preliminary
evaluation is less than a day's work, where finishing a testvoc might be
a couple of weeks. I think things in staging should have some kind of
eval. Even if it is just 30 sentences -- and even if it is automatic
(from a parallel corpus or something). If you've got time to write a
'PROBLEMS' file, you've got time to do that.

> The primary motivation I had in proposing this was that we have a
> current need to distinguish between the modules that can be checked
> out, built, and which can provide a basic word to word translation
> (i.e., which a newcomer can add vocabulary to and expect to see that
> vocabulary translate in some manner, regardless of correctness), and
> those that can't. 

Agree. But there are several pairs that fall into this that I wouldn't
call "staging".  You can get basic word-for-word translations with
no-en, but it isn't something that I would put in staging yet -- far too
much testvoquing left to do. And fo-is too, but that lacks coverage.

> I don't want to go quite to that extreme, but there
> should be a happy medium between that extreme and yours.

Agree. Overall, I think "staging" should be for things that have the
prospect of being released after say, a few weeks (rather than a few
monts) of concerted effort by a newcomer. 

Fran


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Jimmy O'Regan]

On 8 February 2011 14:36, Francis Tyers  wrote:
> I like the idea in general.
>
> It gives more motivation for one. "I've done a bit of a dictionary, woo
> I can get into incubator". But to get from incubator to trunk is a lot
> of work. And if I stay in incubator i've not accomplished much. But if I
> have a mostly working translator, but not quite enough coverage to
> release then I can put it in staging and say "hey guys, this mostly
> works, just needs some work".
>
> Here are the pairs I would move to staging now:
>
>  apertium-af-nl, -- basically ready to go, but there are probably some
>                    easy errors that could be fixed if we look
>                    carefully at the evaluation.
>  apertium-ca-sc, -- needs linguistic revision of Sardinian,
>                    and better coverage, but otherwise testvoc
>                    clean and ready to go.
>  apertium-es-an, -- huge improvement in coverage and linguistic quality
>                    over the last version, just needs to be testvoqued.
>  apertium-fr-pt, -- ready to go, testvoqued, but needs corpus test,
>                    and probably some rule fixes.
>  apertium-pl-cs, -- mostly testvoqued in the direction cs->pl, but
>                    needs extensive work on disambiguation before
>                    it becomes useful, also improved coverage.
>  apertium-sme-nob - not possible to testvoc, but some minor corpus
>                    errors remain.
>
> I'm not sure I like the idea of alpha/pre-releases though. If someone
> wants a development version, they can use the SVN.
>

That's the problem, though. If we want feedback, saying 'get it from
SVN' really reduces the amount of people who /can/ give us feedback.

> To be eligible for inclusion I would say that aside from the 'PROBLEMS'
> file, it should also include an preliminary evaluation of translation
> quality (af-nl, ca-sc, pl-cs, sme-nob) have this.

IMO, that defeats the purpose. It would make sense to have this
restriction on 'alpha' releases, though.

The primary motivation I had in proposing this was that we have a
current need to distinguish between the modules that can be checked
out, built, and which can provide a basic word to word translation
(i.e., which a newcomer can add vocabulary to and expect to see that
vocabulary translate in some manner, regardless of correctness), and
those that can't. I don't want to go quite to that extreme, but there
should be a happy medium between that extreme and yours.

-- 
 jimregan, that's because deep inside you, you are evil.
 Also not-so-deep inside you.

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Francis Tyers]

El dt 08 de 02 de 2011 a les 14:24 +, en/na Jimmy O'Regan va
escriure:
> We've hashed this out a little on IRC, but I want to make the
> proposals more broadly visible.
> 
> 1) Alpha releases
> 
> We have a number of 'incubator' translators that are complete, but not
> fully testvoced, that could benefit from feedback.
> I propose that we make prerelease versions of these translators
> available, with a clear marking in the version to show these are not
> full releases.
> 
> 1a) What should we use: 'pre' or 'alpha'?
> 
> 1b) Should we extend this to existing translators? en-es, for example,
> has had a lot of vocabulary added since the last release, but there
> are definitely problems with that vocabulary.
> 
> -
> 
> 2) 'Staging' in SVN
> 
> The incubator module in SVN has, on the whole, been quite successful,
> but the range of development statuses is problematic.
> I propose that we split incubator into 'incubator' and 'staging'[1].
> 
> Incubator would remain the place for 'sketches' -- pieces of
> analysers/bilingual lexicons
> Staging would become the place for anything that can build and run,
> but is still quite far from release-worthy.
> 
> This could mean anything from 'Apertium is missing X' (e.g., cs-pl),
> or 'we've done as much as we can, but need a native speaker to fill
> the gaps in our knowledge', as long as the module can honestly be
> described as 'basically working'.
> 
> 2b) To be eligible for inclusion in staging, the module must include a
> text file (perhaps 'PROBLEMS') that clearly explains (in brief) the
> status of the module.
> 
> I want to make it clear that I'm thinking about different criteria for
> inclusion in both proposals: current incubator modules that could be
> made available as prereleases, that are being actively worked on,
> should *not* go into staging (eo-fr, es-an), and should just go
> straight to trunk when ready.

I like the idea in general.

It gives more motivation for one. "I've done a bit of a dictionary, woo
I can get into incubator". But to get from incubator to trunk is a lot
of work. And if I stay in incubator i've not accomplished much. But if I
have a mostly working translator, but not quite enough coverage to
release then I can put it in staging and say "hey guys, this mostly
works, just needs some work". 

Here are the pairs I would move to staging now: 

 apertium-af-nl, -- basically ready to go, but there are probably some 
easy errors that could be fixed if we look
carefully at the evaluation.
 apertium-ca-sc, -- needs linguistic revision of Sardinian, 
and better coverage, but otherwise testvoc 
clean and ready to go.
 apertium-es-an, -- huge improvement in coverage and linguistic quality
over the last version, just needs to be testvoqued.
 apertium-fr-pt, -- ready to go, testvoqued, but needs corpus test,
and probably some rule fixes.
 apertium-pl-cs, -- mostly testvoqued in the direction cs->pl, but 
needs extensive work on disambiguation before
it becomes useful, also improved coverage.
 apertium-sme-nob - not possible to testvoc, but some minor corpus
errors remain.

I'm not sure I like the idea of alpha/pre-releases though. If someone
wants a development version, they can use the SVN. 

To be eligible for inclusion I would say that aside from the 'PROBLEMS'
file, it should also include an preliminary evaluation of translation
quality (af-nl, ca-sc, pl-cs, sme-nob) have this.  And to reach a
certain level of coverage (e.g. over 70% -- arbitrary figure -- what I
mean is that the closed categories be mostly done and lots of the
paradigms too).

Fran


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Proposal: alpha releases/'staging' area in SVN

[Jimmy O'Regan]

We've hashed this out a little on IRC, but I want to make the
proposals more broadly visible.

1) Alpha releases

We have a number of 'incubator' translators that are complete, but not
fully testvoced, that could benefit from feedback.
I propose that we make prerelease versions of these translators
available, with a clear marking in the version to show these are not
full releases.

1a) What should we use: 'pre' or 'alpha'?

1b) Should we extend this to existing translators? en-es, for example,
has had a lot of vocabulary added since the last release, but there
are definitely problems with that vocabulary.

-

2) 'Staging' in SVN

The incubator module in SVN has, on the whole, been quite successful,
but the range of development statuses is problematic.
I propose that we split incubator into 'incubator' and 'staging'[1].

Incubator would remain the place for 'sketches' -- pieces of
analysers/bilingual lexicons
Staging would become the place for anything that can build and run,
but is still quite far from release-worthy.

This could mean anything from 'Apertium is missing X' (e.g., cs-pl),
or 'we've done as much as we can, but need a native speaker to fill
the gaps in our knowledge', as long as the module can honestly be
described as 'basically working'.

2b) To be eligible for inclusion in staging, the module must include a
text file (perhaps 'PROBLEMS') that clearly explains (in brief) the
status of the module.

I want to make it clear that I'm thinking about different criteria for
inclusion in both proposals: current incubator modules that could be
made available as prereleases, that are being actively worked on,
should *not* go into staging (eo-fr, es-an), and should just go
straight to trunk when ready.


[1] I took the name from the kernel, I'm not totally sold on it.

-- 
 jimregan, that's because deep inside you, you are evil.
 Also not-so-deep inside you.

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff