Bug 193140 - fix confliction of japanese/dvi2tty
Summary: fix confliction of japanese/dvi2tty
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Hiroki Sato
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-30 04:55 UTC by TsurutaniNaoki
Modified: 2015-03-29 11:02 UTC (History)
2 users (show)

See Also:


Attachments
dvi2tty.diff (967 bytes, patch)
2014-08-30 04:55 UTC, TsurutaniNaoki
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description TsurutaniNaoki 2014-08-30 04:55:31 UTC
Created attachment 146521 [details]
dvi2tty.diff

japanese/dvi2tty conflicts with dvi2tty and texlive-base.
	only "j" prefixed files are installed now.

Fix:
here is a patch.
Comment 1 Hiroki Sato freebsd_committer freebsd_triage 2014-08-30 06:46:52 UTC
Just of my curiosity, but dvi2tty in TeXLive 2014 supports pTeX and jTeX dvi files (-A and -N flags).  Do we still need Japanese-localized version?
Comment 2 TsurutaniNaoki 2014-08-30 08:21:53 UTC
I do not know it.
A dvi file processed via platex in ja-tex-ptex-3.5 can be shown
with "dvi2tty -A" in texlive-20140525_1, but some charactors are
not shown, even if it is shown with jdvi2tty.
If this is a slight trouble and is fixed soon, I can throw away this port at this time.
Comment 3 commit-hook freebsd_committer freebsd_triage 2014-08-30 08:32:42 UTC
A commit references this bug:

Author: hrs
Date: Sat Aug 30 08:31:41 UTC 2014
New revision: 366596
URL: http://svnweb.freebsd.org/changeset/ports/366596

Log:
  Fix filename conflict with dvi2tty installed by TeXLive.

  PR:	193140

Changes:
  head/japanese/dvi2tty/Makefile
Comment 4 Hiroki Sato freebsd_committer freebsd_triage 2014-08-30 08:36:30 UTC
Committed the patch.  Can you please send me a sample .tex file which gives different results between jdvi2tty and dvi2tty -A?
Comment 5 Bartek Rutkowski freebsd_committer freebsd_triage 2015-03-29 11:02:44 UTC
The fix has been already committed, so I am closing this PR.