[GitHub] incubator-joshua pull request #36: Demo
Github user hsaputra commented on a diff in the pull request: https://github.com/apache/incubator-joshua/pull/36#discussion_r73449163 --- Diff: src/main/java/org/apache/joshua/server/ServerThread.java --- @@ -225,15 +225,18 @@ private void handleMetadata(String meta, JSONMessage message) { String source = argTokens[1]; String target = argTokens[2]; String featureStr = ""; + String alignmentStr = ""; if (argTokens.length > 3) featureStr = argTokens[3]; - + if (argTokens.length > 4) +alignmentStr = " ||| " + argTokens[4]; --- End diff -- What is this `alignmentStr` argument for ? Wonder if we could add test for this new argument --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Podling Report Reminder - August 2016
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 August 2016, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, August 03). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/August2016 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[GitHub] incubator-joshua pull request #:
Github user mjpost commented on the pull request: https://github.com/apache/incubator-joshua/commit/0663a9c7f704e1fc911d1792910ca9337840553b#commitcomment-18511694 @KellenSunderland do you have a minute to look at this? I thought this had passed CI tests, but Travis [is now telling me](https://travis-ci.org/apache/incubator-joshua/builds/148722346) that it didn't. It runs fine on my OS X machine and on a Linux machine I have access to, but seems to fail the generic test here. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-joshua pull request #36: Demo
GitHub user mjpost opened a pull request: https://github.com/apache/incubator-joshua/pull/36 Demo Made some improvements to the Joshua demo under demo/. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjpost/incubator-joshua demo Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-joshua/pull/36.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #36 commit c465e71530eecead797f73c06da25f1c0cff28ed Author: Matt PostDate: 2016-08-02T13:08:42Z fiddling with demo commit 1038a144468b48408f3eca1122efb3c8f84e4537 Author: Matt Post Date: 2016-08-02T13:41:39Z quick add rules for OOVs, format fiddling commit aedeafd0df1a30ecf686193cd9446ba7e569e84f Author: Matt Post Date: 2016-08-02T16:14:22Z HTTP server now projects case commit 3387b16befb1e8121a05e7b3a13d041bdeb7260b Author: Matt Post Date: 2016-08-02T16:19:44Z fixed to work with detokenized output commit ca6fc49dc853ea07189e65b2df9e77f36bbfd7dd Author: Matt Post Date: 2016-08-02T16:20:03Z denormalizes output commit 84301b9f04b3ffeecf35432309b1ca762c692313 Author: Matt Post Date: 2016-08-02T16:20:10Z remove sentence marker commit 81b33d2218e51bc70f3ef42c2f0cd3c0d3059340 Author: Matt Post Date: 2016-08-02T16:38:27Z added alignment point in custom rules --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---