[liblouis-liblouisxml] Re: UEB August 13
- From: Ken Perry <kperry@xxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Wed, 27 Aug 2014 11:36:25 +0000
One warning on the files I sent. Because we do not capitalize our characters
you need to capitalize our results to compare to duxbury. This includes things
like brackets. I still wonder if Liblouis should not do like Duxbury and
capitalize the results. I realize that would break people using the current
liblouis. I find we end up converting them so we don't get the wrong dot 7
through but maybe there should be a flag in liblouis to capitalize the results.
What do you think?
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Joseph Lee
Sent: Wednesday, August 27, 2014 7:33 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: UEB August 13
Hi,
In the meantime, I'll add test data based on actual UEB rulebook examples
(there are plenty of them).
Cheers,
Joseph
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar Hameed
Sent: Wednesday, August 27, 2014 4:26 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: UEB August 13
Hi Ken,
Fully understood.
Hopefully now that we have a much better amount of reliable test data (thanks
for the other email), I can start to convert the files you provided into
harness tests, after which I can have a proper stab at:
http://liblouis.org/todo/deduplicate_ueb_tables/
Once we have one UEB table instead of three, it should be much simpler to
identify, fix and add test data.
I don't have enough time between now and sept 1st to start addressing this, but
touch wood this can be done before the next release in 3 months time.
thanks,
Mesar
On Wed 27/08/14,10:55, Ken Perry wrote:
> Well in truth if it was just Joseph and I that I want to combine we
> can
even do it on github by fetching from each other's branches. As it expands out
though if we want 3 or 4 peoples fixes it gets ugly quick.
>
> Ken
>
> -----Original Message-----
> From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar
> Hameed
> Sent: Tuesday, August 26, 2014 9:10 AM
> To: liblouis-liblouisxml@xxxxxxxxxxxxx
> Subject: [liblouis-liblouisxml] Re: UEB August 13
>
> Hi Ken, Joseph,
>
> In addition to what Bert already wrote.
> This is exactly the point of having the bitbucket staging repo, so
> that Us
three can work together on those branches with possible trial/error commits,
and once things have settled down they can be cleaned up and submitted as a
single patch to the official liblouis repo.
>
> The repo on bitbucket is just an example, the same setup can be
> created
with anything that you can host a git repo on.
>
> you can just add a git remote to your local git repo to interact with
different locations.
>
> Best,
> Mesar
> On Tue 26/08/14,13:15, Bert Frees wrote:
> > Hi Ken and Joseph,
> >
> > Yes you guys have a point. If you want to combine several unofficial
> > changes there's no other option then to wait for them to be accepted
> > on the main branch. Again, in the future this process should become
> > more smoothly!
> >
> > @Joseph, if you want to make such a snapshot, now is maybe not a
> > good timing because we're so close to an official release.
> >
> > Best,
> > Bert
> >
> >
> > Ken Perry writes:
> >
> > > This is a problem if your trying to try out other peoples changes
> > > with yours though. I will see what I can do with this new
> > > situation but I would hate to see APH split off and fork just to
> > > keep our own master so that we can have all the newest stuff
> > > before a
release.
> > >
> > > Ken
> > >
> > > -----Original Message-----
> > > From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> > > [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of
> > > Bert Frees
> > > Sent: Tuesday, August 26, 2014 5:06 AM
> > > To: liblouis-liblouisxml@xxxxxxxxxxxxx
> > > Subject: [liblouis-liblouisxml] Re: UEB August 13
> > >
> > > Hi Ken,
> > >
> > > Although we've all got busy day jobs, the rate of contributions is
> > > not one that we can't manage with 3 persons. However I do
> > > recognize there is a problem. I think it's mainly a matter of
> > > miscommunication between maintainers and contributors.
> > >
> > > We have some ideas about managing contributions but we're
> > > currently failing to get those ideas across to you guys. There
> > > should be more feedback from us and we should make more clear what
> > > we expect from table authors. We're working on that. If we've left
> > > some of you out in the cold, I apologize for that.
> > >
> > > Anyway, please don't panic if your pull requests aren't accepted
> > > right away. The only thing that really counts is that they will be
> > > included in the next release. In between releases it doesn't
> > > really matter whether your stuff is in the main repository because
> > > we're not in the subversion era anymore. At any time you can make
> > > your
own "release"
> > > with a simple URL:
> > >
"https://github.com/<your_username>/liblouis/tarball/<your_branch_or_commit_
hash>"
> > >
> > > Also, because from now on releases will follow each other
> > > relatively quickly (every 3 months), even if your change doesn't
> > > make it into a release, you will have to wait at most six months
> > > in total for it to eventually be incorporated, which is about the
> > > same
time as before.
> > >
> > >
> > > Thanks,
> > > Bert
> > >
> > >
> > >
> > > Ken Perry writes:
> > >
> > >> I made a pull request on Liblouis on August 13 that update the
> > >> old UEB tables to fix a few problems. Nothing has happened with
> > >> that pull request. I am just wondering what is going on with it
> > >> because my boss is asking why my changes had not yet made it in.
> > >> If I screwed something up in the pull request that is cool I can
> > >> fix it but if it is just we don't have the amount of maintainers
> > >> we need to keep the clean flow of requests that might be another
issue.
> > >>
> > >> Ken
> > >
> > > For a description of the software, to download it and links to
> > > project pages go to http://www.abilitiessoft.com For a description
> > > of the software, to download it and links to project pages go to
> > > http://www.abilitiessoft.com
> >
> > For a description of the software, to download it and links to
> > project pages go to http://www.abilitiessoft.com
> For a description of the software, to download it and links to project
> pages go to http://www.abilitiessoft.com
For a description of the software, to download it and links to project pages go
to http://www.abilitiessoft.com
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
