xgridfit-users

[Xgridfit-users] -m and -S options

[Andrey V. P. <pa...@ca...>]

Peter,

when xgridfit is invoked simultaneously with -m and -S options, for example 
"xgridfit -m -p 25 -G no -S py/Heuristica-Regular -i Heuristica-Regular_.sfd  -o 
Heuristica-Regular.ttf Heuristica-Regular.ed.xgf" in Heuristica font project, it 
does not save separate files for glyphs. This prevents me from switching to this 
merging mode.

-- 
Andrey V. Panov
http://canopus.iacp.dvo.ru/~panov/

Re: [Xgridfit-users] -m and -S options

[Peter B. <b....@gm...>]

Andrey,

I'd like to know more about what you're trying to do. I've looked at
the Makefile from your current Google Code site, but it doesn't use
the -S option.

The reason there is no -S option availabe in merge-mode right now is
that the output Python script is differently organized in that mode.
The glyph programs are stored in a dictionary. Auto-hinting and
-instructing (when required) are done by comparing the collection of
glyphs in the existing font against this dictionary. And glyph
programs are installed by iterating through the dictionary.

By contrast, the standard Python or FF scripting language output just
inserts the code into a function call:

install_glyph_program("uni025B", "...code...")

So there it is easier to put the function calls in their separate files.

I don't mind reorganizing the Python output for merge-mode (I can
think of other arrangements that would work), but I'd like to know
more about what you're trying to do so that I make the right kinds of
revisions.

To tell the truth, I've always been a bit hazy about how you use -S.

Peter

On Wed, Apr 7, 2010 at 12:48 AM, Andrey V. Panov
<pa...@ca...> wrote:
> Peter,
>
> when xgridfit is invoked simultaneously with -m and -S options, for example
> "xgridfit -m -p 25 -G no -S py/Heuristica-Regular -i Heuristica-Regular_.sfd  -o
> Heuristica-Regular.ttf Heuristica-Regular.ed.xgf" in Heuristica font project, it
> does not save separate files for glyphs. This prevents me from switching to this
> merging mode.
>
> --
> Andrey V. Panov
> http://canopus.iacp.dvo.ru/~panov/
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Xgridfit-users mailing list
> Xgr...@li...
> https://lists.sourceforge.net/lists/listinfo/xgridfit-users
>

Re: [Xgridfit-users] -m and -S options

[Andrey V. P. <pa...@ca...>]

On 8 апреля 2010, Peter Baker wrote:
> I'd like to know more about what you're trying to do. I've looked at
> the Makefile from your current Google Code site, but it doesn't use
> the -S option.

I use it internally for instructing Istok font. It still utilizes ttx. If it is 
impossible to combine merging mode with -S option I will stay on the old ttx 
based merge.

-- 
Andrey V. Panov
panov /@/ canopus.iacp.dvo.ru

Re: [Xgridfit-users] -m and -S options

[Peter B. <b....@gm...>]

It's far from impossible; it's just a matter of figuring out how to do
it in a way that will actually be helpful. Here's one possiblity:

-S option produces files containing instructions only--that is, not
wrapped in a function call. The generated Python script builds the
dictionary it needs in either of two ways:

1. by having its own list of filenames ["instrs/Heuristica_A.txt",
"instrs/Heuristica_B.txt"] and reading the instructions from the files
into the dictionary; or

2. by getting its own list of files by doing e.g. the Python
equivalent of "ls Heuristica_*.txt" and building this dictionary from
these.

Would something like this--the raw instructions in text files--serve
your purpose?

2010/4/7 Andrey V. Panov <pa...@ca...>:

> I use it internally for instructing Istok font. It still utilizes ttx. If it is
> impossible to combine merging mode with -S option I will stay on the old ttx
> based merge.
>
xgridfit-users
>

Re: [Xgridfit-users] -m and -S options

[Peter B. <b....@gm...>]

Here's another possibility. If what you want is a series of little
Python programs that can be run individually, the -S option could also
produce these (though in merge-mode it has got to have access to the
original .sfd or .ttf file to produce them):

One for CVT, prep and fpgm;

One for each glyph program.

Is this the sort of thing you want?

On Thu, Apr 8, 2010 at 4:19 PM, Peter Baker <b....@gm...> wrote:
> It's far from impossible; it's just a matter of figuring out how to do
> it in a way that will actually be helpful. Here's one possiblity:
>

Re: [Xgridfit-users] -m and -S options

[Andrey V. P. <pa...@ca...>]

On 9 апреля 2010, Peter Baker wrote:
> Here's another possibility. If what you want is a series of little
> Python programs that can be run individually, the -S option could also
> produce these (though in merge-mode it has got to have access to the
> original .sfd or .ttf file to produce them):
> 
> One for CVT, prep and fpgm;
> 
> One for each glyph program.
> 
> Is this the sort of thing you want?

I think this variant is closer to current behavior of -S option. It allows 
further collecting instructions for all the glyphs. But feel free to choose most 
relevant way of separate compilation of instructions for different glyphs with 
possibility to combine all the compilations into one font file.

-- 
Andrey V. Panov
panov /@/ canopus.iacp.dvo.ru