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

Re: Bug#570901: Bumping up severity; any progress in this bug?



Hello,

On Wed, Mar 3, 2010 at 10:26 AM, Norbert Preining <preining@logic.at> wrote:
> severity 570901 important
> thanks
>
> Hi Yoshihito-san,
>
> On Mi, 03 Mär 2010, YOSHINO Yoshihito wrote:
>> severity 570901 grave
>
> Well, that is discussable, did you check the definition of "grave" in
> the reference:
>        makes the package in question unusable or mostly so,
>        or causes data loss,
>        or introduces a security hole allowing access to the accounts
>           of users who use the package.
> So let us check that:
> - unusable or mostly so: definitely not, the majority still does not
>  use ptex!
> - causes data loss: definitely not
> - security hole: definitely not

I read the definition of severity before the bump but I missed the point
that other programs than dvipdfmx work properly.

>> I hope this bug be fixed before release of squeeze, or many CJK people will
>> have incovenience. It does not work unless manually modifying configuration
>> files.
>
> THese changes would create for the majority of the users (those
> not having ptex-jisfonts installed) the warning message you mentioned,
> so I am not overly happy with the approach you have proposed.
>
> With the original dvipdfmx package before the take over, how was that
> handled in detail?

In the old dvipdfmx package "/etc/texmf/dvipdfm/fontmapsx" file _was_
used in which additional dvipdfmx configuration lines are handled by
other dvipdfmx-needing packages; for example, ptex-jisfonts appends
"f  jis-cjk.map" line to it or removes the line in the maintainer
postinst/prerm scripts using sed... By using this fontmapsx approach,
users who do not have the fontmapsx file always get another warning but
can have PDFs normally:

    ** WARNING ** Could not open config file "fontmapsx".

However, upstream dvipdfmx 20080517 or later changed the kpathsea
application name from dvipdfm to dvipdfmx and at the same time got to
look for dvipdfmx-specific configuration directory /etc/texmf/dvipdfmx
(cf. Important Note in http://project.ktug.or.kr/dvipdfmx/). Debian
lenny's dvipdfmx tried to revert to the older behavior (looking into
/etc/texmf/dvipdfm etc.) before 20080517 for dvipdfmx-needing packages
to work, by changing back the kpathsea progname to "dvipdfm"... This
revert was done partially; in reality, for files other than (at least)
"fontmapsx". Actually lenny's dvipdfmx does not even read
"/etc/texmf/dvipdfm/fontmapsx" :(

Anyway, adding needed map file entries to dvipdfmx.cfg causes each
warning to each line...

> Are there any other additions of map files expected?
I don't know, but more map files are added, and more warnings will be
produced...

> We should find a good solution for that. The problem is that dvipdfmx
> is now the default program and is even used as dvipdfm, so we don't
> want that warning message show up permanently.
>
> For example, *every* *EVERY* xetex run would produce that warning
> message, so that is definitely NOT the way to go, sorry.

OK, I attach another patch in place of the warning-full patch to add
some mappings to "cid-x.map" necessary for jis fonts (rml-jis and
gbm-jis) which are copied from "jis-cjk.map" file in ptex-jisfonts.
This patch works around for ptex-jisfonts users, and other people will
not receive any warning message. I don't know other Chinese/Korean
people need their extra mappings, but, if so, the mappings can be added
like this patch. One caveat of this patch is that it does not handle
well with mapping the same font to another font, that is, mapping
"rml-jis" to other than "Ryumin-Light". This patch will work except in
such a situation (which I think "fontmapsx" takes into account.)

Note that the patch to restore DVIPDFMx.cnf proposed in the first post
is still needed to look for cmap files.

Regards,

-- 
YOSHINO Yoshihito <yy.y.ja.jp@gmail.com>
diff -urN texlive-base-2009/debian/patches/dvipdfmx-cid-x.map-add-jis texlive-base-2009.new/debian/patches/dvipdfmx-cid-x.map-add-jis
--- texlive-base-2009/debian/patches/dvipdfmx-cid-x.map-add-jis	1970-01-01 09:00:00.000000000 +0900
+++ texlive-base-2009.new/debian/patches/dvipdfmx-cid-x.map-add-jis	2010-03-05 03:25:02.000000000 +0900
@@ -0,0 +1,12 @@
+--- texlive-base-2009.orig/texmf/fonts/map/dvipdfmx/cid-x.map	2009-08-23 09:26:55.000000000 +0900
++++ texlive-base-2009/texmf/fonts/map/dvipdfmx/cid-x.map	2010-03-05 03:22:51.000000000 +0900
+@@ -76,6 +76,9 @@
+ rmlv V Ryumin-Light
+ gbmv V GothicBBB-Medium
+ 
++rml-jis H Ryumin-Light
++gbm-jis H GothicBBB-Medium
++
+ %% Synthetic font used for futo* family.
+ %% jun101 not available.
+ %ryumin-l    H Ryumin-Light
diff -urN texlive-base-2009/debian/patches/series texlive-base-2009.new/debian/patches/series
--- texlive-base-2009/debian/patches/series	2010-03-05 04:01:43.000000000 +0900
+++ texlive-base-2009.new/debian/patches/series	2010-03-05 04:00:10.000000000 +0900
@@ -9,6 +9,7 @@
 fix-info-dir-sections
 fix-pgf2pdf-script
 dvipdfm-config-no-rungs
+dvipdfmx-cid-x.map-add-jis
 fix-xyframe.tex.patch
 texdoc-update
 texdoc-viewer-use-see

Reply to: