Fonty 0.4.3
2 views
Skip to first unread message
Michael Hoeft
Nov 15, 2009, 1:01:51 PM11/15/09
to fonty...@googlegroups.com
Hello Donn and the rest of the world,
it seems fonty's development sleeps for a while, so I will take the
chance to step out of the scenery, wherefrom I watched the spectacle.
Would it be worthwhile to start the translation or do you plan more
changes? Changes in the GUI are not grave, especially I mean the help
and man pages.
I tested the last revision in /trunk (161) and I noticed a few little
things. For "Quick Search" (bold-, italic-, regular-buttons) are now
used standard-togglebuttons, in an older revision (155) bitmap-buttons
are used. Even if they are causes many problems, imho they looks much
nicer. Perhaps you reflect on this sometime later, Donn. Furthermore
the buttons "bold" and "italic" toggles, that means deactivating the
button clears the filter. But the "regular" button doesn't toggle, is
it on purpose?
Some words about my work (or not-work). I tried to enhance the filter,
but I feel I miss knowlegde and time to get something usefull working.
And I asked me, if this functionality is desirable. It may disagree to
fontypythons concept (be simple and fast) to include things like PANOSE
or font comparsion.
So long
Michael
it seems fonty's development sleeps for a while, so I will take the
chance to step out of the scenery, wherefrom I watched the spectacle.
Would it be worthwhile to start the translation or do you plan more
changes? Changes in the GUI are not grave, especially I mean the help
and man pages.
I tested the last revision in /trunk (161) and I noticed a few little
things. For "Quick Search" (bold-, italic-, regular-buttons) are now
used standard-togglebuttons, in an older revision (155) bitmap-buttons
are used. Even if they are causes many problems, imho they looks much
nicer. Perhaps you reflect on this sometime later, Donn. Furthermore
the buttons "bold" and "italic" toggles, that means deactivating the
button clears the filter. But the "regular" button doesn't toggle, is
it on purpose?
Some words about my work (or not-work). I tried to enhance the filter,
but I feel I miss knowlegde and time to get something usefull working.
And I asked me, if this functionality is desirable. It may disagree to
fontypythons concept (be simple and fast) to include things like PANOSE
or font comparsion.
So long
Michael
Donn
Nov 15, 2009, 9:16:52 PM11/15/09
to fonty...@googlegroups.com
Greetings Michael!
> Would it be worthwhile to start the translation or do you plan more
> changes? Changes in the GUI are not grave, especially I mean the help
> and man pages.
No, please go ahead with any translations you fancy. Have a look at the
Makefile and the fontypythonmodules/pofiles/README file too.
The fontypython.1 file is the raw source for the manpage. I am not sure how to
make multiple translations of this... Please contact Kartik (he is part of the
group in Savannah and on this list) for further advice.
The help file should be fairly easy to do.... I hope. I have put all the raw
design files (svg, fonts I used, etc.) into design/ under trunk. It's a matter
of translating the html file and perhaps a few images (png files from the svg
source -- use Inkscape) to match that. Just ask me if you need any help!
(All to be found in the svn trunk -- but don't change *anything there. Make a
branch please!)
* The only stuff you can put into trunk would be the fontypythonmodules/pofiles
and the mo files into locale, for any new translations of the actual program.
That would be fine.
> For "Quick Search" (bold-, italic-, regular-buttons) are now
> used standard-togglebuttons, in an older revision (155) bitmap-buttons
> are used. Even if they are causes many problems, imho they looks much
> nicer.
I agree they looked nice, but on my GTK theme they had this horrible white
backdrop and did not match the other buttons. I asked on the wxPython list and
they say that only in the next version of wxPython will this have a small
chance of changing, so I just went back to normal buttons. You can't even
change the *font* of a button!
> Furthermore the buttons "bold" and "italic" toggles, that means
> deactivating the button clears the filter.
> But the "regular" button doesn't toggle, is it on purpose?
Yes. Bold and Italic can mix (Bold-Italic) but Regular is exclusive (there is
no Regular-Bold etc.). So pressing 'r' gives 'regular|normal' in the filter.
Does this make sense? If I missed something just shout! Or hack the code ;)
I always wonder about these English words 'regular', 'bold', etc. Do some
fonts use German or Japanese words for these things? If so, then the bir
buttons would need some more thought...
> Some words about my work (or not-work). I tried to enhance the filter,
> but I feel I miss knowlegde and time to get something usefull working.
> And I asked me, if this functionality is desirable. It may disagree to
> fontypythons concept (be simple and fast) to include things like PANOSE
> or font comparsion.
As you know, I think this would be a great thing for fonty to have and I also
have no idea how to do it :) I was hoping you would have a breakthrough of
some kind.
My talk in the past of a "google" type search was all about the simplicity of
the *interface* (for the user) into the very complex *background* system of
finding fonts by PANOSE and/or comparison.
(I suggested pyparsing only because I have used it in the past, but I am not
married to that toolkit -- there are others and other ways to handle it.)
My only concern is with the *simplicity* for the user, not that Fonty should
not be able to do complex things -- but that those complex things be really
easy for a user and require no special knowledge or insight. Does that make
sense?
If you are in the mood to hack then please give it a go. Just make a branch
for your experiments because trunk is going to be the next version very soon.
Some notes I made about branching:
To make a copy of trunk to XX, at my command-line I did:
trunk:$ URL=svn+ssh://YOUR...@svn.savannah.nongnu.org/fontypython
trunk:$ svn copy $URL/trunk $URL/branches/XX/
Then you would Check-Out branches/XX to your local machine and hack there,
doing svn commit every now and then.
(Please check the svn manual again, I confess that I still don't have a good
grasp on svn :) I am not the brightest crayon in the box :D )
*Oh* another thing that needs doing, if you are in the mood: Someone asked
about Right-to-left languages and how they could be displayed properly in Font
Items. This should not be impossible, but tricky... ;)
Have fun with Fonty, keep us posted!
All the best,
Donn.
On Sunday 15 November 2009 20:01:51 Michael Hoeft wrote:
> it seems fonty's development sleeps for a while, so I will take the
> chance to step out of the scenery, wherefrom I watched the spectacle.
Welcome back!
> it seems fonty's development sleeps for a while, so I will take the
> chance to step out of the scenery, wherefrom I watched the spectacle.
> Would it be worthwhile to start the translation or do you plan more
> changes? Changes in the GUI are not grave, especially I mean the help
> and man pages.
Makefile and the fontypythonmodules/pofiles/README file too.
The fontypython.1 file is the raw source for the manpage. I am not sure how to
make multiple translations of this... Please contact Kartik (he is part of the
group in Savannah and on this list) for further advice.
The help file should be fairly easy to do.... I hope. I have put all the raw
design files (svg, fonts I used, etc.) into design/ under trunk. It's a matter
of translating the html file and perhaps a few images (png files from the svg
source -- use Inkscape) to match that. Just ask me if you need any help!
(All to be found in the svn trunk -- but don't change *anything there. Make a
branch please!)
* The only stuff you can put into trunk would be the fontypythonmodules/pofiles
and the mo files into locale, for any new translations of the actual program.
That would be fine.
> For "Quick Search" (bold-, italic-, regular-buttons) are now
> used standard-togglebuttons, in an older revision (155) bitmap-buttons
> are used. Even if they are causes many problems, imho they looks much
> nicer.
backdrop and did not match the other buttons. I asked on the wxPython list and
they say that only in the next version of wxPython will this have a small
chance of changing, so I just went back to normal buttons. You can't even
change the *font* of a button!
> Furthermore the buttons "bold" and "italic" toggles, that means
> deactivating the button clears the filter.
> But the "regular" button doesn't toggle, is it on purpose?
no Regular-Bold etc.). So pressing 'r' gives 'regular|normal' in the filter.
Does this make sense? If I missed something just shout! Or hack the code ;)
I always wonder about these English words 'regular', 'bold', etc. Do some
fonts use German or Japanese words for these things? If so, then the bir
buttons would need some more thought...
> Some words about my work (or not-work). I tried to enhance the filter,
> but I feel I miss knowlegde and time to get something usefull working.
> And I asked me, if this functionality is desirable. It may disagree to
> fontypythons concept (be simple and fast) to include things like PANOSE
> or font comparsion.
have no idea how to do it :) I was hoping you would have a breakthrough of
some kind.
My talk in the past of a "google" type search was all about the simplicity of
the *interface* (for the user) into the very complex *background* system of
finding fonts by PANOSE and/or comparison.
(I suggested pyparsing only because I have used it in the past, but I am not
married to that toolkit -- there are others and other ways to handle it.)
My only concern is with the *simplicity* for the user, not that Fonty should
not be able to do complex things -- but that those complex things be really
easy for a user and require no special knowledge or insight. Does that make
sense?
If you are in the mood to hack then please give it a go. Just make a branch
for your experiments because trunk is going to be the next version very soon.
Some notes I made about branching:
To make a copy of trunk to XX, at my command-line I did:
trunk:$ URL=svn+ssh://YOUR...@svn.savannah.nongnu.org/fontypython
trunk:$ svn copy $URL/trunk $URL/branches/XX/
Then you would Check-Out branches/XX to your local machine and hack there,
doing svn commit every now and then.
(Please check the svn manual again, I confess that I still don't have a good
grasp on svn :) I am not the brightest crayon in the box :D )
*Oh* another thing that needs doing, if you are in the mood: Someone asked
about Right-to-left languages and how they could be displayed properly in Font
Items. This should not be impossible, but tricky... ;)
Have fun with Fonty, keep us posted!
All the best,
Donn.
Michael Hoeft
Nov 29, 2009, 8:45:30 AM11/29/09
to fonty...@googlegroups.com
Greetings back Donn!
I would send a long message, because I commit a new branch (see
branches). But for this time you only get a few words to know something
goes on.
The new branch has a full german translation for GUI. Could I leave it
up to you, to include the po-, mo-files in the release? The help is
under construction.
In this branch I also made some hacks with the BIR-buttons. Look for
comments (## Michael:....) and the log message. Try it and give me your
mind!
Have a good time!!
Michael
I would send a long message, because I commit a new branch (see
branches). But for this time you only get a few words to know something
goes on.
The new branch has a full german translation for GUI. Could I leave it
up to you, to include the po-, mo-files in the release? The help is
under construction.
In this branch I also made some hacks with the BIR-buttons. Look for
comments (## Michael:....) and the log message. Try it and give me your
mind!
Have a good time!!
Michael
Donn
Nov 29, 2009, 11:04:41 AM11/29/09
to fonty...@googlegroups.com
Hello Michael.
Krautfont :D I had a good laugh. Thanks for the work. I promise I will give it
my attention, but I can't say how soon that will be. During the next week I
should think. I will get back to you about everything and the BIR buttons.
BTW - I have a Google Wave account -- would you like an invitation?
Best,
\d
--
\/\/ave: donn....@googlewave.com
home: http://otherwise.relics.co.za/
2D vector animation : https://savannah.nongnu.org/projects/things/
Font manager : https://savannah.nongnu.org/projects/fontypython/
Krautfont :D I had a good laugh. Thanks for the work. I promise I will give it
my attention, but I can't say how soon that will be. During the next week I
should think. I will get back to you about everything and the BIR buttons.
BTW - I have a Google Wave account -- would you like an invitation?
Best,
\d
--
\/\/ave: donn....@googlewave.com
home: http://otherwise.relics.co.za/
2D vector animation : https://savannah.nongnu.org/projects/things/
Font manager : https://savannah.nongnu.org/projects/fontypython/
Donn
Dec 2, 2009, 2:46:33 PM12/2/09
to fonty...@googlegroups.com
On Sunday 29 November 2009 15:45:30 Michael Hoeft wrote:
> In this branch I also made some hacks with the BIR-buttons. Look for
> comments (## Michael:....) and the log message. Try it and give me your
> mind!
Michael -- very clever code in there. I loved the line:
> In this branch I also made some hacks with the BIR-buttons. Look for
> comments (## Michael:....) and the log message. Try it and give me your
> mind!
ss = ("", "regular|normal")[state]
Was that yours? Still it's nice. I think you have improved the BIR buttons and
I like the way they toggle now.
I will do a diff against trunk and then see if I can merge your branch into it.
Are you going to be doing any more work? I see its at rev 163 right now.
Best,
\d
Michael Hoeft
Dec 2, 2009, 3:44:44 PM12/2/09
to fonty...@googlegroups.com
On Wed, 2 Dec 2009 21:46:33 +0200
Donn <donn....@gmail.com> wrote:
Hello Donn,
> Are you going to be doing any more work? I see its at rev 163 right now.
Yes, mainly in translation. I made few changes in po-file and the help is not
finished yet. I will try to include the images/screenshot in german, too. Therefore
some changes in the html-source are needed and graphical work.
I not be up to hack the python code. My next commit comes not before next week,
probably later. I hope it is not to late for the next release.
Bye
\m
Donn <donn....@gmail.com> wrote:
Hello Donn,
> Michael -- very clever code in there. I loved the line:
> ss = ("", "regular|normal")[state]
> Was that yours? Still it's nice. I think you have improved the BIR buttons and
> I like the way they toggle now.
Thanks!!
> ss = ("", "regular|normal")[state]
> Was that yours? Still it's nice. I think you have improved the BIR buttons and
> I like the way they toggle now.
> Are you going to be doing any more work? I see its at rev 163 right now.
finished yet. I will try to include the images/screenshot in german, too. Therefore
some changes in the html-source are needed and graphical work.
I not be up to hack the python code. My next commit comes not before next week,
probably later. I hope it is not to late for the next release.
Bye
\m
Donn
Dec 3, 2009, 12:36:20 AM12/3/09
to fonty...@googlegroups.com
On Wednesday 02 December 2009 22:44:44 Michael Hoeft wrote:
> My next commit comes not before next
> week, probably later. I hope it is not to late for the next release.
No, that's fine. There are no plans. I will move after you are all done. Take
> My next commit comes not before next
> week, probably later. I hope it is not to late for the next release.
your time.
Best,
\d
Reply all
Reply to author
Forward
0 new messages