When replying, please edit your Subject line so it is more specific than "Re: Contents of pspp-dev digest..."
1. Re: Translator credits in AUTHORS file (Ben
Pfaff) 2. New Dutch PO file for 'pspp' (version 0.7.9) (Translation Project Robot) 3. Re: problem with this file (Ben Pfaff) 4. Re: New Dutch PO file for 'pspp' (version 0.7.9) (Ben Pfaff) 5. Re: Ascii Driver Patches (Ben Pfaff) 6. Re: problem with this file (Harry Thijssen) 7. Re: [ronaldo.baltar@...: Re: How to Insert cases using PSPPIRE?] (Ben Pfaff) 8. Re: Ascii Driver Patches (John Darrington)
> The translators listed in AUTHORS is currently out of date. > > Now that we're getting quite a few localisations, it's becoming > hard to maintain these. Since the pspp.pot file contains a > "translator-credits" key, it's somewhat redundant anyway. > > I suggest that we remove the translators from AUTHORS. Any >
Sounds reasonable to me. I don't think that other GNU packages list translators in AUTHORS.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'pspp' has been submitted by
the Dutch team of translators. The file is available at:
(We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
Please consider including all of these in your next release, whether official or a pretest.
Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context.
The following HTML page has been updated:
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the name of your translation coordinator. <coordinator@...>
Message: 3 Date: Sun, 26 Feb 2012 10:09:51 -0800 From: Ben Pfaff <blp@...> To: Harry Thijssen <pspp@...> Cc: pspp-dev@... Subject: Re: problem with this file Message-ID: <87wr79lb4g.fsf@...> Content-Type: text/plain; charset=us-ascii
I don't think I have the file mentioned in this thread for testing. Can you send me (or the list) a copy?
Message: 4 Date: Sun, 26 Feb 2012 10:02:25 -0800 From: Ben Pfaff <blp@...> To: pspp-dev@... Subject: Re: New Dutch PO file for 'pspp' (version 0.7.9) Message-ID: <8762etmq1a.fsf@...> Content-Type: text/plain; charset=us-ascii
think I finally tracked down a bug in the ascii driver which has been annoying me for > years. The bug is difficult to reproduce, since it manifests itself only when output > is to the terminal and exactly if and when it occurs is likely to be dependent on the > terminal's dimensions. > > However I think the attached patches solve the problem. I'm sending them here for review > before I check them in.
These all look reasonable to me. I didn't compile or test them. Thanks for spotting the problem. -- Ben Pfaff http://benpfaff.org
My "gut feeling" is that the new sheet is probably usable now. My current to-do list is:
Keyboard interface needs work.
* Running syntax is too slow when there are many columns.
* Empty sheets could look better.
* Case numbers shouldn't scroll off-window.
Do you have anything else? If not, and if you don't think any of those are important enough to delay getting user feedback, then I'll start on cleanup this week (rather than on features etc.) and when I think it's ready I'll ask for you to review the code. I think you should have as much time as you need to review it. If I take a week for cleanup and you take a week for review, then maybe the new sheet is two weeks out, total?
> Ben, > > I looked at this problem some time
ago, but decided that an elegant solution > would not be trivial. Then you started your psppsheet re-implementation so > I decided to leave it. > > When do you estimate the new sheet will be stable enough for general public > consumption? In other words, do you think it's worth doing a quick and > nasty fix to the current sheet as a stopgap measure (and risking the > consequences) or should we wait for the new sheet? > > What's your gut feeling? > > J' > > ----- Forwarded message from Ronaldo Baltar <ronaldo.baltar@...> ----- >> I found a problem when inserting cases directly using PSPPIRE, maybe >> I'm doing something wrong. >> >> No. You're not doing anything wrong. This is a bug which
will be fixed in the >> new psppsheet implementation (coming soon). >> >> In the meantime, I suggest you work-around it by using the Insert-Cases function and >> then deleting the last case, if appropriate. >> >> J' > > I'll try your suggestion, but PSPP will be easier to teach to my > students when this limitation with psppsheet is solved. > > Ronaldo Baltar > Departamento de Ciencias Sociais > Universidade Estadual de Londrina > Parana - Brasil > > _______________________________________________ > Pspp-users mailing list > Pspp-users@... > https://lists.gnu.org/mailman/listinfo/pspp-users > > ----- End forwarded message -----
On Sun, Feb 26, 2012 at 10:07:51AM -0800, Ben Pfaff wrote: John Darrington <john@...> writes:
> I think I finally tracked down a bug in the ascii driver which has been annoying me for > years. The bug is difficult to reproduce, since it manifests itself only when output > is to the terminal and exactly if and when it occurs is likely to be dependent on the > terminal's dimensions. > > However I think the attached patches solve the problem. I'm sending them here for review > before I check them in.
These all look reasonable to
me. I didn't compile or test them. Thanks for spotting the problem. -- Ben Pfaff http://benpfaff.org
-- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://keys.gnupg.net or any PGP keyserver for public key.