Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.
Hi,
On Fri, Aug 22, 2008 at 07:51:36AM -0700, Junichi Uekawa wrote:
> > > I'm a bit worried that this needs to be fixed for
> > > xpdf-chinese-simplified
> > > xpdf-chinese-traditional
> > > xpdf-korean
> > > xpdf-japanese
> > >
> > > packages. The fix would probably be simple. It should probably be
> > > hardlinks rather than symlinks considering dpkg behavior wrt symlinked
> > > dirs.
> >
> > You can't hardlink directories though, so we might as well symlink the
> > individual files.
> >
> > > I'd like this fix included in lenny so that we don't see a regression
> > > in Debian for Japanese users.
> > >
> > >
> > > There was a package in the NEW queue 'poppler-data' which should
> > > really have fixed this bug.
> > > http://ftp-master.debian.org/new/poppler-data_0.2.0-1.html
> > >
> > > That going into Debian sid would fix this bug also, but not quite sure
> > > if it's reasonable to expect a new package to enter Debian lenny.
> >
> > I kinda think it's in poppler's domain to fix this; logically
> > xpdf-japanese (etc) exists only to enhance xpdf. poppler-data appears to
> > be a good solution.
>
> 1. poppler was theoretically self-contained, poppler-data was REJECTed
> once and not yet part of non-free as of today.
>
> 2. Japanese users upgrading from etch would have xpdf-japanese
> installed because evince (poppler) needed and used xpdf-japanese, and
> natural upgrade path would be xpdf-japanese supporting poppler.
>
> These factors make adding support in poppler somewhat reasonable.
If the release managers would approve an update to xpdf-japanese I am
happy to upload a new version including your patch, or for you to NMU
the package.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
Reply to: