Moses-support Digest, Vol 103, Issue 40

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. Which symal? (Jeroen Vermeulen)
2. Re: Which symal? (Ergun Bicici)
3. New source formatter & checker (Jeroen Vermeulen)


----------------------------------------------------------------------

Message: 1
Date: Sun, 17 May 2015 19:15:19 +0700
From: Jeroen Vermeulen <jtv@precisiontranslationtools.com>
Subject: [Moses-support] Which symal?
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID: <55588657.2040106@precisiontranslationtools.com>
Content-Type: text/plain; charset=utf-8

The symal source code is duplicated between the moses-smt and mgiza
repositories. Does it make sense to have both? They're quietly
diverging, which is probably a bad thing.

Here's the differences that I can see:
* I modernized the code in moses-smt. Big diff, no functional change.
* The moses-smt version supports longer source and target strings.
* The mgiza version has what looks like some extra debug output.
* The moses-smt version avoids non-portable use of /dev/stdout.
* One builds through bjam, the other through cmake.

Could we perhaps just delete the mgiza one, and tell people to use the
one from moses instead?


Jeroen


------------------------------

Message: 2
Date: Sun, 17 May 2015 13:47:30 +0100
From: Ergun Bicici <Ergun.Bicici@computing.dcu.ie>
Subject: Re: [Moses-support] Which symal?
To: Jeroen Vermeulen <jtv@precisiontranslationtools.com>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAB2pGneBmGsyrDCY7_b8p8OD=Fxq2PjtS4OSXZgFn9MDMbO5vg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Moses' symal:
http://article.gmane.org/gmane.comp.nlp.moses.user/11544


Best Regards,
Ergun

Ergun Bi?ici, CNGL, School of Computing, DCU, www.cngl.ie
http://www.computing.dcu.ie/~ebicici/


On Sun, May 17, 2015 at 1:15 PM, Jeroen Vermeulen <
jtv@precisiontranslationtools.com> wrote:

> The symal source code is duplicated between the moses-smt and mgiza
> repositories. Does it make sense to have both? They're quietly
> diverging, which is probably a bad thing.
>
> Here's the differences that I can see:
> * I modernized the code in moses-smt. Big diff, no functional change.
> * The moses-smt version supports longer source and target strings.
> * The mgiza version has what looks like some extra debug output.
> * The moses-smt version avoids non-portable use of /dev/stdout.
> * One builds through bjam, the other through cmake.
>
> Could we perhaps just delete the mgiza one, and tell people to use the
> one from moses instead?
>
>
> Jeroen
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150517/7a9443c7/attachment-0001.htm

------------------------------

Message: 3
Date: Sun, 17 May 2015 20:13:43 +0700
From: Jeroen Vermeulen <jtv@precisiontranslationtools.com>
Subject: [Moses-support] New source formatter & checker
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID: <55589407.6040402@precisiontranslationtools.com>
Content-Type: text/plain; charset=utf-8

Hi all,

We have a replacement for the old beautify.perl script:
scripts/other/beautify.py.

It does one of two things, or both:
* Re-format C/C++ source code, just like the old script did.
* Check for style errors and such.

This last thing is called a "lint" check. For this I chose Pocketlint,
a checker I have good experiences with, although if people want a
different one (or additional checks) I can change that.

I fixed most of the lint that got reported, except in JavaScript code.
We may add automatic reformatting for additional languages later. I
sincerely hope all of this does not cause any serious merge problems for
your branches.

Ideally, everyone would get in the habit of installing Pocketlint and
running this script regularly whether they accidentally added any lint.
To see how the script works, run:

./scripts/other/beautify.py -h

The lint check processes a few files at a time. By default it stops
when it sees lint. If you want to see a full check, use the -i option.


Jeroen


------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 103, Issue 40
**********************************************

Tweet