what system/FontLab version are you running? Did you get the macro from steroids.fontlab.net? What exactly is the problem when you're trying to run it?
I'm running FontLab 4.6, Python 2.3 and the script is from the steroids download you mention. I've placed my .ren file within the Mapping folder as instructed in the script too.
I have a few dozen T1 files that I'm breaking into full featured OpenType fonts. Currently I'm trying to rename the small caps: a to a.smcp b to b.smcp c to c.smcp etc.
I've set them up as detailed in the script: a a.smcp b b.smcp c c.smcp etc.
Thinking I may have set something up incorrectly I also ran some of the Tiro rename files and but got the same result.
After running the script I get: "OK, glyphs renamed"
1. Which *operating system* are you using? (Exactly).
2. So, you run the script and the *only* thing you see is "OK, glyphs renamed"? You don't see the dialog box? Or do you see the dialog box, run the script, get the "OK, glyphs renamed" message but the glyphs themselves aren't actually renamed? Are they color-marked?
Please try to describe everything you are doing and everything that happens, step-by-step.
I get the dialog box, run the script, and then recieve the "Ok, glyphs renamed" message. I've checked the option to mark the glyphs that have been changed - though they don't as the names aren't changing.
That's it, step by step.
I'm able to run my other Python scripts without a problem.
Adam, I'm not sure if this is the issue that Eric is encountering, but I had a problem with the rename glyphs script last year when some .ren files I created had Unicode encoding instead of 'DOS'. [I made them in UltraEdit, with which I know you are familiar, and had set up my preferences so that every new document was automatically Unicode encoded.] When I converted the .ren files to 'DOS' encoding, the script worked.
Is it possible that your script requires 8-bit text?
21 Oct 2004 — 3:13pm
Eric,
what system/FontLab version are you running? Did you get the macro from steroids.fontlab.net? What exactly is the problem when you're trying to run it?
Adam
21 Oct 2004 — 3:34pm
Adam -
I'm running FontLab 4.6, Python 2.3 and the script is from the
steroids download you mention. I've placed my .ren file within
the Mapping folder as instructed in the script too.
I have a few dozen T1 files that I'm breaking into full featured
OpenType fonts. Currently I'm trying to rename the small caps:
a to a.smcp
b to b.smcp
c to c.smcp
etc.
I've set them up as detailed in the script:
a a.smcp
b b.smcp
c c.smcp
etc.
Thinking I may have set something up incorrectly I also
ran some of the Tiro rename files and but got the same result.
After running the script I get:
"OK, glyphs renamed"
I'm not sure what would be causing this.
Thanks
21 Oct 2004 — 3:53pm
Eric,
1. Which *operating system* are you using? (Exactly).
2. So, you run the script and the *only* thing you see is "OK, glyphs renamed"? You don't see the dialog box? Or do you see the dialog box, run the script, get the "OK, glyphs renamed" message but the glyphs themselves aren't actually renamed? Are they color-marked?
Please try to describe everything you are doing and everything that happens, step-by-step.
Regards,
Adam
21 Oct 2004 — 4:04pm
I'm running OSX - Panther 10.3.5
I get the dialog box, run the script, and then recieve the
"Ok, glyphs renamed" message. I've checked the option
to mark the glyphs that have been changed - though
they don't as the names aren't changing.
That's it, step by step.
I'm able to run my other Python scripts without a problem.
Thanks
21 Oct 2004 — 5:37pm
Adam, I'm not sure if this is the issue that Eric is encountering, but I had a problem with the rename glyphs script last year when some .ren files I created had Unicode encoding instead of 'DOS'. [I made them in UltraEdit, with which I know you are familiar, and had set up my preferences so that every new document was automatically Unicode encoded.] When I converted the .ren files to 'DOS' encoding, the script worked.
Is it possible that your script requires 8-bit text?