First of all this question is not related to Glyphs app. More about how Adobe handles Private Use Area glyphs.
Here is a screenshot showing how things are:
There are three letters: b and two of it’s alternates each of them has unicode value assigned. Everything looks fine in pdf. BUT if I want to copy/paste from the pdf, Adobe Illustrator doesn’t recognize the two alternates.
Does anybody knows if there is a way to fix this? Perhaps some settings in either Illustrator or Acrobat?
What I’m trying to achieve is, for a font that has a lot of alternates, have all the glyphs listed in a file so users can copy/paste from the pdf into a document instead of surfing the PUA table looking for the alternate glyph they need. Surfing might be not that bad but if the font is layered and not all layers are easily recognizable (lets say it’s a shadow or a kind of letterpress effect fill…) - this can be a nightmare…
I agree, it’s definitely what Unicode is for, but, shouldn’t PUA characters be copy-pastable, whatever their glyph forms happen to be? I can’t see why this wouldn’t actually work. Are the Adobe apps constrained to look at GID perhaps?
@mekkablue@Bendy, thank you guys!
I will give it a try.
The thing is I need this to work the usual “ss0X” way in open type aware apps. Do I just need to modify the ss0X functions replacing A.ss0X with uniXXXX in order this to work?
In the source file, click cmd-alt-i on one of the relevant glyphs in the main tab to see ‘info for selection’ and check the ‘production name’ field. Or open one of the exported OTFs in Glyphs and check glyph names for those ones.
Another funny thing.
When a character was named A.ss01 (with unicode E000 assigned) - the glyph was showing up in PopChar and I could copy/paste it into a Word document. When I renamed the glyphs to uniE000 - the glyph is not visible in PopChar (it says there is 1 character in Private Use Area though) and it is not copy/paste-able
Sorry guys, I’m still trying to understand why this doesn’t work with pdfs… @GeorgSeifert - did you mean that I can keep the names of the glyphs as is (A.ss01 etc) - so the features can still be generated automatically - and by using set.productionGlyphName assign uniEXXX names to all the glyphs that has no unicode and this should work well with pdf?
Elena, you are trying a hack here. You try to use PUA for something it is not meant for. Even if you get the one workflow to work for the current version of a certain PDF viewer (and there is no guarantee the PDF viewer will let you circumvent the character stream), there is no guarantee it will work in the future, or with another version, or another PDF viewer.
And even if it works, you are breaking your character stream with it. That means your text would not be searchable, copy-pasteable, transferable anymore. You have mentioned problems in PopChar already. Are you really sure you want to do that, just to find a workaround for apps that do not support OT properly?