Fonty Python 0.4 - Beta test help please
Donn
Apologies for the spam on this list. I don't know what to do about it.
I am aiming for a 0.4 release soon and need a spot of help. If you are in the
mood, could you take the latest trunk for a run and let me know what breaks!
Get it fresh by:
svn co svn://svn.sv.gnu.org/fontypython/trunk
Or from:
http://download.savannah.nongnu.org/releases/fontypython/
(look for version 0.4 -- which might not be there for a few hours yet.)
I need to know:
1. i18n -- still working? Many translations will be broken cos I changed stuff.
2. Functionality. I am suffering "code bleh" -- I can't tell if the app does
what it's supposed-to or not. Just too close to the trees to see the etc.
Have to check a)The command-line b)The Gui c)The help.
3. Bugs. If you use Savannah to report them, please email me a warning too.
Once I get your feedback and fix any bugs, our friendly packager will be
unleashed and FP-0.4 will hit the Universe! :D
Many thanks,
Donn.
--
home: http://otherwise.relics.co.za/
2D vector animation : https://savannah.nongnu.org/projects/things/
Font manager : https://savannah.nongnu.org/projects/fontypython/
Donn
\d
Kartik Mistry
> I have had no responses yet. Anyone reading the list?
I have sent mail to my LUG too, No reply yet. However, I tested 0.4
build on Debian - it works fine :)
--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Debian GNU/Linux Developer
Blog.en: ftbfs.wordpress.com
Blog.gu: kartikm.wordpress.com
Donn
> I have sent mail to my LUG too, No reply yet. However, I tested 0.4
> build on Debian - it works fine
I don't think we will get any other feedback in a hurry. I will make a new
'release' on the svn server called fonty0-4 and ping you when it's done. You
can package from that when you are ready.
Thanks for all your support,
\d
Kartik Mistry
> I will make a new
> 'release' on the svn server called fonty0-4 and ping you when it's done. You
> can package from that when you are ready.
Sure.
However, for packaging, it is better to have upstream tar ball..
Donn
> However, for packaging, it is better to have upstream tar ball..
trunk and making sure I didn't miss anything and then I will build and test
and get it off to you.
Pietro Battiston
> On Sunday, 05 July 2009 09:39:01 Kartik Mistry wrote:
> > I have sent mail to my LUG too, No reply yet. However, I tested 0.4
> > build on Debian - it works fine
> Thanks Kartik, you are a rock!
> I don't think we will get any other feedback in a hurry.
May I disagree?
I spent only few minutes with an Internet connection in the last days,
so I had no time to report my findings, but I did test fontypython on a
karmic and found some problems: it seems like for some reason just
giving "sudo python setup.py install" creates the "~/.fontypython"
directory. There are two problems with that:
- it is not a nice logic: the directory should just be created on the
first run, regardless of the user which performed the installation
- the directory is created owned by user root. The original user _can_
remove it (since he presumably has write rights on his home), but until
he does so he gets the following error:
No config file found, creating it with defaults.
Could not write to the config file.
CORNER CASE ERROR in logBadStrings:
(<type 'exceptions.IOError'>, IOError(13, 'Permission denied'),
<traceback object at 0xa386d74>)
Unhandled error:
Please move () away from here and report this to us.
(the startup screen shows, but then fontypython exits)
Pietro
Donn
> May I disagree?
Sure, hi Pietro :)
> I spent only few minutes with an Internet connection in the last days,
> so I had no time to report my findings, but I did test fontypython on a
> karmic and found some problems:
Thanks for doing that! It sure helps.
> it seems like for some reason just
> giving "sudo python setup.py install" creates the "~/.fontypython"
> directory.
That is just plain strange. I recall this from a few years ago, but not the
cause. The fact is there is no call to create that folder in the setup.py
It is created by fonty when you first run it.
I will have a better look at it when I wake up properly ;)
Thanks for the report.
Donn
Some feedback. You were 100% correct. I found a way around the problem and now
setup.py does not create the .fontypython folder. Mnay thanks. I have updated
the svn.
I would love to know if the latest fonty works in Italian... :)
Thanks,
Pietro Battiston
> Pietro,
> Some feedback. You were 100% correct. I found a way around the problem and now
> setup.py does not create the .fontypython folder. Mnay thanks. I have updated
> the svn.
>
> I would love to know if the latest fonty works in Italian... :)
It does, and here's the updated .po file.
However, some remarks:
1) I didn't translate
"CORNER CASE in Folder.__init__: UnicodeDecodeError under: %s"
To what extent to you think it should be translated? Probably only
"under"?
2) You usually write "Pog", but sometimes "pog". I preferred the
latter...
3) It is a bit of a pain to review very big strings, of which usually
only a small part has changed. While in general I do understand that
it's a pain for the programmer to split a string in many, in the
particular case of command line help messages, I would warmly recommend
to drop getopt for optparse. Not only it takes the burden of printing
help from better organized (and updateable) strings, hence reducing
their average size, but moreover it takes care of the typesetting of the
help, reducing the need of all the \t, \n and 80 characters limit (which
it's a mess to respect while using poedit).
4) in the README for translation, you talk about fr_all_merged.po when
you probably mean fr_all.merged.po
Anyway, here's the .po up to now.
Pietro
Donn
> > I would love to know if the latest fonty works in Italian... :)
> It does, and here's the updated .po file.
> However, some remarks:
> 1) I didn't translate
> "CORNER CASE in Folder.__init__: UnicodeDecodeError under: %s"
> To what extent to you think it should be translated? Probably only
> "under"?
Corner cases are supposed to never happen. If they do, the english error would
be more useful (to me at least). So just leave them. I will remove any _()
from them.
> 2) You usually write "Pog", but sometimes "pog". I preferred the
> latter...
I am consistent in my inconsistency :) I'll make a note and try to squash this
wherever I see it.
> 3) It is a bit of a pain to review very big strings...recommend
> to drop getopt for optparse.
It's a few years ago now, but I started with optparse and found that it had
trouble passing unicode arguments into the app. I tried everything I could and
gave up for the solution in cli.py right now. This does not mean that it can't
be done, just that I may not have the brains for it.
I will make another note (gnote FTW!) and hack it a little.
> 4) in the README for translation, you talk about fr_all_merged.po when
> you probably mean fr_all.merged.po
Right - will go look.
I go now to mo the po :)
\d
Pietro Battiston
> > 3) It is a bit of a pain to review very big strings...recommend
> > to drop getopt for optparse.
> It's a few years ago now, but I started with optparse and found that it had
> trouble passing unicode arguments into the app. I tried everything I could and
> gave up for the solution in cli.py right now.
You're absolutely right (I stumbled in the problem in another app):
http://bugs.python.org/issue2931
bye
Pietro