Debian Bug report logs - #481134
xpdf-japanese Should register fonts in fontconfig and/or defoma and/or provide poppler specific symlinks

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Junichi Uekawa <dancer@netfort.gr.jp>

To: submit@bugs.debian.org

Subject: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Wed, 14 May 2008 08:49:43 +0900

Package: libpoppler2
Severity: grave


xpdf-japanese installs CMAP files in
/usr/share/fonts/cmap/adobe-japan1 etc, but libpoppler looks at
/usr/share/poppler.

I need to install the following symlinks in order to use the adobe
CMAP files.

$ ls -l  /usr/share/poppler/cidToUnicode/Adobe-Japan1 
lrwxrwxrwx 1 root root 34 2008-01-18 19:53 Adobe-Japan1 -> /usr/share/fonts/cmap/adobe-japan1

$ ls -l  /usr/share/poppler/cMap/
lrwxrwxrwx 1 root root 50 2008-01-18 19:53 /usr/share/poppler/cidToUnicode/Adobe-Japan1 -> /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode



Please either make poppler look at the old location or install some
kind of symlinking.


regards,
	junichi
-- 
dancer@{debian.org,netfort.gr.jp}   Debian Project

Message #10 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Loïc Minier <lool@dooz.org>

To: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Tue, 10 Jun 2008 17:17:32 +0200

On Wed, May 14, 2008, Junichi Uekawa wrote:
> xpdf-japanese installs CMAP files in
> /usr/share/fonts/cmap/adobe-japan1 etc, but libpoppler looks at
> /usr/share/poppler.
> 
> I need to install the following symlinks in order to use the adobe
> CMAP files.
> 
> $ ls -l  /usr/share/poppler/cidToUnicode/Adobe-Japan1 
> lrwxrwxrwx 1 root root 34 2008-01-18 19:53 Adobe-Japan1 -> /usr/share/fonts/cmap/adobe-japan1
> 
> $ ls -l  /usr/share/poppler/cMap/
> lrwxrwxrwx 1 root root 50 2008-01-18 19:53 /usr/share/poppler/cidToUnicode/Adobe-Japan1 -> /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode
> 
> Please either make poppler look at the old location or install some
> kind of symlinking.

 Is this a regression from previous poppler versions?

-- 
Loïc Minier

Message #15 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Junichi Uekawa <dancer@netfort.gr.jp>

To: Loïc Minier <lool@dooz.org>

Cc: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Wed, 11 Jun 2008 08:38:57 +0900

Hi,

> On Wed, May 14, 2008, Junichi Uekawa wrote:
> > xpdf-japanese installs CMAP files in
> > /usr/share/fonts/cmap/adobe-japan1 etc, but libpoppler looks at
> > /usr/share/poppler.
> > 
> > I need to install the following symlinks in order to use the adobe
> > CMAP files.
> > 
> > $ ls -l  /usr/share/poppler/cidToUnicode/Adobe-Japan1 
> > lrwxrwxrwx 1 root root 34 2008-01-18 19:53 Adobe-Japan1 -> /usr/share/fonts/cmap/adobe-japan1
> > 
> > $ ls -l  /usr/share/poppler/cMap/
> > lrwxrwxrwx 1 root root 50 2008-01-18 19:53 /usr/share/poppler/cidToUnicode/Adobe-Japan1 -> /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode
> > 
> > Please either make poppler look at the old location or install some
> > kind of symlinking.
> 
>  Is this a regression from previous poppler versions?

Yup. It used to use xpdf resources in etch.

I wondered why this is the case and looked a bit closer into the problem.

etch poppler used to look at /etc/xpdfrc for configuration, thus it
re-used xpdf configuration for CID etc.

sid poppler has the paths hard-coded somewhere.

$ strings /usr/lib/libpoppler.so | grep usr
/usr/share/poppler/unicodeMap
/usr/share/poppler/cMap
/usr/share/poppler/nameToUnicode
/usr/share/poppler/cidToUnicode


These are apparently configured in poppler/GlobalParams.cc, 
GlobalParams::scanEncodingDirs() 


It looks as if it's a trivial task to add the other dirs and make it
scan there also for backwards portability.  

For full compatibility, parsing of xpdfrc is necessary, but that's
going backwards looking at poppler changelog.


There are probably 3 ways to fix this problem, and I think 1 has the least impact.

1. make poppler look into the old paths again

2. make xpdf-japanese/xpdf-* provide the files in the new path (hardlinked or symlinked) 

3. get poppler-data into NEW (users will have to install packages with duplicate data).


regards,
	junichi
-- 
dancer@{debian.org,netfort.gr.jp}   Debian Project

Message #22 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Hideki Yamane <henrich@debian.or.jp>

To: debian-devel@lists.debian.org

Cc: Junichi Uekawa <dancer@debian.org>, 481134@bugs.debian.org

Subject: Re: Re: Needs help: CJK Debian users will not be able to read PDF with poppler-data in default Debian Desktop in Lenny

Date: Fri, 8 Aug 2008 00:34:33 +0900

> >  But evince was changed. We need poppler package (depends on libpoppler-glib3)
> >  to view PDF files, and if you want to view Japanese PDF file, you
> >  also need to install poppler-data - but it is NOT in Debian yet.
> 
> Debian lenny is frozen, it is too late to get new packages in.

 Yes, late...um...but we -CJK Debian users- need to solve this problem.


> > How do we deal with this issue?
> 
> The first two solutions proposed in #481134 sound fine, just someone
> to make the required changes.

 Okay, I cannot go to Debconf8, but Junichi will go, so I'll leave it
 to him, poppler maintainer and RMs :-)

-- 
Regards,

 Hideki Yamane     henrich @ debian.or.jp/iijmio-mail.jp
 http://wiki.debian.org/HidekiYamane

Message #27 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Loïc Minier <lool@dooz.org>

To: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org, Hideki Yamane <henrich@debian.or.jp>

Cc: debian-devel@lists.debian.org, Junichi Uekawa <dancer@debian.org>, control@bugs.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Wed, 20 Aug 2008 16:06:40 +0200

clone 481134 -1
reassign 481134 xpdf-japanese
retitle 481134 xpdf-japanese Should register fonts in fontconfig and/or defoma and/or provide poppler specific symlinks
retitle -1 poppler doesn't support xpdf config anymore
severity -1 important
stop

        Heya,

 Executive summary: downgrading RC-ness against poppler, the burden of
 the fix is probably on xpdf-japanese to start with.  Request for
 comments/help on fontconfig/defoma topics.

On Wed, May 14, 2008, Junichi Uekawa wrote:
> xpdf-japanese installs CMAP files in
> /usr/share/fonts/cmap/adobe-japan1 etc, but libpoppler looks at
> /usr/share/poppler.
> I need to install the following symlinks in order to use the adobe
> CMAP files.
> $ ls -l  /usr/share/poppler/cidToUnicode/Adobe-Japan1 
> lrwxrwxrwx 1 root root 34 2008-01-18 19:53 Adobe-Japan1 -> /usr/share/fonts/cmap/adobe-japan1
> $ ls -l  /usr/share/poppler/cMap/
> lrwxrwxrwx 1 root root 50 2008-01-18 19:53 /usr/share/poppler/cidToUnicode/Adobe-Japan1 -> /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode

 (the symlinks are flipped)

 I confirmed that adding similar symlinks allows display of Japanese PDF
 files with evince (poppler).  I don't think adding the symlinks in
 poppler is a good idea.

 What happens here is that xpdf-japanese installs a xpdfrc config file
 snippet which will properly configure unicodeMap and cMapDir with
 various files for xpdf, see /etc/xpdf/xpdfrc-japanese:
    #----- begin Japanese support package (2004-jul-27)
    cidToUnicode    Adobe-Japan1    /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode
    unicodeMap      ISO-2022-JP     /usr/share/xpdf/japanese/ISO-2022-JP.unicodeMap
    unicodeMap      EUC-JP          /usr/share/xpdf/japanese/EUC-JP.unicodeMap
    unicodeMap      Shift-JIS       /usr/share/xpdf/japanese/Shift-JIS.unicodeMap
    cMapDir         Adobe-Japan1    /usr/share/fonts/cmap/adobe-japan1
    toUnicodeDir                    /usr/share/fonts/cmap/adobe-japan1
    ...

 poppler probably used to parse xpdf's config as it was forked from
 xpdf.

 Nowadays, poppler has these /usr/share/poppler/cidToUnicode and /cMap
 dirs (along others) to allow for these mappings; these rely on the
 filenames for the mappings to work, so e.g. if poppler needs
 Adobe-Japan1's mapping, it will look for Adobe-Japan1 in there.  The
 actual data for the Adobe-Japan1 font is available in
 /usr/share/fonts/cmap/adobe-japan1 and
 /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode, but there isn't any
 place with the data available with the expected file names
 "Adobe-Japan1".

 My understanding is that xpdf-japanese is very xpdf specific; it does
 install some files below /usr/share/fonts/cmap, but I'm not sure this
 is used by anything except xpdf.  It only calls update-xpdfrc in
 postinst.

 As I see it, the modern way of dealing with fonts is to use fontconfig
 which poppler supports, but I'm not sure fontconfig provides support
 for cMap and cidToUnicode information.  A Debian alternative for
 dealing with fonts is to use defoma which allows for package specific
 scripts to be run when fonts are registered/removed via defoma.  Some
 defoma scripts mention cmap, but I saw no cidToUnicode references there
 either.

 So because the data is not currently available in any place I could
 find / think of or isn't in the proper format, I see the following
 solutions to fix this bug:
 a) make poppler parse xpdf's config again; I'm not too hot on this as
    it makes poppler leak that it's xpdf based, diverges from upstream,
    and isn't a sustainable long-term option; I'm not even sure it's
    still possible
 b) make xpdf-japanese register fonts properly in fontconfig; I don't
    have enough fontcp,fog foo to understand whether fontconfig can
    carry the relevant information/mappings though; help to write a
    /etc/fonts/conf.d/*xpdf-japanese*.conf is welcome; it's not clear to
    me whether such mappings are reaching too far for fontconfig's goal;
    this might also require poppler patching to lookup the relevant
    fontconfig data if poppler doesn't use this part of fontconfig, or
    if we had new API for this stuff to fontconfig; probably a good
    solution for other packages in the same solution as well
 c) make xpdf-japanese register fonts with defoma and make poppler run a
    defoma script to generate appropriate symlinks to the cidToUnicode
    and cMap files/dirs; I don't have enough defoma foo to understand
    whether it's already possible in defoma, but I would expect it is;
    this has the benefit of making it easy to handle other packages in
    the same case; help welcome to answer the open issues here
 d) make xpdf-japanese generate /usr/share/poppler/{cMap,cidToUnicode}/*
    symlinks; probably dead easy, but makes the solution poppler
    specific: other fontconfig or defoma using apps wont benefit from
    the fonts/mappings; also leaves open the question of integration:
    should it be a new poppler-japanese package?  who should be pulling
    this package?

 For the long term, I'd recommend either b), or c) if b) isn't possible;
 for lenny, either the long term approach or the d) approach would work,
 but d) would only solve the problem for this particular package.

 Because b, c), and d) will almost certainly require changes to
 xpdf-japanese, I'm reassigning the RC counterpart of this bug to this
 package.  I'm keeping an important bug open against poppler because it
 can be considered a regression of poppler, but I don't think it should
 be considered RC for poppler because:
  * xpdf-japanese is non-free while poppler is free; perhaps this is a
    fallacy, but I don't think support for a non-free package should
    affect the Debian release; if this is considered >= serious
    severity, it shouldn't be release-blocking
  * it's an upstream design decision that poppler doesn't support xpdf
    config/data and poppler doesn't aim to be compatible with xpdf's
    config/data: xpdf-japanese needs to grow compatibility with poppler
    instead


    Cheers,
-- 
Loïc Minier

Message #38 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Hamish Moffatt <hamish@debian.org>

To: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org, Hideki Yamane <henrich@debian.or.jp>, debian-devel@lists.debian.org, Junichi Uekawa <dancer@debian.org>

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Thu, 21 Aug 2008 14:18:42 +1000

On Wed, Aug 20, 2008 at 04:06:40PM +0200, Loïc Minier wrote:
>  For the long term, I'd recommend either b), or c) if b) isn't possible;
>  for lenny, either the long term approach or the d) approach would work,
>  but d) would only solve the problem for this particular package.
> 
>  Because b, c), and d) will almost certainly require changes to
>  xpdf-japanese, I'm reassigning the RC counterpart of this bug to this
>  package.  I'm keeping an important bug open against poppler because it
>  can be considered a regression of poppler, but I don't think it should
>  be considered RC for poppler because:
>   * xpdf-japanese is non-free while poppler is free; perhaps this is a
>     fallacy, but I don't think support for a non-free package should
>     affect the Debian release; if this is considered >= serious
>     severity, it shouldn't be release-blocking
>   * it's an upstream design decision that poppler doesn't support xpdf
>     config/data and poppler doesn't aim to be compatible with xpdf's
>     config/data: xpdf-japanese needs to grow compatibility with poppler
>     instead

Patches for xpdf-japanese would be most welcome. I'm not familiar with
the details of fontconfig, defoma etc.

Maybe the relevant data in xpdf-japanese should be moved into
cmap-adobe-japan1 instead. Probably xpdf-japanese's additional CMaps
should move too; I thought I submitted a bug about this years ago but I
don't see it now.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Message #43 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Junichi Uekawa <dancer@netfort.gr.jp>

To: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org, Hideki Yamane <henrich@debian.or.jp>, debian-devel@lists.debian.org, Junichi Uekawa <dancer@debian.org>

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Wed, 20 Aug 2008 21:42:21 -0700

Hi,

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.

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.


regards,
	junichi


> clone 481134 -1
> reassign 481134 xpdf-japanese
> retitle 481134 xpdf-japanese Should register fonts in fontconfig and/or defoma and/or provide poppler specific symlinks
> retitle -1 poppler doesn't support xpdf config anymore
> severity -1 important
> stop
> 
>         Heya,
> 
>  Executive summary: downgrading RC-ness against poppler, the burden of
>  the fix is probably on xpdf-japanese to start with.  Request for
>  comments/help on fontconfig/defoma topics.

Message #48 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Hamish Moffatt <hamish@debian.org>

To: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org

Cc: Hideki Yamane <henrich@debian.or.jp>, debian-devel@lists.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Thu, 21 Aug 2008 15:18:13 +1000

On Wed, Aug 20, 2008 at 09:42:21PM -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.

thanks,
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Message #53 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Junichi Uekawa <dancer@netfort.gr.jp>

To: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org, Hideki Yamane <henrich@debian.or.jp>, debian-devel@lists.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Fri, 22 Aug 2008 07:51:36 -0700

Hi,


> > 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.


diff -ur xpdf-japanese-20040727-orig/debian/changelog xpdf-japanese-20040727/debian/changelog
--- xpdf-japanese-20040727-orig/debian/changelog	2008-08-22 07:13:09.000000000 -0700
+++ xpdf-japanese-20040727/debian/changelog	2008-08-22 07:24:30.000000000 -0700
@@ -1,3 +1,10 @@
+xpdf-japanese (1:20040727-1.1) unstable; urgency=low
+
+  * add symlinks to facilitate poppler transition for lenny. 
+    In the longer term, users should migrate to poppler-data.
+
+ -- Junichi Uekawa <dancer@debian.org>  Fri, 22 Aug 2008 07:24:30 -0700
+
 xpdf-japanese (1:20040727-1) unstable; urgency=low
 
   * New upstream version
diff -ur xpdf-japanese-20040727-orig/debian/rules xpdf-japanese-20040727/debian/rules
--- xpdf-japanese-20040727-orig/debian/rules	2008-08-22 07:13:09.000000000 -0700
+++ xpdf-japanese-20040727/debian/rules	2008-08-22 07:45:47.000000000 -0700
@@ -2,6 +2,9 @@
 TARGET=japanese
 CMAP=/usr/share/fonts/cmap/adobe-japan1
 
+# datadir for poppler
+POPPLER_DATA=/usr/share/poppler
+
 POSTRM=debian/xpdf-$(TARGET).postrm
 PREINST=debian/xpdf-$(TARGET).preinst
 
@@ -29,6 +32,11 @@
 	cp -r *.cidToUnicode *.unicodeMap debian/xpdf-$(TARGET)/usr/share/xpdf/$(TARGET)/
 	cp add-to-xpdfrc debian/xpdf-$(TARGET)/etc/xpdf/xpdfrc-$(TARGET)
 
+	# install poppler symlinks
+	mkdir -p debian/xpdf-$(TARGET)${POPPLER_DATA}/cMap/
+	dh_link ${CMAP} ${POPPLER_DATA}/cMap/Adobe-Japan1
+	dh_link /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode  ${POPPLER_DATA}/cidToUnicode/Adobe-Japan1/Adobe-Japan1.cidToUnicode
+
 	cp debian/preinst-template $(PREINST)
 	cp debian/postrm-template $(POSTRM)
 
 

regards,
	junichi
-- 
dancer@{netfort.gr.jp,debian.org}

Message #58 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Deng Xiyue <manphiz-guest@users.alioth.debian.org>

To: Junichi Uekawa <dancer@netfort.gr.jp>

Cc: 481134@bugs.debian.org, Hideki Yamane <henrich@debian.or.jp>, debian-devel@lists.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Fri, 22 Aug 2008 23:26:53 +0800

在 2008-08-22五的 07:51 -0700，Junichi Uekawa写道：
> 1. poppler was theoretically self-contained, poppler-data was REJECTed
> once and not yet part of non-free as of today.

Which is now sitting in NEW queue again for approval[1].  IMHO, It
doesn't worth to put effort in something to solve problem that is
already handled by others, which makes it unnecessary once accepted.
Better to push ftp-masters to get it reviewed and ask for a freeze
exception ASAP.

[1] http://ftp-master.debian.org/new/poppler-data_0.2.0-1.html

-- 
Regards,
Deng Xiyue, a.k.a. manphiz

Message #63 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Hamish Moffatt <hamish@debian.org>

To: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org

Cc: Hideki Yamane <henrich@debian.or.jp>, debian-devel@lists.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Sat, 23 Aug 2008 11:39:11 +1000

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>

Message #68 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Deng Xiyue <manphiz-guest@users.alioth.debian.org>

To: Hamish Moffatt <hamish@debian.org>

Cc: Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org, Hideki Yamane <henrich@debian.or.jp>, debian-devel@lists.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Sat, 23 Aug 2008 14:40:40 +0800

在 2008-08-23六的 11:39 +1000，Hamish Moffatt写道：
> 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.
> 

Which means the same should be done in
xpdf-{chinese-{simplified,tranditional},korean} as well, and all will be
unnecessary once poppler-data get accepted.  I kind of think that's not
a good way to deal with it.  But well, just my 2 cents.

-- 
Regards,
Deng Xiyue, a.k.a. manphiz

Message #73 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Deng Xiyue <manphiz-guest@users.alioth.debian.org>

To: debian-devel@lists.debian.org

Cc: ftpmaster@debian.org, 481134@bugs.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Sat, 23 Aug 2008 15:10:22 +0800

[Message part 1 (text/plain, inline)]

在 2008-08-23六的 02:33 +0900，Osamu Aoki写道：
> On Fri, Aug 22, 2008 at 11:26:53PM +0800, Deng Xiyue wrote:
> > 在 2008-08-22五的 07:51 -0700，Junichi Uekawa写道：
> > > 1. poppler was theoretically self-contained, poppler-data was REJECTed
> > > once and not yet part of non-free as of today.
> > 
> > Which is now sitting in NEW queue again for approval[1].  IMHO, It
> > doesn't worth to put effort in something to solve problem that is
> > already handled by others, which makes it unnecessary once accepted.
> > Better to push ftp-masters to get it reviewed and ask for a freeze
> > exception ASAP.
> > 
> > [1] http://ftp-master.debian.org/new/poppler-data_0.2.0-1.html
> 
> Time is short...
> 
> * Does Junichi's fix cause any side effects?
>   If no, then just do it and ask release team to give hint to include
> this in release.  (We all know release team acts fast.)
> 
> * Do we know how to ask FTP master?  My impression is they ar too busy
>   with many things so they may not be able to act soon enough.  Why take
>   chance.
> 
> (Deng: did you send request?  Arguing here for FTP mater seems not so
> effective.)
> 
> 
> Osamu
> 


Don't know whether it is orthodox, but as the urgency of the issue, I
got the the mail addres of ftp-masters from pabs on IRC (thanks pabs)
and added to CC.

Ftp-masters, sorry to break the protocol, but due to the current
situation, it'll be very helpful if the poppler-data package sitting in
NEW will be reviewed soonish so that it can be decided whether the NMU
of xpdf-CJK packages should be done.  Obviously poppler-data is the best
way to solve the issue.  Thanks very much.

-- 
Regards,
Deng Xiyue, a.k.a. manphiz

[signature.asc (application/pgp-signature, inline)]

Message #78 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Hamish Moffatt <hamish@debian.org>

To: Deng Xiyue <manphiz-guest@users.alioth.debian.org>, 481134@bugs.debian.org

Cc: debian-devel@lists.debian.org, ftpmaster@debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Sat, 23 Aug 2008 18:09:44 +1000

On Sat, Aug 23, 2008 at 03:10:22PM +0800, Deng Xiyue wrote:
> Ftp-masters, sorry to break the protocol, but due to the current
> situation, it'll be very helpful if the poppler-data package sitting in
> NEW will be reviewed soonish so that it can be decided whether the NMU
> of xpdf-CJK packages should be done.  Obviously poppler-data is the best
> way to solve the issue.  Thanks very much.

You also need the release managers (debian-release@lists.debian.org) to
accept the new package into lenny, and they appear reluctant to allow
new packages in general.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Message #83 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Deng Xiyue <manphiz-guest@users.alioth.debian.org>

To: Hamish Moffatt <hamish@debian.org>

Cc: 481134@bugs.debian.org, debian-devel@lists.debian.org, ftpmaster@debian.org, debian-release@lists.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Sat, 23 Aug 2008 16:50:08 +0800

[Message part 1 (text/plain, inline)]

在 2008-08-23六的 18:09 +1000，Hamish Moffatt写道：
> On Sat, Aug 23, 2008 at 03:10:22PM +0800, Deng Xiyue wrote:
> > Ftp-masters, sorry to break the protocol, but due to the current
> > situation, it'll be very helpful if the poppler-data package sitting in
> > NEW will be reviewed soonish so that it can be decided whether the NMU
> > of xpdf-CJK packages should be done.  Obviously poppler-data is the best
> > way to solve the issue.  Thanks very much.
> 
> You also need the release managers (debian-release@lists.debian.org) to
> accept the new package into lenny, and they appear reluctant to allow
> new packages in general.
> 
> Hamish

Adding debian-release@ to CC, though it's unclear to me whether non-free
package is in the realm of Release Team administration, and it'll be
great to be directed to the right place to deal with the issue if it's
not the case.

FWIW, it is important to know whether the Release Team will make a lenny
freeze exception for poppler-data which is a new package.  Though it
does break the Lenny release criterion, it's the best solution to avoid
duplicated and unnecessary work at present and in future.  So release
team, please consider an unorthodox freeze exception for poppler-data.
Thanks.

> -- 
> Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
> 
> 
-- 
Regards,
Deng Xiyue, a.k.a. manphiz

[signature.asc (application/pgp-signature, inline)]

Message #88 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Junichi Uekawa <dancer@netfort.gr.jp>

To: Deng Xiyue <manphiz-guest@users.alioth.debian.org>

Cc: Hamish Moffatt <hamish@debian.org>, Junichi Uekawa <dancer@netfort.gr.jp>, 481134@bugs.debian.org, Hideki Yamane <henrich@debian.or.jp>, debian-devel@lists.debian.org

Subject: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

Date: Sat, 23 Aug 2008 11:58:07 -0700

Hi,


> > > 
> > > 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.
> > 
> 
> Which means the same should be done in
> xpdf-{chinese-{simplified,tranditional},korean} as well, and all will be
> unnecessary once poppler-data get accepted.  I kind of think that's not
> a good way to deal with it.  But well, just my 2 cents.

Yeah, which is why I'm a bit reluctant on fixing xpdf-japanese etc.
With additional upgrade path to poppler-data when it enters.


Getting poppler-data in for lenny should be much better: it's a new
random package in non-free which has little side-effect if added to
Debian archive.  

From the user's perspective, we probably want some
kind of documentation, since nothing pulls in poppler-data; users
expect working evince but they will be broken on upgrade until they
install poppler-data.



Looking forward into lenny+1, I think it's about time we start
thinking about adobe-cmap-xxx and xpdf-xxx and poppler-data unified in
some way; shipping similar files in multiple packages, and
dpkg-diverting patched files forever doesn't sound right.



regards,
	junichi
-- 
dancer@{netfort.gr.jp,debian.org}

Message #93 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <osamu@debian.org>

To: debian-release@lists.debian.org

Cc: Hamish Moffatt <hamish@debian.org>, 481134@bugs.debian.org, debian-devel@lists.debian.org, Hideki Yamane <henrich@debian.or.jp>

Subject: Please hint poppler-data for lenny inclusion

Date: Sun, 24 Aug 2008 04:58:58 +0900

[Message part 1 (text/plain, inline)]

Hi,

On Sat, Aug 23, 2008 at 04:50:08PM +0800, Deng Xiyue wrote:
> 在 2008-08-23六的 18:09 +1000，Hamish Moffatt写道：
> > On Sat, Aug 23, 2008 at 03:10:22PM +0800, Deng Xiyue wrote:
> > > Ftp-masters, sorry to break the protocol, but due to the current
> > > situation, it'll be very helpful if the poppler-data package sitting in
> > > NEW will be reviewed soonish so that it can be decided whether the NMU
> > > of xpdf-CJK packages should be done.  Obviously poppler-data is the best
> > > way to solve the issue.  Thanks very much.

FTP master has been acted :-)

> > You also need the release managers (debian-release@lists.debian.org) to
> > accept the new package into lenny, and they appear reluctant to allow
> > new packages in general.
> > 
> > Hamish
> 
> Adding debian-release@ to CC, though it's unclear to me whether non-free
> package is in the realm of Release Team administration, and it'll be
> great to be directed to the right place to deal with the issue if it's
> not the case.
> 
> FWIW, it is important to know whether the Release Team will make a lenny
> freeze exception for poppler-data which is a new package.  Though it
> does break the Lenny release criterion, it's the best solution to avoid
> duplicated and unnecessary work at present and in future.  So release
> team, please consider an unorthodox freeze exception for poppler-data.
> Thanks.

Please hint poppler-data .

Although it is in non-free, it is essential to read PDF files created in
Asian languages.  These data were in main packages but due to package
reorganization and better license review, it is in non-free.
nfortunately, there is no other ways to use pdf in Asian languages.

Osamu

[signature.asc (application/pgp-signature, inline)]

Message #98 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Christian Perrier <bubulle@debian.org>

To: 481134@bugs.debian.org, debian-devel@lists.debian.org, Hideki Yamane <henrich@debian.or.jp>

Subject: Re: Please hint poppler-data for lenny inclusion

Date: Sun, 24 Aug 2008 08:32:21 +0200

[Message part 1 (text/plain, inline)]

Quoting Osamu Aoki (osamu@debian.org):

> Although it is in non-free, it is essential to read PDF files created in
> Asian languages.  These data were in main packages but due to package
> reorganization and better license review, it is in non-free.
> nfortunately, there is no other ways to use pdf in Asian languages.


Also don't forget about suggesting to add it to the CJK languages
-desktop tasks in tasksel, if it is that important.

I think that non-free packages can be added there...

[signature.asc (application/pgp-signature, inline)]

Message #103 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Luk Claes <luk@debian.org>

To: debian-release@lists.debian.org, Hamish Moffatt <hamish@debian.org>, 481134@bugs.debian.org, Hideki Yamane <henrich@debian.or.jp>

Subject: Re: Please hint poppler-data for lenny inclusion

Date: Sun, 24 Aug 2008 19:45:13 +0200

Osamu Aoki wrote:
> Hi,
> 
> On Sat, Aug 23, 2008 at 04:50:08PM +0800, Deng Xiyue wrote:
>> 在 2008-08-23六的 18:09 +1000，Hamish Moffatt写道：
>>> On Sat, Aug 23, 2008 at 03:10:22PM +0800, Deng Xiyue wrote:
>>>> Ftp-masters, sorry to break the protocol, but due to the current
>>>> situation, it'll be very helpful if the poppler-data package sitting in
>>>> NEW will be reviewed soonish so that it can be decided whether the NMU
>>>> of xpdf-CJK packages should be done.  Obviously poppler-data is the best
>>>> way to solve the issue.  Thanks very much.
> 
> FTP master has been acted :-)
> 
>>> You also need the release managers (debian-release@lists.debian.org) to
>>> accept the new package into lenny, and they appear reluctant to allow
>>> new packages in general.
>>>
>>> Hamish
>> Adding debian-release@ to CC, though it's unclear to me whether non-free
>> package is in the realm of Release Team administration, and it'll be
>> great to be directed to the right place to deal with the issue if it's
>> not the case.
>>
>> FWIW, it is important to know whether the Release Team will make a lenny
>> freeze exception for poppler-data which is a new package.  Though it
>> does break the Lenny release criterion, it's the best solution to avoid
>> duplicated and unnecessary work at present and in future.  So release
>> team, please consider an unorthodox freeze exception for poppler-data.
>> Thanks.
> 
> Please hint poppler-data .
> 
> Although it is in non-free, it is essential to read PDF files created in
> Asian languages.  These data were in main packages but due to package
> reorganization and better license review, it is in non-free.
> nfortunately, there is no other ways to use pdf in Asian languages.

unblocked

Cheers

Luk

Message #108 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Hideki Yamane <henrich@debian.or.jp>

To: Christian Perrier <bubulle@debian.org>

Cc: 481134@bugs.debian.org, debian-devel@lists.debian.org

Subject: Re: Please hint poppler-data for lenny inclusion

Date: Wed, 27 Aug 2008 21:37:01 +0900

On Sun, 24 Aug 2008 08:32:21 +0200
Christian Perrier <bubulle@debian.org> wrote:
> Also don't forget about suggesting to add it to the CJK languages
> -desktop tasks in tasksel, if it is that important.
> 
> I think that non-free packages can be added there...

 That's very very helpful for our users!

 If not, users must edit their apt lines by hand, and know this
 poppler-data package is needed to view PDF files, it's painful
 thing for average users (Yes, I can do that easily, and you can
 also do that, but your mother, father, little brother or sister
 probably can't do that).

 "Our priorities are our users and free software" - yeah, you know that, 
 "users" are important for us :) (not only free software)

 
 So I and other Japanese Debian developer/maintainer/package maintainer/
 users want poppler-data package to there, the CJK languages-desktop 
 tasks in tasksel. Please consider that.

 



-- 
Regards,

 Hideki Yamane     henrich @ debian.or.jp/iijmio-mail.jp
 http://wiki.debian.org/HidekiYamane

Message #113 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Hideki Yamane <henrich@debian.or.jp>

To: Luk Claes <luk@debian.org>

Cc: debian-release@lists.debian.org, Hamish Moffatt <hamish@debian.org>, 481134@bugs.debian.org

Subject: Re: Please hint poppler-data for lenny inclusion

Date: Wed, 27 Aug 2008 21:47:03 +0900

On Sun, 24 Aug 2008 19:45:13 +0200
Luk Claes <luk@debian.org> wrote:
> unblocked

 Great thanks Luk!
 But, verrry sooorry, I've updated this poppler-data package before
 read this mail... 

 changelog is below, 1 bug fix and trivial changes.

> poppler-data (0.2.0-2) unstable; urgency=low
> 
>   * debian/control
>     - add "DM-Upload-Allowed: yes", because I'm DM :)
>     - fix "poppler-data should suggest libpoppler3" (Closes: #496268)
>     - change "Priority: optional" from extra, same as cmap-adobe-*
>     - add some descriptions for cmap-adobe-* users

 so, please unblock this again, please...
 I am terribly sorry about the inconvenience.

-- 
Regards,

 Hideki Yamane     henrich @ debian.or.jp/iijmio-mail.jp
 http://wiki.debian.org/HidekiYamane

Message #118 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Christian Perrier <bubulle@debian.org>

To: Hideki Yamane <henrich@debian.or.jp>

Cc: 481134@bugs.debian.org, debian-devel@lists.debian.org

Subject: Re: Please hint poppler-data for lenny inclusion

Date: Wed, 27 Aug 2008 15:58:38 +0200

Hideki Yamane a écrit :

>  So I and other Japanese Debian developer/maintainer/package maintainer/
>  users want poppler-data package to there, the CJK languages-desktop 
>  tasks in tasksel. Please consider that.

The easiest way to have this to happen is by sending a wishlist bug
report against tasksel.

Message #123 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Deng Xiyue <manphiz-guest@users.alioth.debian.org>

To: Christian Perrier <bubulle@debian.org>

Cc: Hideki Yamane <henrich@debian.or.jp>, 481134@bugs.debian.org, debian-devel@lists.debian.org

Subject: Re: Please hint poppler-data for lenny inclusion

Date: Wed, 27 Aug 2008 22:07:16 +0800

[Message part 1 (text/plain, inline)]

在 2008-08-27三的 15:58 +0200，Christian Perrier写道：
> Hideki Yamane a écrit :
> 
> >  So I and other Japanese Debian developer/maintainer/package maintainer/
> >  users want poppler-data package to there, the CJK languages-desktop 
> >  tasks in tasksel. Please consider that.
> 
> The easiest way to have this to happen is by sending a wishlist bug
> report against tasksel.
> 

Though I'm not a maintainer of tasksel stuff, I think it's valid to
suggest the same to be done for Chinese(both simplified and traditional)
and Korean tasks as well, so that we save some bug number count :)

> 
-- 
Regards,
Deng Xiyue, a.k.a. manphiz

[signature.asc (application/pgp-signature, inline)]

Message #128 received at 481134@bugs.debian.org (full text, mbox, reply):

From: Luk Claes <luk@debian.org>

To: Hideki Yamane <henrich@debian.or.jp>

Cc: debian-release@lists.debian.org, Hamish Moffatt <hamish@debian.org>, 481134@bugs.debian.org

Subject: Re: Please hint poppler-data for lenny inclusion

Date: Wed, 27 Aug 2008 20:05:55 +0200

Hideki Yamane wrote:
> On Sun, 24 Aug 2008 19:45:13 +0200
> Luk Claes <luk@debian.org> wrote:
>> unblocked
> 
>  Great thanks Luk!
>  But, verrry sooorry, I've updated this poppler-data package before
>  read this mail... 
> 
>  changelog is below, 1 bug fix and trivial changes.
> 
>> poppler-data (0.2.0-2) unstable; urgency=low
>>
>>   * debian/control
>>     - add "DM-Upload-Allowed: yes", because I'm DM :)
>>     - fix "poppler-data should suggest libpoppler3" (Closes: #496268)
>>     - change "Priority: optional" from extra, same as cmap-adobe-*
>>     - add some descriptions for cmap-adobe-* users
> 
>  so, please unblock this again, please...
>  I am terribly sorry about the inconvenience.

unblocked

Cheers

Luk

Message #133 received at 481134-done@bugs.debian.org (full text, mbox, reply):

From: Josselin Mouette <joss@debian.org>

To: 481134-done@bugs.debian.org

Subject: Now we have poppler-data

Date: Thu, 23 Oct 2008 11:48:43 +0200

[Message part 1 (text/plain, inline)]

Hi,

now that poppler-data is available in testing and unstable, poppler is
able to read Japanese (and other languages) documents, so I’m closing
this bug.

Cheers,
-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.