From: George W. <gw...@si...> - 2010-04-29 20:25:59
|
I fear I no longer have time to provide (and support) binary releases, so the current release is source (and documentation) only. |
From: Barry S. <che...@ch...> - 2010-04-30 04:10:32
|
George Williams <gw...@si...> wrote: > I fear I no longer have time to provide (and support) binary > releases, so the current release is source (and documentation) only. Just the documentation would be more than enough. |
From: Alexandre P. <ale...@gm...> - 2010-04-30 19:13:28
|
On 4/30/10, George Williams wrote: > I fear I no longer have time to provide (and support) binary releases, so > the current release is source (and documentation) only. Ouch, and I was going to send translation update... Oh well :) Nevermind :) One question: where exactly do I find splines stroking? BTW, the changelog says "arbetrary convex polygons". Should be "arbitrary"? Alexandre |
From: Alexandre P. <ale...@gm...> - 2010-04-30 20:46:29
|
On 4/30/10, Alexandre Prokoudine wrote: > One question: where exactly do I find splines stroking? Okay, found it: Expand Strokes in Element menu. But I don't understand how to make it work for the freehand drawing tool. I see that when I set some options for e.g. a polygon in a dialog that I open by double-clicking tool's icon, changes apply to the tool after I click OK in the dialog, and every new polygon I draw uses new settings. This is expected behavior. When I double-click freehand tool's icon, set settings and click OK, I still see regular paths. And when I reopen settings dialog, default settings are used again. This is all not really expected. I'm running CVS build from April 16, but building current CVS atm. Alexandre |
From: Kevin F. <ke...@sc...> - 2010-05-01 04:34:05
Attachments:
signature.asc
|
On Thu, 29 Apr 2010 13:25:51 -0700 (PDT) George Williams <gw...@si...> wrote: > I fear I no longer have time to provide (and support) binary > releases, so the current release is source (and documentation) only. I'm running into a build issue with the latest: ( cd po ; make ) make: [pos] Error 1 (ignored) make[1]: Entering directory `/builddir/build/BUILD/fontforge-20100429/po' msgfmt -o de.mo de.po msgfmt -o el.mo el.po el.po:16555: duplicate message definition... el.po:6706: ...this is the location of the first definition msgfmt: found 1 fatal error make[1]: Leaving directory `/builddir/build/BUILD/fontforge-20100429/po' make[1]: *** [el.mo] Error 1 make: *** [pos] Error 2 Any ideas? kevin |
From: Khaled H. <kha...@eg...> - 2010-05-01 06:05:27
|
On Fri, Apr 30, 2010 at 10:15:08PM -0600, Kevin Fenzi wrote: > On Thu, 29 Apr 2010 13:25:51 -0700 (PDT) > George Williams <gw...@si...> wrote: > > > I fear I no longer have time to provide (and support) binary > > releases, so the current release is source (and documentation) only. > > I'm running into a build issue with the latest: > > ( cd po ; make ) > make: [pos] Error 1 (ignored) > make[1]: Entering directory `/builddir/build/BUILD/fontforge-20100429/po' > msgfmt -o de.mo de.po > msgfmt -o el.mo el.po > el.po:16555: duplicate message definition... > el.po:6706: ...this is the location of the first definition > msgfmt: found 1 fatal error > make[1]: Leaving directory `/builddir/build/BUILD/fontforge-20100429/po' > make[1]: *** [el.mo] Error 1 > make: *** [pos] Error 2 > > Any ideas? Me too, seems some PO files are broken. Gettext doesn't allow duplicated entries, they should either be merged together or, if necessary, differentiated by msgctx. Looks like PO files need to be updated using gettext tools, usually by generating a POT file then using msgmerge to merge old translations. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer |
From: Michal N. <mi...@li...> - 2010-05-01 08:50:28
|
Khaled Hosny pisze: > Looks like PO files need to be updated using gettext tools, usually by > generating a POT file then using msgmerge to merge old translations. Fixed, but I guess translators still have to review their files - automata don't care for orthography. Regards, Michał Nowakowski |
From: Paulo S. <nit...@gm...> - 2010-04-29 20:47:42
|
yes, just let this task for the GNU/Linux distribution packagers - Debian/Ubuntu binary packages of FontForge are just awesome! :) - anyway George, thank you so much for the huge initiative and contribution in a so brilliant project FontForge is! :) On 4/29/10, George Williams <gw...@si...> wrote: > I fear I no longer have time to provide (and support) binary releases, so > the current release is source (and documentation) only. > > ------------------------------------------------------------------------------ > _______________________________________________ > Fontforge-users mailing list > Fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-users > -- Don't give Microsoft the remote control. Don't use Windows 7. <http://windows7sins.org> |
From: Michal N. <mi...@li...> - 2010-06-04 08:19:03
|
W dniu 30.04.2010 22:45, Alexandre Prokoudine pisze: > When I double-click freehand tool's icon, set settings and click OK, I > still see regular paths. And when I reopen settings dialog, default > settings are used again. This is all not really expected. I can confirm this, for docked pallettes. For undocked pallettes, I'm getting a segfault at cvpallettes.c:818, because of corruption of charviev->b1_tool & company, somewhere between clicking 'OK' and re-drawing tool icon for first mouse button in the pallettes. And, George, I was unable to fix it. It looks to me, as if memory regions for pallettes image and for charview metadata overlap a bit, so that drawing the tiny icons below tool selection buttons reads their indices from b1_tool from charview, that just got corrupted by drawing tool buttons. I could't isolate, where the overlap happens. Regards, Michał Nowakowski |
From: Khaled H. <kha...@eg...> - 2010-06-04 09:12:08
|
On Fri, Jun 04, 2010 at 10:18:42AM +0200, Michal Nowakowski wrote: > W dniu 30.04.2010 22:45, Alexandre Prokoudine pisze: > > > When I double-click freehand tool's icon, set settings and click OK, I > > still see regular paths. And when I reopen settings dialog, default > > settings are used again. This is all not really expected. > > I can confirm this, for docked pallettes. > > For undocked pallettes, I'm getting a segfault at cvpallettes.c:818, > because of corruption of charviev->b1_tool & company, somewhere between > clicking 'OK' and re-drawing tool icon for first mouse button in the > pallettes. And, George, I was unable to fix it. > > It looks to me, as if memory regions for pallettes image and for > charview metadata overlap a bit, so that drawing the tiny icons below > tool selection buttons reads their indices from b1_tool from charview, > that just got corrupted by drawing tool buttons. I could't isolate, > where the overlap happens. I'm experiencing many strange memory issues for a while now, and more frequent crashes than it used to be, it seems to be a more general issue. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer |
From: Michal N. <mi...@li...> - 2010-12-23 20:38:38
|
W dniu 04.06.2010 11:11, Khaled Hosny pisze: > On Fri, Jun 04, 2010 at 10:18:42AM +0200, Michal Nowakowski wrote: >> W dniu 30.04.2010 22:45, Alexandre Prokoudine pisze: >> >>> When I double-click freehand tool's icon, set settings and click OK, I >>> still see regular paths. And when I reopen settings dialog, default >>> settings are used again. This is all not really expected. >> >> I can confirm this, for docked pallettes. >> >> For undocked pallettes, I'm getting a segfault at cvpallettes.c:818, >> because of corruption of charviev->b1_tool& company, somewhere between >> clicking 'OK' and re-drawing tool icon for first mouse button in the >> pallettes. And, George, I was unable to fix it. >> >> It looks to me, as if memory regions for pallettes image and for >> charview metadata overlap a bit, so that drawing the tiny icons below >> tool selection buttons reads their indices from b1_tool from charview, >> that just got corrupted by drawing tool buttons. I could't isolate, >> where the overlap happens. > > I'm experiencing many strange memory issues for a while now, and more > frequent crashes than it used to be, it seems to be a more general > issue. I managed to suppress the segfault for undocked pallettes. It was because refreshing pallettes was taking data from charview inside freehand dialog, that got inactivated previously. The fix may hide the pallettes - just click a charview to get them back. However, it still doesn't stroke the freehand path. Regards, Michał Nowakowski |