Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unicode quotes notdef for postscript #15

Closed
bbeardsley opened this issue Mar 2, 2018 · 6 comments
Closed

unicode quotes notdef for postscript #15

bbeardsley opened this issue Mar 2, 2018 · 6 comments

Comments

@bbeardsley
Copy link

bbeardsley commented Mar 2, 2018

My abc file has unicode apostrophe and quotes in the words but abcm2ps is returning notdef in both ps and eps output. How do I go about getting it to work with ps/eps?

@bbeardsley bbeardsley changed the title unicode quotes notdef unicode quotes notdef for postscript Mar 2, 2018
@bbeardsley
Copy link
Author

I did a apt-get install libpango1.0-dev and recompiled. Now the unicode quotes are rendered but in a different font :(

@bbeardsley
Copy link
Author

%abc-2.1
X:1
T: Test
M: 4/4
L: 1/4
K: C
CC
W:I’ve found
W:I have not found

@bbeardsley
Copy link
Author

I've found and I have not found lines are in different fonts when pango is enabled. When it is not enabled, the apostrophe in I've is notdef

@bbeardsley
Copy link
Author

bbeardsley commented Mar 2, 2018

1st - With pango, 2nd - without. On the first notice the different fonts being used, on the second the apostrophe is gone (notdef)

test-with-pango

test-without-pango

@bbeardsley
Copy link
Author

bbeardsley commented Mar 2, 2018

In the PS if I replace

/TeXGyreTermes-Regular 16.0 selectfont

with

16.0 F2

It renders correctly - not sure why it's doing the first...

@moinejf
Copy link
Collaborator

moinejf commented Mar 3, 2018

Without pango (--pango 0 in the command line), you just have to define the missing glyphs with %%glyph:

%%glyph 2019 quoteright

Otherwise, in my distro (VoidLinux), they removed PS support in pango, so, I cannot fully test your font problem.
But this can be explained by the fact that, when finding a non ASCII character, pango searches a font in which the character may be rendered. Then, this font is not changed anymore, up to the next line.
In your case, the first searched font would not be the current font, and, so, the font change.

Anyway, unicode rendering with PostScript is a nightmare. That's why I engage people to move to abc2svg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants