I installed the trial version of Glyphs 3, as I am working with version 2 and considered upgrading at the end of the evaluation period. However when trying to open a project made in version 2, Glyphs 3 says that the document cannot be opened, giving the error message “No semicolon at the end of the string at line: 32802”.
You had an invalid metrics key that Glyphs 2 was being able to cope with. Open the files in a code editor (TestMate, Sublime Text, BBEdit …) and goto the line mentioned in the error message. Then look a few lines before and you’ll see a metrics key like this: = "o""; remove the duplicate closing quote and it will work again.
You should get an error message: “No semicolon at the end of the string at line: 176601”. You can open the file in a text editor and go to that line. There you see that there are some corrupted nodes. Glyphs 2 seems to be fine with it, Glyphs 3 trips over them (I see if I can prevent). But you can edit the file by deleting those nodes or giving them a valid node type like “LINE” and then check that outline.
You can search for “glyphname” and search backwards form that location. It is the second layer in the “m”. At least that looks strange after I fixed those nodes.
Suddenly I can’t open the font I have many many hours into. It has a lot of symbols and proprietary so I can’t share the file. It won’t open and says “No semicolon at the end of the string at line: 2”
Here are the first three lines of the .glyphs file I’m trying to open (Glyphs 3):
This happened to me, out of nowhere. I was making kerning groups. I looked at what the dev said above but I cant find the problem. The weird thing is its a Glyphs 3 doc.
This is the text around the line: unicode = 47;
},
{
glyphname = backslash;
kernLeft = "";
kernRight = "";
lastChange = “2023-05-15 12:24:40 +0000”;
layers = (
{
layerId = m01;
shapes = (
{
Line 6148 with lastChange is supposed to be the problem