Bug 12078 - latin small g with acute shifts accent back one letter in serif on printout v2.19
Summary: latin small g with acute shifts accent back one letter in serif on printout v...
Status: RESOLVED NOTOURBUG
Alias: None
Product: DejaVu
Classification: Unclassified
Component: Serif (show other bugs)
Version: unspecified
Hardware: PowerPC Mac OS X (All)
: medium normal
Assignee: Deja Vu bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-20 18:34 UTC by David Bilides
Modified: 2007-08-21 16:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
pdf of page with 2 occurrences of small g with acute (18.79 KB, application/pdf)
2007-08-21 15:04 UTC, David Bilides
Details

Description David Bilides 2007-08-20 18:34:04 UTC
The small g with acute ǵ Unicode 01F5 cannot print without shifting the acute accent back one letter in all serifs except bold italic and bold oblique. Happens in more than 1 application. Screen looks fine in all serifs, Latin capital g with acute Ǵ 01F4 in serif prints fine, and all Latin sans print fine capital and small.

I just discovered this (was only writing on screen, first printout was today) and am planning on publishing a Macedonian book which uses this character this fall. I would like to use the Deja Vu font, so any help or ideas are much appreciated. Regardless, thanks to all who have taken this project this far.
Comment 1 Denis Jacquerye 2007-08-21 06:57:23 UTC
Is this only happening on Mac OS X?
David, can you print to a PDF file and maybe post it here if the bug still occurs?
Comment 2 David Bilides 2007-08-21 15:04:55 UTC
Created attachment 11199 [details]
pdf of page with 2 occurrences of small g with acute

See my response to Denis question (Comment #1).
Comment 3 David Bilides 2007-08-21 15:07:11 UTC
(In reply to comment #1)
> Is this only happening on Mac OS X?
> David, can you print to a PDF file and maybe post it here if the bug still
> occurs?
> 

Thank you, Denis, for an unbelievably quick response.

(Don't know about Windows...don't use it.)

This was a great idea. In the pdf (attached) the letters (words are highlighted) looked fine. But when I tried to print the pdf, same problem, the accent had skipped back one letter (to the a in raǵanje and to r in Ǵorǵi). So, I then tried to see if this might have to do with how the printer driver reads the output. I downloaded the latest version of Gutenprint, and wouldn't you know that it printed fine!

This doesn't explain why the accent *didn't* jump in bold italic and bold serif in my original printings, and why it happened only with the small g and not the cap, so I think that's still worth investigating in all your spare time; I'd be surprised if this doesn't happen on someone else's printer. But, it works for now for me.

Thank you once again, I very much appreciate it.
Comment 4 Denis Jacquerye 2007-08-21 15:38:55 UTC
The bug looks like the precomposed parts of the character 'ǵ' are not repositioned as the font specifies. Combining actue <U+0301> has negative horizontal placement when on its own, but it is repositioned in positives in this character. Capital 'ǵ' uses a part that already has positive horizontal placement.

Possible bug triggers for gutenprint:

- In DejaVu Serif 'ǵ' is composed with 'g' and U+0301 (combining acute), but 'g' with U+00B4 (acute) in Sans. However Bold and Italic have the same composition.
- The order of the references are U+0301 then 'g', that's glyph indeces 769 then 103. Some apps have bugs with composed that do not have references by increasing indeces. However Bold and Italic have the same order.

Marking as notourbug as other shapers don't have the bug.

David: which version of gutenprint was it before?
Comment 5 David Bilides 2007-08-21 16:28:27 UTC
(In reply to comment #4)

> 
> David: which version of gutenprint was it before?
> 

Denis,

I'm sorry if I was not clear. I wasn't using gutenprint before, I was using the driver that was installed with the printer (Brother HL-5170DN Postscript 3). ǵ *did* print as it is supposed to only *after* I used the current (5.1.3) gutenprint cups (1.1) driver.

From what I can understand of your response, it seems as though the bug would probably be in the Brother printer driver, yes?

Thank you very much. What you are all trying to do, as complex as it seems to a layperson like myself, is something I very much support, and I want to express my appreciation for your work and follow-through.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.