[CLOSED] Exception in Glyph Transformer with '.' rather than ','

FontCreator - Font Editor FontCreator - Bug Reports
1

I mistakenly used a “.” (full stop aka period) instead of a “,” (comma) to separate code points in the Override Range by Code Point(s) Glyph Transformation, and got an exception (and no clue as to the cause). Don’t know if it affects other list-oriented Glyph Transforms.

I did try the checkbox and it was silent …

2

You need to buy and install the Show Error extension.

3

… or I should get better glasses …

4

I think Erwin is teasing us. :laughing:

Here are some new glasses for you. :beer_mug::beer_mug:

If I am editing long Glyph Transform scripts, I often copy them to Notepad, where I can set the font size. However, in the OT Designer you can choose the font.
OpenType Designer Settings.png

5

Same here :sunglasses:

Anyway, we switched from one exception handler to another a couple of months ago. That was a good move, but it seems they all have their specific quirks…

I think this update solves the problem, in the sense that it now shows an error message box.

FontCreator 13.0.0.2662 (64-bit)

Let us know your results.

6

Yes. I get a useful error message to help me locate the problem.

7

So maybe a group of typographers declaring publicly that they need new glasses is not the greatest form of marketing … :laughing:

Interesting behavior on 13.0.0.2663. In the Override Range by Code Point(s) glyph transformation:

  • if I have “$1234-$4567. $89” (a dot following a code point range) the glyph transform (both on the check button and on execution) will change the erroneous dot to a comma and do the right thing silently. Helpful.


  • If I have “$1234. $89” (a dot following a single code point) it will complain with a (valid) error message.

Both are OK, but different. Just pointing this out … not a real bug (unless there is some relate issue …)

Also … wanted to mention that one very mildly annoying thing about upgrading to a new minor version: Noramally, [Save] (ctrl-S) on a .FCP file will simply save the file directly. However, after an upgrade, [Save] of a .FCP file become a [Save As], putting up a dialog box and asking you if you want to overwrite the file you are working on. Very minor thing, not really an issue …

8

That happens because the new Font Project cannot be opened by older versions.

9

This will be fixed with a next upcoming update.

Actually the font project files are not backwards compatible with earlier releases of FontCreator. That is why you need to go through this process. However, FontCreator should also have warned about this, but apparently it does not. Sorry about this now confusing behaviour. The reason for the upgraded project format, is the newly added PairPosFormat1 option for pair positioning.

10

We have just released an update that solves the issue.

11

Works perfectly in all the cases I could think of to test.

.. and I didn’t even need the Show Error extension after all!

12

Does not seem to make any difference for decimal code-points.

42802-42809. 42812. 42813, 42830, 42831, 42848, 42849, 61124, 61125, 61129-61131, 61133-61136, 61143-61148. 61150-61152, 61363-61374, 61378-61390, 61392, 64256-64262
13

I didn’t think of testing decimal code points … sorry!

14

Well, the codepoints should be separated by commas (or hyphens to add a range of characters). We will release another update that is less strict, so it also accepts codepoints separated by space characters.

15

Here is another update that should do the trick:

FontCreator 13.0.0.2665 (64-bit)

Let us know your results.

16

Still failing on my above code with periods replacing some commas.

17

Periods are not allowed.

18

I am happy with that. At least we’re told where they are so that it is easy to fix typos.

19

:smiley:

20

Works great! Tried out-of-order lists, mixed hex and decimal, and mix of commas and spaces.