[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#661863: marked as done (ghostscript: CIDFont fallback to DroidSansFallback doesn't happen as advertised)

Your message dated Thu, 04 Jan 2024 22:34:54 -0600
with message-id <18397908.sWSEgdgrri@riemann>
and subject line Re: dangling symlink /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf
has caused the Debian Bug report #661863,
regarding ghostscript: CIDFont fallback to DroidSansFallback doesn't happen as advertised
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
661863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661863
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ghostscript
Version: 9.05~dfsg-2

Jonas Smedegaard wrote[1]:

> Hmm, I will try that - when I locate a CJK PostScript file to test 
> against.

Looks like the feature just doesn't work.

When I try to view example 38 here: http://www.tcpdf.org/examples.php
It renders without obvious trouble, whether or not fonts-droid is
installed.

So I purged ttf-sazanami-mincho.  The result:

| $ ghostscript -dSAFER ~/web/example_038.pdf
[...]
| Processing pages 1 through 1.
| Page 1
| Can't find CID font "ArialUnicodeMS".
| Attempting to substitute CID font /Adobe-Japan1 for /ArialUnicodeMS, see doc/Use.htm#CIDFontSubstitution.
|    **** Warning: can't process font stream, loading font by the name.
| Can't find the font file /usr/share/fonts/truetype/fonts-japanese-mincho.ttf
| Can't find CID font "ArialUnicodeMS".
| Attempting to substitute CID font /Adobe-Japan1 for /ArialUnicodeMS, see doc/Use.htm#CIDFontSubstitution.
|    **** Error reading a content stream. The page may be incomplete.
|    **** File did not complete the page properly and may be damaged.
| Can't find the font file /usr/share/fonts/truetype/fonts-japanese-mincho.ttf
| >>showpage, press <return> to continue<<

and a blank page.  Next try: purging cmap-adobe-japan1, which
incidentally refreshes the fontconfig cache.  This time I get:

| Processing pages 1 through 1.
| Page 1
|    **** Error reading a content stream. The page may be incomplete.
|    **** File did not complete the page properly and may be damaged.
| >>showpage, press <return> to continue<<

and a blank page.  I was expecting it to fall back to characters from
DroidSansFallback.

Ideas?
Jonathan

[1] http://bugs.debian.org/661764

| $ dpkg-query -W ghostscript ghostscript-x libgs9 libgs9-common gs-cjk-resource
| ghostscript	9.05~dfsg-2
| ghostscript-x	9.05~dfsg-2
| gs-cjk-resource	1.20100103-3
| libgs9	9.05~dfsg-2
| libgs9-common	9.05~dfsg-2

--- End Message ---
--- Begin Message --- 
On Wed, 16 May 2012 09:59:48 -0700 Ian Zimmerman <itz@buug.org> wrote:
> 
> Just BTW, installing fonts-droid doesn't do away with the broken
> symlink:

Tested in current sid with ghostscript 10.02.1 and package "fonts-droid-
fallback".  The symlink is present and correct:

$ file  /usr/share/ghostscript/10.02.1/Resource/CIDFSubst/DroidSansFallback.ttf
/usr/share/ghostscript/10.02.1/Resource/CIDFSubst/DroidSansFallback.ttf: 
symbolic link to ../../../../fonts/truetype/droid/DroidSansFallbackFull.ttf

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: