Re: Digest for ploversteno@googlegroups.com - 17 Messages in 2 Topics

[bob purinton]

Can I search Plover's dictionary?

are the Plover dictionary entries sorted alphabetically anywhere by strokes or translations?

any help on this will be greatly appreciated!

Thanks,

Bob 

On Tue, Apr 30, 2013 at 2:02 AM, <plove...@googlegroups.com> wrote:

  Today's Topic Summary

Group: http://groups.google.com/group/ploversteno/topics

• Help wanted: debian package for plover [15 Updates]
• Which dictionary is plover based on? [2 Updates]

 Help wanted: debian package for plover

Daniel Langlois <danlan...@gmail.com> Apr 29 12:14AM -0700  

I note this, from https://github.com/plover/plover:
---
These installation notes are for Debian-like Linux systems. From the
directory in which this README file is located, run the following commands:
 
sudo apt-get install python-xlib python-serial python-wxgtk2.8 appdirs
sudo python setup.py install
---
 
And, appdirs is not in Debian.
 
This has come up, as here:
https://groups.google.com/forum/?fromgroups=#!topic/ploversteno/7Vfb_3ixaqg
---
Hesky Fisher
Apr 7
 
 
Hi Varid and Brent,
 
I'm sorry you are having trouble installing plover. The real solution to
this problem will be to have a debian package that people can use to
install plover. Something like: apt-get install plover. Hopefully we will
have that soon.
 
Until then, appdirs is a python package that plover depends on. Many python
packages are not available via apt-get and need to be installed via pip or
something similar. We'll need to update the instructions. We will also need
to update the install guide because the version of plover linked to on
launchpad is out of date.
 
Hesky
---
 
 
I'd like to construe the issue, as one of automatically
find/download/install/upgrading dependencies at build time. More generally,
our goal is to distribute a Python package that has several other widely
used Python packages as dependencies.
 
 
 
What about pip/virtualenv. That is, installing pip and virtualenv, and then
figuring out how these tools work, and how they are different.
 
Here:
https://groups.google.com/forum/?fromgroups=#!searchin/ploversteno/pip/ploversteno/O8eUhHVegEk/zu-7TMUbl-EJ
---
I grabbed the zip from the dictupdate branch, and had some difficulties
installing. Thought you might want to know.
 
1) Appdirs. Several people have mentioned this as being a problem, but
just for clarity, the solution on Ubuntu is to install pip "sudo apt-get
install python-pip", and then use pip to install appdirs "sudo pip install
appdirs".
---
 
Is there a way to distribute software in a way that doesn't depend on users
having to chase down all these dependencies and versions? To, perhaps,
compile all the relevant packages into something self-contained, that can
just be downloaded and used as a binary? This issue happens even when all
of our Python package dependencies are well-known, well-written and
well-maintained Pypi-available packages.
 
And, I get it, that the idea you have in mind, is that for the end user,
the installation process will be sudo apt-get install some_python_package
or sudo pacman -S some_python_package, however their package manager works.
This is sensible. But there will need to be a bootstrap script, or
something. This could download something for managing remote installations,
and then build, and install, our package + deps.
 
I have created a little Debian package, a 'single binary'. I've run the
Debian package checker on the package, it shows me a list of errors and
warnings, such as, I didn't create a man page. But the last test of the
package is to install it and run it. Which, it asks for appdirs :)
 
 
 
 
On Sunday, April 28, 2013 3:36:02 PM UTC-7, Hesky Fisher wrote:


 

Daniel Langlois <danlan...@gmail.com> Apr 29 12:57AM -0700  

To sum up, in my previous post I described building a .deb, and doing so, I
got a fresh perspective on the problem of more easily building and
distributing Python packages, especially ones that have dependencies on
other packages. Here are some further notes:
 
*Here is the idea, can we produce eggs, upload to PyPI, and automatically
include all packages in the directory where the setup.py lives. Answer:
yes. *
 
I mention releasing Plover to PyPI, has this been considered? Yes.
https://groups.google.com/forum/?fromgroups=#!searchin/ploversteno/pypi/ploversteno/ASNmkVTeqtQ/T8DBcb8EC7EJ
Kevin Tran
11/8/11
Will Plover be uploaded to PyPI eventually?
 
*Is there something that supports automatically installing dependencies
when a package is installed, and including information about dependencies
in Python Eggs (so that package management tools like EasyInstall can use
the information)? Answer: Yes. *
 
 
I think we might download 'distribute_setup.py':
http://nightly.ziade.org/distribute_setup.py
 
And, put it in the same directory as your setup.py script.
That means, it literally goes into Github here:
https://github.com/plover/plover
 
Then add these two lines to the very top of your setup script:
import distribute_setup
distribute_setup.use_setuptools()
 
Then, in the case of users not having setuptools installed on their
machines, the distribute_setup module will automatically download a
matching version of setuptools from PyPI.
 
There is also a PyPI 'upload' command--you can use 'setup.py sdist upload'
or 'setup.py bdist_egg upload' to upload your source or egg distributions
respectively.
 
I'll mention setup.py register, and then I'll mention:
setup.py register sdist bdist_egg upload
 
This will register the package, build source and egg distributions, and
then upload them both to PyPI.
 
 
These are just notes, at this point, had a little progress..
 
On Monday, April 29, 2013 12:14:19 AM UTC-7, Daniel Langlois wrote:


 

Thomas Thurman <tho...@thurman.org.uk> Apr 29 09:04AM +0100  

> osx <https://github.com/plover/plover/tree/master/osx>.
 
> Launchpad PPA is certainly an attractive option and we can explore using
> it. But using it comes strictly after creating the source package.
 
I made the original ITP, but work got in the way. Then another person
on this list (I forget who) said he'd rather make the .deb, but that
seemed to come to nothing. I'm happy to give it another go this week,
if people would like. If anyone would like to help, all the better!
 
T


 

Hesky Fisher <hesky....@gmail.com> Apr 29 11:19AM -0400  

Hi Daniel,
 
I'm not sure what the right answer is for appdirs. It is a dependent
package that does not have a debian package. I'm hoping there is a standard
method for dealing with this kind of problem somewhere.
 
I believe that debian frowns on downloads being needed as part of the
installation process of packages.
 
Hesky
 
 


 

Hesky Fisher <hesky....@gmail.com> Apr 29 11:20AM -0400  

Hi Thomas,
 
If you could work on this then that would be much appreciated.
 
Thanks,
Hesky
 
 


 

Jeremy Kahn <tro...@trochee.net> Apr 29 08:50AM -0700  

I believe the recommended approach would be to help "appdir" release their
package to Debian or at least a PPA.
 
Less preferred, but still workable, would be to bundle the appropriate
version of appdir into the deb package for plover.


 

Hesky Fisher <hesky....@gmail.com> Apr 29 12:09PM -0400  

Hi Jeremy,
 
Thanks for the response!
 
Since option one is preferred I opened an issue with them to see if they
are interested: https://github.com/ActiveState/appdirs/issues/29
 
In the meantime, I think we should push ahead with option two and bundle
appdirs in our package so that we are not slowed down.
 
Hesky
 


 

Daniel Langlois <danlan...@gmail.com> Apr 29 09:11AM -0700  

For what it's worth, here's a .deb, taking the approach of automatically
installing PYPI dependencies. Anyways, it's a .deb, what one looks like,
and it's something to test on somebody else's machine. A .deb file is
installed with this: sudo dpkg -i plover_1.1-3_i386.deb
 
There's then a script at /usr/local/bin/plover
 
There are a couple of threads to disentangle, here. There's the matter of
having a debian package, including having a make target for that..also,
there are the modifications to automatically install dependencies (what I
got into discussing for this, above, I have implemented, but I'll come back
around w/maybe a simple pull request).
 
 
 
 
 
On Monday, April 29, 2013 10:50:01 AM UTC-5, Jeremy K wrote:


 

Hesky Fisher <hesky....@gmail.com> Apr 29 12:16PM -0400  

Thanks Daniel!
 
Could you also share the source package that you used to make this?
 
Right now setup.py manages the installation of the application. It seems
like setup.py should handle installing the python code as a python module
but something else should actually do the OS parts.
 
 
 
 


 

Daniel Langlois <danlan...@gmail.com> Apr 29 11:42AM -0700  

https://github.com/DanLanglois/PloverDebianPackage
 
This is my source package--it's 7 megs. If you compare it to Plover as
represented in Github, there are some new folders, there is the debian
folder, and I've discussed, a bit, the contents of this. At the moment,
it's got lots of default configurations. there is a 'copyright' file, for
example, and a 'changelog'. The files are normal to see in this 'debian'
directory, and you have a 'debian' directory, for making a debian package.
The debian make file is in there, it's called 'rules'.
 
Besides the 'debian' directory, there's a 'Makefile'. If you do 'make all',
you'll see my 'make buildsrc' listed. 'sudo make buildsrc' will make a
debian .deb. A build folder will appear here, in that case, as well. The
.deb, is dropped up one directory, along with a .build file, a .changes
file. Also in here, is a distribute-0.6.36-py2.7.egg, and
distribute-0.6.36.tar.gz. Also, running make will download these files, if
they are missing. I've added lines to setup.py, calling distribute_setup.py
(also a new file).
 
There's a plover.egg-info directory. this directory is also created by the
debian make target. So, in sum, there's something to peruse here. It works
'on my machine', but I made a number of provisional decisions.
 
What is it--it has a Maketarget that creates a Debian package, basically.
There's a 'dist' folder, that contains a plover egg. This also is
created.
 
There are, then, multiple moving new parts, here. This may be perused for
reference, I hope it's progress, towards adding debian packaging to plover.
 
On Monday, April 29, 2013 11:16:20 AM UTC-5, Hesky Fisher wrote:
 
On Monday, April 29, 2013 11:16:20 AM UTC-5, Hesky Fisher wrote:


 

Hesky Fisher <hesky....@gmail.com> Apr 29 03:14PM -0400  

Hi Daniel,
 
Thanks again for sharing.
 
I think something went wrong in the build process though. I extracted the
.deb file you sent with ar but there doesn't seem to be any of plover in
there. I think the only files that made it into the .deb are the debian
specific files.
 
Hesky
 
 


 

Daniel Langlois <danlan...@gmail.com> Apr 29 02:58PM -0700  

Yes, oops. It turns out, that though the extraction procedure is trivial,
you copy three files, and run 'dpkg-source -x plove_1.1-1.dsc'. This is a
summary of the contents of the source code.
 
The .deb is, it seems, just a completed binary package.
plover_1.1-1.debian.tar.gz contains our debian directory contents. There is
also an original upstream source code tarball. I've attached this,
'plover-1.1.orig.tar.gz'.
 
So actually, nothing went wrong with the build process, but w/my general
inexperience, I can't say much of anything more about the details of fixing
upstream sources. There is a program that offers a basic method for
recording modifications to the upstream source for Debian packages. One
thing that I have encountered, is that while I thought most third-party
software installed itself in the /usr/local directory hierarchy, and same
w/Plover, on Debian this is reserved for private use by the system
administrator. Rather than, as they say, obeying the Filesystem Hierarchy
Standard, we can always sudo (it seems that actually this is the m.o.).
 
Beyond knowing something of the required files, and other files, under the
debian directory, I haven't read much. Funny thing, I knew to check the
package for errors, it wasn't actually *missing the full source!* I was
running debian test scripts that were green :)
On Monday, April 29, 2013 2:14:41 PM UTC-5, Hesky Fisher wrote:


 

Daniel Langlois <danlan...@gmail.com> Apr 29 04:14PM -0700  

Is this an interesting question-->whether a single file deployment with all
binaries (extension modules and their dependencies) packed into the
executable, is possible?
 
On Monday, April 29, 2013 2:58:51 PM UTC-7, Daniel Langlois wrote:


 

Hesky Fisher <hesky....@gmail.com> Apr 29 09:22PM -0400  

It's certainly possible. That's how we do our mac and windows releases. But
I'm not sure if that's the way debian releases are supposed to work.
 
 


 

Jeremy Kahn <tro...@trochee.net> Apr 29 08:24PM -0700  

See the legalistic (some might say Talmudic!) Debian Python Policy for
answers, especially chapters two and three.
 
http://www.debian.org/doc/packaging-manuals/python-policy/
 
(The analogy is imperfect, because the DPP needs its own Talmud:
commentary, tutorials and subtitles.)


 

 Which dictionary is plover based on?

mtac23 <markjas...@gmail.com> Apr 29 11:10AM -0700  

Reading this, could I possibly view in text format the Student
Dictionaries in the Stenovations' Download section? This is just so I
can have a resource material on Philly Clinic theory.
 


 

Mirabai Knight <askel...@gmail.com> Apr 29 02:25PM -0400  

The DigitalCAT student dictionary downloads are DCT files,
DigitalCAT's proprietary format, so you'll have to open it in
DigitalCAT, export it in rtf/cre format, and then either view it with
something like Vim (which will show you all the markup, unlike Word,
which will just show you all the words squashed together without
markup or spaces), or get it converted into JSON format, if you want
to use it with Plover.
 
Incidentally, the Plover dictionary is a synthesis of NYCI and StenEd
theory, with a few tens of thousands of my own additions sprinkled in.
It's basically just a direct export of my own personal working
dictionary, after six years of CART and two years of offline
captioning.
 
 
--
Mirabai Knight, CCP, RPR, CBC
StenoKnight CART Services
917 576 4989
m...@stenoknight.com
http://stenoknight.com


 

You received this message because you are subscribed to the Google Group ploversteno.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "Plover" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ploversteno...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Hesky Fisher]

Hi Bob,

We are still working on the dictionary tools so we don't have a nice way to do what you describe inside plover.

However, I've attached a file that you can open up in Excel or other spreadsheet program. This has the dictionary in two columns. The first one is stroke and the second is translation. You should be able to sort by either and alsop be able to search within this file.

I hope this helps.

Hesky