Bug#451799: new evince cannot display Japanese characters correctly

clone 451799 -1
retitle 451799 evince should depend on poppler-data
reassign -1 wnpp
retitle -1 RFP: poppler-data -- Encoding data for the poppler PDF renderinglibrary
block 451799 by -1
thanks

* Package name : poppler-data
Version : 0.1.1
Upstream Author : Adobe, Red Hat
* URL : http://poppler.freedesktop.org/
* License : non-free, see below
Programming Lang: None
Description : Encoding data for the poppler PDF rendering library

This package contains the encoding data needed to view some PDF
documents with libpoppler.

The copyright is the following:
Copyright 1990-1998 Adobe Systems Incorporated.
All Rights Reserved.

Patents Pending

NOTICE: All information contained herein is the property of Adobe
Systems Incorporated.

Permission is granted for redistribution of this file provided
this copyright notice is maintained intact and that the contents
of this file are not altered in any way from its original form.

PostScript and Display PostScript are trademarks of Adobe Systems
Incorporated which may be registered in certain jurisdictions.

However I don't think there is anything copyrightable in these files;
they only contain series of numbers that describe the mappings. Do you
people think it could be suitable for main?
(Please follow-up on -legal only for licensing discussions.)

Ondrej, are you willing - if the legal problems are settled out - to
package it? Otherwise I guess me or any of the co-maintainers could do
it, the packaging is absolutely trivial.

Le lundi 19 novembre 2007 à 02:25 +0900, Hideki Yamane a écrit :
> New evince package displays Japanese characters wrong. Broken.
> Please see attached image file, one is opened CP-06.pdf with evince
> (Screenshot-CP-06.pdf.png), and another is with Adobe Reader (shows
> fine). I heard same problem from other people on IRC.

The new poppler version needs some specific files that contain some
mappings between Unicode and other encodings, which are in a separate
package.

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.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHTGhIrSla4ddfhTMRAqUbAJ4jwISWpZPCKyYcj9HUKc ulYI2ihACeLCrM
O6aame0nGHwOJpU1bq5lZ34=
=7QVb
-----END PGP SIGNATURE-----

> However I don't think there is anything copyrightable in these files;
> they only contain series of numbers that describe the mappings. Do you
> people think it could be suitable for main?
> (Please follow-up on -legal only for licensing discussions.)
>
> Ondrej, are you willing - if the legal problems are settled out - to
> package it? Otherwise I guess me or any of the co-maintainers could do
> it, the packaging is absolutely trivial.

It's already packaged in pkg-freedesktop SVN, but it was rejected by
ftp-masters due licensing problems.

Ondrej.
--
OndÅ™ej SurÃ½ *** http://blog.rfc1925.org/
KulturnÃ* obÄasnÃ*k *** http://www.obcasnik.cz/
Nehoupat, prosÃ*m *** http://nehoupat.blogspot.com/

(Dropping -legal from the cc)

On Nov 27, 2007 3:56 PM, Josselin Mouette wrote:

> The new poppler version needs some specific files that contain some
> mappings between Unicode and other encodings, which are in a separate
> package.

That's all that it contains? can't that be reproduced with data from
iconv or similar?

--
Martín Ferrari

On Wed, Nov 28, 2007 at 01:22:49PM +0100, OndÅ™ej SurÃ½ wrote:
> > However I don't think there is anything copyrightable in these files;
> > they only contain series of numbers that describe the mappings. Do you
> > people think it could be suitable for main?
> > (Please follow-up on -legal only for licensing discussions.)
> >
> > Ondrej, are you willing - if the legal problems are settled out - to
> > package it? Otherwise I guess me or any of the co-maintainers could do
> > it, the packaging is absolutely trivial.
>
> It's already packaged in pkg-freedesktop SVN, but it was rejected by
> ftp-masters due licensing problems.

If problem is only modification right, why not uploading to non-free?

Osamu

Hi,

Le samedi 01 dÃ©cembre 2007 Ã* 02:11 -0300, MartÃ*n Ferrari a Ã©crit :
> On Nov 27, 2007 3:56 PM, Josselin Mouette wrote:
>
> > The new poppler version needs some specific files that contain some
> > mappings between Unicode and other encodings, which are in a separate
> > package.
>
> That's all that it contains? can't that be reproduced with data from
> iconv or similar?

Files in the unicodeMap directory could certainly be generated
automatically, since they map Unicode to some other standard and
widespread encodings (KOI8-R, EUC-JPâ€¦)

However, for other files, I donâ€™t think iconv knows these encodings:
Adobe-CNS1, Adobe-GB1, Adobe-Japan1 and Adobe-Korean1.

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHVURVrSla4ddfhTMRApvmAJ4pqzrufAvxuIfUqBWUO+ ICxgbA2wCgxrb0
aex2R8Q+Wlc0f/eEC5ptDuc=
=F2e8
-----END PGP SIGNATURE-----

On Tue, Dec 04, 2007 at 01:13:09PM +0100, Josselin Mouette wrote:
> Hi,
>
> Le samedi 01 dÃ©cembre 2007 Ã* 02:11 -0300, MartÃ*n Ferraria Ã©crit :
> > On Nov 27, 2007 3:56 PM, Josselin Mouette wrote:
> >
> > > The new poppler version needs some specific files that contain some
> > > mappings between Unicode and other encodings, which are in a separate
> > > package.
> >
> > That's all that it contains? can't that be reproduced with data from
> > iconv or similar?
>
> Files in the unicodeMap directory could certainly be generated
> automatically, since they map Unicode to some other standard and
> widespread encodings (KOI8-R, EUC-JPâ€¦)
>
> However, for other files, I donâ€™t think iconv knows these encodings:
> Adobe-CNS1, Adobe-GB1, Adobe-Japan1 and Adobe-Korean1.

Note we have cmap-adobe-* packages in non-free, that contain CMaps for
these.

Mike

Bug#451799: new evince cannot display Japanese characters correctly - Debian

Thread: Bug#451799: new evince cannot display Japanese characters correctly

LinkBack

Tools