[fontforge-devel] Pending Pull Requests, Pressing Issues?

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[fontforge-devel] Pending Pull Requests, Pressing Issues?

Frank Trampe
Hi, all.

I'm hoping to cut a FontForge release by the end of the month. Let me know of any changesets that you want to make the cut and of any critical bugs that we need to fix.


------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Dave Crossland
I am very keen to see the new menu layout in the next release :) 

On 5 September 2016 at 19:21, Frank Trampe <[hidden email]> wrote:
Hi, all.

I'm hoping to cut a FontForge release by the end of the month. Let me know of any changesets that you want to make the cut and of any critical bugs that we need to fix.


------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html




--
Cheers
Dave

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Frank Trampe
That seems unlikely at this point. The pull request isn't finished, and I think Pathum told me that the developer working on it is no longer available.

There are also issues that we need to sort out regarding the actual changes, some of which this FontForge user finds puzzling/irritating. Even if we leave the old menu system as an option for those who want it (which we will almost certainly do since I want it), I think we need to get a bit more community feedback before pushing such a visible change on people.


On Tue, Sep 6, 2016 at 3:04 AM, Dave Crossland <[hidden email]> wrote:
I am very keen to see the new menu layout in the next release :) 

On 5 September 2016 at 19:21, Frank Trampe <[hidden email]> wrote:
Hi, all.

I'm hoping to cut a FontForge release by the end of the month. Let me know of any changesets that you want to make the cut and of any critical bugs that we need to fix.


------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html




--
Cheers
Dave

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html



------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Dave Crossland

On 6 September 2016 at 14:53, Frank Trampe <[hidden email]> wrote:
That seems unlikely at this point. The pull request isn't finished, and I think Pathum told me that the developer working on it is no longer available.

I can raise funds to enable Ben Martin to complete it, if it needs more work. But it isn't clear to me what additional work needs to be done. 

However, I am really feeling frustrated that reordering menu items could be very complex :( 
 
There are also issues that we need to sort out regarding the actual changes, some of which this FontForge user finds puzzling/irritating. Even if we leave the old menu system as an option for those who want it (which we will almost certainly do since I want it), I think we need to get a bit more community feedback before pushing such a visible change on people.

I'd be happy to see FF releases with 2 versions, a 'stable' version with the classic menus and a 'testing' or 'unstable' version with the new menus, for say 12 months.

However, for me this reveals a more serious problem, which is that we don't have reliable automatic installer package creation for Windows and Mac OS X. jtanx has just posted that he has a windows installer going with AppVeyor, so I think for me the #1 changeset would be to the travis file, to get travis building Mac binaries for each PR. 

I can raise funds for that to happen, if needed.

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Frank Trampe


On Tue, Sep 6, 2016 at 11:42 AM, Dave Crossland <[hidden email]> wrote:

On 6 September 2016 at 14:53, Frank Trampe <[hidden email]> wrote:
That seems unlikely at this point. The pull request isn't finished, and I think Pathum told me that the developer working on it is no longer available.

I can raise funds to enable Ben Martin to complete it, if it needs more work. But it isn't clear to me what additional work needs to be done. 

I'm not sure either. My information is second-hand, and the pull request is very large, so it is difficult for me to ascertain by skimming it. The one thing that I notice is that a large chunk of the documentation has been deleted, which is bad.
 
However, I am really feeling frustrated that reordering menu items could be very complex :( 
 
I think that it would be nice to have a dynamically configured menu system. Perhaps with an xml file with labels, shortcuts, icon image names, and base menu item names. But there are a lot of other more pressing issues.
 
There are also issues that we need to sort out regarding the actual changes, some of which this FontForge user finds puzzling/irritating. Even if we leave the old menu system as an option for those who want it (which we will almost certainly do since I want it), I think we need to get a bit more community feedback before pushing such a visible change on people.

I'd be happy to see FF releases with 2 versions, a 'stable' version with the classic menus and a 'testing' or 'unstable' version with the new menus, for say 12 months.

I'm not proposing a fork. I'm proposing having two sets of menu structures in the codebase and allowing for switching between them via a flag in the preference file. The important thing to me is that those of us who do not wish to switch can continue using the menu system with which we are happy and familiar.

Last time I looked, the new menus did a lot of things that broke the usual rules of menu structure (like moving the revert/reload entry out of the file menu), which I dislike. And anything different (whether better or worse for new users) creates a hassle for those who know how things work. I would strongly prefer to use the old menu system, and I imagine that others would like to do so also.

However, for me this reveals a more serious problem, which is that we don't have reliable automatic installer package creation for Windows and Mac OS X. jtanx has just posted that he has a windows installer going with AppVeyor, so I think for me the #1 changeset would be to the travis file, to get travis building Mac binaries for each PR. 

I can raise funds for that to happen, if needed.

This would seem to be a useful thing.

I'm travelling for the next week. Could I look at this late next week?
 
------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html



------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Dave Crossland

On 6 September 2016 at 17:58, Frank Trampe <[hidden email]> wrote:
I think that it would be nice to have a dynamically configured menu system. Perhaps with an xml file with labels, shortcuts, icon image names, and base menu item names. But there are a lot of other more pressing issues.

I agree. Is the new menu system a 'hard coded' one, just like the old one?

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Frank Trampe

On Tue, Sep 6, 2016 at 12:54 PM, Dave Crossland <[hidden email]> wrote:

On 6 September 2016 at 17:58, Frank Trampe <[hidden email]> wrote:
I think that it would be nice to have a dynamically configured menu system. Perhaps with an xml file with labels, shortcuts, icon image names, and base menu item names. But there are a lot of other more pressing issues.

I agree. Is the new menu system a 'hard coded' one, just like the old one?

Completely. It just rearranges the arrays of things.
 
------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html



------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Dave Crossland

On 6 September 2016 at 19:04, Frank Trampe <[hidden email]> wrote:
Completely. It just rearranges the arrays of things.

How long would it take to develop a configurable system?

XML seems like overkill, I think CSV would be fine :) 

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Frank Trampe
I'll take a closer look today.


On Tue, Sep 6, 2016 at 1:15 PM, Dave Crossland <[hidden email]> wrote:

On 6 September 2016 at 19:04, Frank Trampe <[hidden email]> wrote:
Completely. It just rearranges the arrays of things.

How long would it take to develop a configurable system?

XML seems like overkill, I think CSV would be fine :) 

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html



------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Frank Trampe
We would aim to add configurable menus to the font view, the character view, and the metrics view.

I think that a successful design would look like this.
  • The theme default file can specify file names for menu overlay files for each of the three big views.
  • We would make all routines called from menus accessible via the FontForge scripting interface.
  • The menu overlay files contain an XML representation of the nested GMenuItem2 and GTextInfo data, including image file names and fixed function names. (CSV can't do nesting.)
  • At start, FontForge parses the XML into native GTextInfo and GMenuItem2 data, with pointers to native scripting functions and overlaid translations.
  • This would (initially) be disabled by default, to be enabled via the preference file. In the absence of a preference file, FontForge parses the menu system for the selected theme, and, if valid, enables dynamic menus in the preference file and loads the parsed menu system. Otherwise, it uses the existing static data.


On Tue, Sep 6, 2016 at 1:20 PM, Frank Trampe <[hidden email]> wrote:
I'll take a closer look today.


On Tue, Sep 6, 2016 at 1:15 PM, Dave Crossland <[hidden email]> wrote:

On 6 September 2016 at 19:04, Frank Trampe <[hidden email]> wrote:
Completely. It just rearranges the arrays of things.

How long would it take to develop a configurable system?

XML seems like overkill, I think CSV would be fine :) 

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html




------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Dave Crossland

On 7 September 2016 at 00:15, Frank Trampe <[hidden email]> wrote:
(CSV can't do nesting.)

Some Menu,1,2,3,4
Some Menu/Child 1,5,6,7,8
Some Menu/Child 2,a,b,c,d



------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Philippe Cochy
Le mercredi 07 septembre 2016 à 00:52 +0100, Dave Crossland a écrit :
> On 7 September 2016 at 00:15, Frank Trampe <[hidden email]>
> wrote:
>         (CSV can't do nesting.)
>
> Some Menu,1,2,3,4
> Some Menu/Child 1,5,6,7,8
> Some Menu/Child 2,a,b,c,d

If it is not polluted with unnecessary namespaces, the XML allows
recursion, i.e. building a tree very efficiently.



------------------------------------------------------------------------------
_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
T J
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

T J
In reply to this post by Frank Trampe

I don't mind looking into the automated builds. Although there's a few things in there I'm unsure of - like what's bigv? As far as I can see, it tries to upload some files to there at the end of the builds, but this hasn't happened/worked in a long time.


If I were to do this, I'd probably set it to deploy to bintray, which I already use for hosting the mingw precompiled libraries.

The other thing is that the scripts to make the OS X package are... what I would call unmaintainable. It's a miracle to me that the OS X packages can even be made at all in its current state.

Jeremy

From: Frank Trampe <[hidden email]>
Sent: Wednesday, 7 September 2016 12:58 AM
To: FontForge developers' discussions
Subject: Re: [fontforge-devel] Pending Pull Requests, Pressing Issues?
 


On Tue, Sep 6, 2016 at 11:42 AM, Dave Crossland <[hidden email]> wrote:

On 6 September 2016 at 14:53, Frank Trampe <[hidden email]> wrote:
That seems unlikely at this point. The pull request isn't finished, and I think Pathum told me that the developer working on it is no longer available.

I can raise funds to enable Ben Martin to complete it, if it needs more work. But it isn't clear to me what additional work needs to be done. 

I'm not sure either. My information is second-hand, and the pull request is very large, so it is difficult for me to ascertain by skimming it. The one thing that I notice is that a large chunk of the documentation has been deleted, which is bad.
 
However, I am really feeling frustrated that reordering menu items could be very complex :( 
 
I think that it would be nice to have a dynamically configured menu system. Perhaps with an xml file with labels, shortcuts, icon image names, and base menu item names. But there are a lot of other more pressing issues.
 
There are also issues that we need to sort out regarding the actual changes, some of which this FontForge user finds puzzling/irritating. Even if we leave the old menu system as an option for those who want it (which we will almost certainly do since I want it), I think we need to get a bit more community feedback before pushing such a visible change on people.

I'd be happy to see FF releases with 2 versions, a 'stable' version with the classic menus and a 'testing' or 'unstable' version with the new menus, for say 12 months.

I'm not proposing a fork. I'm proposing having two sets of menu structures in the codebase and allowing for switching between them via a flag in the preference file. The important thing to me is that those of us who do not wish to switch can continue using the menu system with which we are happy and familiar.

Last time I looked, the new menus did a lot of things that broke the usual rules of menu structure (like moving the revert/reload entry out of the file menu), which I dislike. And anything different (whether better or worse for new users) creates a hassle for those who know how things work. I would strongly prefer to use the old menu system, and I imagine that others would like to do so also.

However, for me this reveals a more serious problem, which is that we don't have reliable automatic installer package creation for Windows and Mac OS X. jtanx has just posted that he has a windows installer going with AppVeyor, so I think for me the #1 changeset would be to the travis file, to get travis building Mac binaries for each PR. 

I can raise funds for that to happen, if needed.

This would seem to be a useful thing.

I'm travelling for the next week. Could I look at this late next week?
 
------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html



------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Frank Trampe
On Sep 7, 2016 5:31 AM, "T J" <[hidden email]> wrote:

I don't mind looking into the automated builds. Although there's a few things in there I'm unsure of - like what's bigv? As far as I can see, it tries to upload some files to there at the end of the builds, but this hasn't happened/worked in a long time.


If I were to do this, I'd probably set it to deploy to bintray, which I already use for hosting the mingw precompiled libraries.

The other thing is that the scripts to make the OS X package are... what I would call unmaintainable. It's a miracle to me that the OS X packages can even be made at all in its current state.

The scripts don't actually work. There is a lot of manual work, with work-arounds for the deficiencies in the scripts. I have notes somewhere, and I plan to convert those into new scripts at some point.
 
Jeremy

From: Frank Trampe <[hidden email]>
Sent: Wednesday, 7 September 2016 12:58 AM
To: FontForge developers' discussions
Subject: Re: [fontforge-devel] Pending Pull Requests, Pressing Issues?
 


On Tue, Sep 6, 2016 at 11:42 AM, Dave Crossland <[hidden email]> wrote:

On 6 September 2016 at 14:53, Frank Trampe <[hidden email]> wrote:
That seems unlikely at this point. The pull request isn't finished, and I think Pathum told me that the developer working on it is no longer available.

I can raise funds to enable Ben Martin to complete it, if it needs more work. But it isn't clear to me what additional work needs to be done. 

I'm not sure either. My information is second-hand, and the pull request is very large, so it is difficult for me to ascertain by skimming it. The one thing that I notice is that a large chunk of the documentation has been deleted, which is bad.
 
However, I am really feeling frustrated that reordering menu items could be very complex :( 
 
I think that it would be nice to have a dynamically configured menu system. Perhaps with an xml file with labels, shortcuts, icon image names, and base menu item names. But there are a lot of other more pressing issues.
 
There are also issues that we need to sort out regarding the actual changes, some of which this FontForge user finds puzzling/irritating. Even if we leave the old menu system as an option for those who want it (which we will almost certainly do since I want it), I think we need to get a bit more community feedback before pushing such a visible change on people.

I'd be happy to see FF releases with 2 versions, a 'stable' version with the classic menus and a 'testing' or 'unstable' version with the new menus, for say 12 months.

I'm not proposing a fork. I'm proposing having two sets of menu structures in the codebase and allowing for switching between them via a flag in the preference file. The important thing to me is that those of us who do not wish to switch can continue using the menu system with which we are happy and familiar.

Last time I looked, the new menus did a lot of things that broke the usual rules of menu structure (like moving the revert/reload entry out of the file menu), which I dislike. And anything different (whether better or worse for new users) creates a hassle for those who know how things work. I would strongly prefer to use the old menu system, and I imagine that others would like to do so also.

However, for me this reveals a more serious problem, which is that we don't have reliable automatic installer package creation for Windows and Mac OS X. jtanx has just posted that he has a windows installer going with AppVeyor, so I think for me the #1 changeset would be to the travis file, to get travis building Mac binaries for each PR. 

I can raise funds for that to happen, if needed.

This would seem to be a useful thing.

I'm travelling for the next week. Could I look at this late next week?
 
------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html



------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html


------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pending Pull Requests, Pressing Issues?

Apostolos Syropoulos
In reply to this post by Frank Trampe
2016-09-05 21:21 GMT+03:00 Frank Trampe <[hidden email]>:
> Hi, all.
>
> I'm hoping to cut a FontForge release by the end of the month. Let me know
> of any changesets that you want to make the cut and of any critical bugs
> that we need to fix.
>
>

Hello,

I have noticed that when I try to print a full page glyph to a PDF file or a
to a file (it genereates) a PostScript file, the resulting file is not correct.

Here is what GhostScript reports:

$ gs pr-Frederika2016.ps
GPL Ghostscript 9.19 (2016-03-23)
Copyright (C) 2016 Artifex Software, Inc.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Loading NimbusRomNo9L-Med font from
%rom%Resource/Font/NimbusRomNo9L-Med... 4148548 2794462 6270568
4972733 1 done.
Error: /undefined in 178,723
Operand stack:
   --dict:16/16(ro)(L)--   --nostringval--   --nostringval--   40
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--
--nostringval--   --nostringval--   false   1   %stopped_push   1967
1   3   %oparray_pop   1966   1   3   %oparray_pop   1950   1   3
%oparray_pop   1836   1   3   %oparray_pop   --nostringval--
%errorexec_pop   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:1193/1684(ro)(G)--   --dict:0/20(G)--   --dict:82/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
Current file position is 1265
GPL Ghostscript 9.19: Unrecoverable error, exit code 1


$ gs pr-Frederika2016.pdf
GPL Ghostscript 9.19 (2016-03-23)
Copyright (C) 2016 Artifex Software, Inc.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Processing pages 1 through 1.
Page 1
Loading NimbusRomNo9L-Med font from
%rom%Resource/Font/NimbusRomNo9L-Med... 4148548 2735587 6452296
5103038 3 done.
   **** Error: Unknown operator: '134,435'
   **** Error: Unknown operator: '134,435'
   **** Error: Unknown operator: '42,7911'
   **** Error: Unknown operator: '42,7911'
   **** Error reading a content stream. The page may be incomplete.
               Output may be incorrect.
Error: /typecheck in --run--
Operand stack:
   2   Annots
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--
--nostringval--   2   %stopped_push   --nostringval--
--nostringval--   --nostringval--   false   1   %stopped_push   1967
1   3   %oparray_pop   1966   1   3   %oparray_pop   1950   1   3
%oparray_pop   --nostringval--   --nostringval--   2   1   1
--nostringval--   %for_pos_int_continue   --nostringval--
--nostringval--   --nostringval--   --nostringval--
Dictionary stack:
   --dict:1193/1684(ro)(G)--   --dict:1/20(G)--   --dict:83/200(L)--
--dict:83/200(L)--   --dict:132/256(ro)(G)--   --dict:287/300(ro)(G)--
  --dict:31/32(L)--   --dict:6/8(L)--   --dict:25/40(L)--
--dict:1/1(ro)(G)--
Current allocation mode is local
Last OS error: No such file or directory
GPL Ghostscript 9.19: Unrecoverable error, exit code 1

A.S.

--
Apostolos Syropoulos
Xanthi, GREECE

------------------------------------------------------------------------------
_______________________________________________
fontforge-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html
Loading...